ROC - Update String Parameter in RA 5.5.2

[Anon Anon]

Hi,

 

I have a problem with the "ROC - Update String Parameter" action and i didn't find an answer in the community (i'm sorry if it already exists) !!

I would like to change the value of a parameter (Release ID) but it doesn't working

 

In the field "Parameter Name", the description is -> Name of the parameter (use the "Full Path" attribute of the parameter like it appears in the ROC)

But I don't know where to find this "Full Path" so i put :

 

Parameter Name [String]

Application Parameters/Common/Initialise by Flow/Release ID

 

Parameter value [String]

XXXXXXXX

 

Step Name [String]

Purge Artifacts

But it doesn't working and i have this error :

Failed to update parameter [Application Parameters/Common/Initialise by flow/Release ID].

Reason: [Cannot find parameter [Purge Artifacts/Application Parameters/Common/Initialise by flow/Release ID].]

But i promise that my parameter really exists and has no value

i don't understand ...

Thanks for your help

Best Regards

Romain (France)

[Gregg Stewart]

What is the scope set to for your variable? If it is Internal then maybe you can try using the action: Set Parameter Value - String

If that doesn't work, isn't what you want, or is not an parameter with its scope set to "Internal" then a screenshot showing the structure of the parameter (as seen in the processes -> parameters screen) might help.

 

Cheers,

Gregg

[Billy Keefer]

I think this action is a holdover from pre 5.x and not valid for 5.5.2.  Also, Release ID is a built in parameter and its value is provided by Release Automation.  You will not be able to update it.  Could you please explain (as per Gregg's comment) what you are trying to achieve and we can go from there

 

[Anon Anon]

Hi Gregg and Billy,

 

Thanks for your answers

 

In my process, i'm using some flows only from Shared Components :

 

 

 

I don't want to update the "Release ID" from Built-in Parameters (i know it's not possible) but the "Release ID" that i created in "Application Parameters/Common"

 

 

And i don't understand because it doesn't working :

 

 

Thanks for you help

 

Best Regards

Romain

[Billy Keefer]

Romain just use the “Set Parameter Value – String” action.

 

regards

[Anon Anon]

I would like to use the "Set Parameter Value – String” action but it's not possible because when you're in "Shared Components", you don't see the Application Parameters

 

 

So i wanted to use the "ROC - Update String Parameter" action

 

Thanks

 

Regards

Romain

[Michael Gebhardt]

I'm not sure if this is even possible by design, as shared components should be application independent, so I would also assume, that you're not able to use somethings like the update string parameter. I guess that the same goes for template parameter, but I'm not sure as we didn't use it this much yet

[Michael Gebhardt]

another thing. did you try setting your "Release ID" parameter to a "user input" one?

[Gregg Stewart]

This is an old thread, but it was recently found by someone experiencing the same problems. The problem/solution is described here: Actions meant to update parameters using e.g. ROC - CA Knowledge 

 

User Input is one of the conditions imposed when using that action. 

[StephaneFR]

I'm facing the same issue on a standard component (not shared). It's impossible to update a release parameter defined in the "Application parameters". Howerver, it works with a release parameter at component level.

I have opened a case (00146187) and the support (after 2 monthes...) said me that it is not supported by design !!!

[Michael Gebhardt]

what do you mean with release parameter? when it is a built-in one, than yes, that's impossible. but if it is a application parameter you defined yourself, it should be possible. we're using it quite often, that we're setting application parameters for processes with the "roc-update string parameter" action

[StephaneFR]

I mean a parameter defined by myself (not built-in) with scope "Release" (not Internal, not Environment, not User input, but Release). The action wich fails is "ROC - Update String Release Parameter" used in a Pre-plan step.

[Michael Gebhardt]

mhm ok, but from my understanding (just by the name) I would assume, if you use "Release" as scope, you would need a running deployment and not just the pre-plan phase, where you create the deployment plan. so it would make sense, that it isn't supported by design

 

but again, this is just wild guessing from my side :-)

 

(and we're always using "user input", don't know if this might be an issue as well)