Resource Element when updated in Machine Provisioned stub not reflected in main workflow

[EdSp]

Hi,

We have an issue with Resource Elements. In summary:

We have a main workflow that creates and saves a Resource Element. It then kicks off a vRA request to provision a VM. It will wait for that request to finish.

During VM provisioning, a workflow stub "Machine Provisioned" reads that element and modifies it.

Once the stub is done, the main workflow continues. It reads the Resource Element and sees the "old" values!

Reading the Resource Element manually in the vRO Client shows the modified values...

It's very strange. Does vRA have an execution context or something???

Thanks,

Ed

[iiliev · Accepted solution]

Hi,

Resource element's content is cached so that's probably the reason you see the old values.

Recently we added a new member method .reload() to resource element scripting object that refreshes/reloads the content. Another option for existing vRO versions is to obtain a new instance of the resource element scripting object once the stub workflow finishes (presumably it will have up-to-date content).

[EdSp]

UPDATE:

We redesigned a bit so that we didn't have to use the workflow stub for the update.

It is now added to the main workflow and it works properly as expected.

Thanks,

Ed

[EdSp]

Thanks Ilian!