In V10, is there a way to modify promptset's values after a workflow/job is in the Activities window and without modifying the JCL generated?
Do a search for "Fun with AE" in the forum the "Prompt Sets Part 1" will explain now to set up a job so that the prompt sets work correctly. And yes they did not make it easy and the only way to know it is setup correctly is to try it on every job in your job plan / chain.
Good luck converting over to AE from AM.
Hi Jean-Francois, this is possible. The Workflow has to be in a 'stopped' status to modify it.
Here's the description of the 'Modify Task Parameters' action:
This command opens the task'sPromptSetA user-defined input mask for executable objects. A Automic object type. dialog in which you can modify the prompt values subsequently.
When the optionRequest task parametersis activated in RA jobs ( RA tab), you can also modify the RA-specific values by using the PromptSet dialog.
An error message will appear when no PromptSet objects are assigned to the task or when the task is not an RA job in which the optionRequest task parametersis set.
While the task is being modified, it changes to the statusWaiting for user input.
Modifying values after the task has been generated has no effect.
Thanks Jennifer for your answer. It works when the workflow is active, but when the workflow is scheduled to run in the future (let's say an hour from now...), the option 'Stop' is not there and I get an error when I use the option 'Modify Task Parameters'. So, is there a way of changing the prompset values when a workflow is scheduled to run later?
How is the Workflow Activated? Like in a Schedule?
it could be by a schedule or manually by specifying a time in the future.
As Jennifer said, "Modifying values after the task has been generated has no effect.". So if you do not have the "generate at runtime" option turned on, then I don't think you'll be able to do this. How is your "generate at runtime" option set?
If the "generate at runtime" option is turned on, you won't be able to change the value of prompset; you will get an error specifying that the task has not been generated yet.
FYI: we are currently working with a senior consultant from Automic to help us migrating from AM to AE and it ends that it seems to be a bug. So, we'll wait for further notice.
Thanks everybody for your help.
I think that problem can be overcome by navigating to the "Test options" tab and turning on the "Activate attributes dialog" option at job submit time.
Retrieving data ...