8 Replies Latest reply on Apr 2, 2015 8:53 AM by Fred Breton

Set Properties not Checkmarked

Michael Wu Mar 24, 2015 1:30 PM

Was hoping to find some answers regarding Request Templates.

When creating a new request from a Request Template, we've noticed the property values are not populated in the new request. The property value is populated by what is defined in the property's default value (and not what is saved in the Request Template). This we have learned to work with.

However, there are some other attributes from the Request Template we would like to see carried over to the newly created request after clicking the "New Request From Template" button. We would like to see "Set Properties" checkboxes in the Automation tab inherit the same properties as what was saved in the Request Template.

Is there somewhere in RPM we can have the checkboxes checked off be default or have the new request inherit the checkboxes as per the Request Template?

SetProperties2.jpg 54.0 K
SetProperties1.jpg 51.5 K

1. Re: Set Properties not Checkmarked

Scott Dunbar Mar 25, 2015 3:52 PM (in response to Michael Wu)

Hi Michael,

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.
Like Show 1 Likes(1)

Actions
2. Re: Set Properties not Checkmarked

Michael Wu Mar 26, 2015 2:23 PM (in response to Scott Dunbar)

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.

Thanks,
Mike
Like Show 0 Likes(0)

Actions
3. Re: Set Properties not Checkmarked

Scott Dunbar Mar 26, 2015 4:06 PM (in response to Michael Wu)

Hi Mike,

I tested this in 4.4 patch 7 - all seems ok.
My steps:
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.
Like Show 1 Likes(1)

Actions
4. Re: Set Properties not Checkmarked

Michael Wu Mar 26, 2015 4:33 PM (in response to Scott Dunbar)

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.
Like Show 0 Likes(0)

Actions
5. Re: Set Properties not Checkmarked

Scott Dunbar Mar 27, 2015 8:57 AM (in response to Michael Wu)

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
Like Show 1 Likes(1)

Actions
6. Re: Set Properties not Checkmarked

Fred Breton Apr 2, 2015 3:11 AM (in response to Michael Wu)

What BRPM version are you using? is it 4.6?
Like Show 0 Likes(0)

Actions
7. Re: Set Properties not Checkmarked

Michael Wu Apr 2, 2015 8:34 AM (in response to Fred Breton)

Fred, 4.4.00.07.
Like Show 0 Likes(0)

Actions
8. Re: Set Properties not Checkmarked

Fred Breton Apr 2, 2015 8:53 AM (in response to Michael Wu)

Michael Wu it seems that we have a bug in this product release. Maybe it is corrected in patch 9. Jon Thomas, Brendan Farrell, can you confirm. For sure this is corrected in 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.
Like Show 0 Likes(0)

Actions

Go to original post

Communities

Communities

Set Properties not Checkmarked

1. Re: Set Properties not Checkmarked

2. Re: Set Properties not Checkmarked

3. Re: Set Properties not Checkmarked

4. Re: Set Properties not Checkmarked

5. Re: Set Properties not Checkmarked

6. Re: Set Properties not Checkmarked

7. Re: Set Properties not Checkmarked

8. Re: Set Properties not Checkmarked

Actions

More Like This