VMware

vRealize Orchestrator – Configuration element

Hi everyone,

We are currently using workflows and configurations elements. I have a use case to do a loop until a configuration element value is not what it is intented.

So I would like to know if it is possible to get a value of a configuration element, if it not intented, do a retry after 1 hour. I know how to do this, but it seems impossible to get the changed value of the configuration element until I stop and restart the workflow.

Ex:

Try to get configuration element value X, I should have Y value, but I receive Z value.
I will do a retry in 1 hour, in the same workflow.
I manually change the value for Z in the configuration element.
After 1 hour, the workflow try to get the configuration element value, but still get Z value. Why ? If I cancel and start that workflow again, I get the “Y” value…


View Reddit by X3nOnQCView Source

Related Articles

2 Comments

  1. vRO initially loads the values of the Config Element “as is” into the workflow state and only works from there. You need to refresh the config element after you’re hour sleep, I forget what the exact name of the method for the object is but just use the API explorer in the vRO client and look at the configuration element object and you should see it.

  2. > but it seems impossible to get the changed value of the configuration element until I stop and restart the workflow

    How are you reading in the config element? If you’re just bringing in the value as an attribute, see /u/killamongaro259’s comment.

    Otherwise, if you’re reading it in via **configElement.getAttributeWithKey(*keyName*)** or something, try a **configElement.reload()** before where you’re reading the value.

Leave a Reply

Your email address will not be published. Required fields are marked *

Close