The values selected in a Resource Automation, and saved as part of a Request Template, should persist in the Request loaded from that template. In my experience this has always worked.
Can you share the Automation that you are running (is it one of the canned automations?) and the version of RPM you are using.
Thanks for your reply Scott.
The automation is 'RLM Deployment'/'Rlm create and deploy package instance' automation. The automation calls a package in RPD.
Our RPM version is 4.4.00.07.
I tested this in 4.4 patch 7 - all seems ok.
Added a step to a request template calling the rpm create/deploy package (the OTTB one).
Selected some properties from the resource automation and saved the step.
Created a request from this template.
Checked the step and could see the same properties remain selected.
Out of interest, try create a new request template using the same steps above and see if the property selections still dont save.
Thanks Scott, even after creating a new Request Template, the properties selected in that Request Template did not pass along to the new Request. Thanks.
Suggest opening a ticket Mike. I dont have same behavior in my environment.
A Request Template is supposed to save the values from a resource automation when it is run and the step is saved as part of the Request Template
What BRPM version are you using? is it 4.6?
However, what I experienced is that when you open a steps and you land on General tab, then you move to automation tab, you lose all values in your automation fields. A work around I found from now is to define the automation tab as the default landing one when you open the step:
I hope this help.