jnc38
Contributor
Contributor

Dynamic Resource Element creation

Jump to solution

Hi,

I'm  using ResourceElement within actions to log some informations that needs to be kept (not temp file, neither in cache)

Using Server.createResourceElement(resourceElementCategory, resourceElementName, null) which works fine.

The problem is when integrating thoses actions into a single workflow. Within the same workflow run, if the ResourceElement have just been created, I won't be able to retrieve them by parsing their ResourcElementCategory (using Server.getResourceElementCategoryWithPath(path))

is there a way to "flush" ResourceElement?

or am I doing something wrong?

1 Solution

Accepted Solutions
cdecanini_
VMware Employee
VMware Employee

Instead of using an action use a workflow and start it as an asynchronous or nested workflow.

What happens is that the resourceElement is saved when the workflow finishes.

I have opened feature requests to have this being improved in next versions of vRO.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter

View solution in original post

2 Replies
cdecanini_
VMware Employee
VMware Employee

Instead of using an action use a workflow and start it as an asynchronous or nested workflow.

What happens is that the resourceElement is saved when the workflow finishes.

I have opened feature requests to have this being improved in next versions of vRO.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter

View solution in original post

jnc38
Contributor
Contributor

Thanks for the info, it's working fine!

0 Kudos