The AWA v12.1 documentation page on defining workflow task properties states:
By default, the prompt sets of workflow tasks are not displayed on screen and user interaction is not required while the workflow is being executed; the default values specified in the Prompts Tab. This is important to avoid unnecessary interruptions. However, there can be situations in which you want to change this behavior. Activate the Request User Input checkbox if you want the task prompt sets to be displayed on screen requesting the user to enter values.
This is precisely what I want to do. I am revisiting an old workflow that has a somewhat complicated prompt set. For this prompt set, a few of the initial default values must be looked up first, before the initial defaults of the other fields can be evaluated. I had previously tried a very circuitous way of forcing a particular sequence of evaluation, but this proved impractical. So instead, I hit upon the idea of looking up the initial default values of these dependent variables first using a SCRI, and then prompting the user for additional input using a prompt set on the second SCRI in the workflow.
Others have asked this question before, and I actually have it working fine in another workflow. But now with this different workflow, I cannot get it working. The workflow task runs immediately, without displaying the prompt set. It appears to be configured exactly the same as in the workflow where it works as desired.
What’s the secret incantation I must recite?
I figured it out. The prompt set had not been appearing because of errors during evaluation of prompt set defaults. Once I fixed these errors, the prompt set appeared as expected.
This approach seemed promising, but I quickly ran into another problem: when a prompt set is defined on a child task in a workflow, variable resolution in prompt set defaults is not reliable. Depending on the configuration details, one of these two things happens:
U00011801 Error in Server routine 'UCPRMPTR'...U01001002 Invalid MEMSV handle.U00015006 System forced memory trace dump.
If I move the prompt set to the level of the workflow, things work fine. I reported the error to CA Support.