Welcome to my site. I started this site as an online archive for me and all things virtual. I kept getting requests for help around some of the more standard issues we all hit in dealing with Cloud automation, particularly around the VMware vCloud Stack so I decided to make my forum public...and here we are.

My name is Lee Friend and I'm based in London, UK. I am a Cloud orchestration specialist in the end to end management, automation and integration of virtualisation stacks covering all pieces of the puzzle from IPAM (InfoBlox / QIP / IP Control), DNS, AD, resiliency & DR (SRM automation), management system integration (including ServiceNow, BMC Remedy, ticketing systems) and on and on.

Having worked since the very early days of virtualisation, I specialise in the vRealize suite (vRO,vRA,vCD,vR OPs,vCloudClient,SRM,and on) with the aim of orchestrating wherever it's needed. I have helped out large financials, global exchanges and cloud service providers at an architecture level all the way through to workflow engineering.

Edit library worflows and actions

All topics related to VMware vCenter Orchestrator / vRealize Orchestrator
Site Admin
Posts: 30
Joined: Sat Dec 20, 2014 4:45 pm

Edit library worflows and actions

Postby leefriend » Mon Mar 21, 2016 2:18 pm

Before we start, editing library workflows and actions should only be undertaken as a last resort as these may potentially get updated with later releases from the plug-in vendor. The preferred approach is to duplicate the workflow / action and reference the duplicate from your workflows.

As such, whatever changes you make are completely at your own risk! Be warned and be careful!!!

Anyway, that said there are occasions that duplication may not solve your requirements. If so...
We need to edit the vRO database. The example shown is for Microsoft SQL but the principal is the same when using the embedded database.

1. Locate the workflow / action:
- workflows are in the VMO_Workflow table
- actions in the VMO_ScriptModule table
i.e. Example is for updating a workflow's access; simply replace the table name with VMO_ScriptModule for actions.

Update by workflow ID found in the vRO client or API (preferred)

Code: Select all

SELECT * FROM VMO_Workflow w WHERE w.name = 'my_workflow'

or by workflow name (make sure only a single workflow is found) i.e.

Code: Select all

SELECT * FROM VMO_Workflow w WHERE w.id = 'workflow_id'

2. Update the allowedOperations column
i.e. By workflow ID (preferred)

Code: Select all

UPDATE VMO_Workflow SET allowedOperations = 'vef' WHERE name = 'workflow_id'

or by name i.e.

Code: Select all

UPDATE VMO_Workflow SET allowedOperations = 'vef' WHERE name = 'my_workflow''

Reload (F5) the vRO client and the workflow or action will now be editable.

To set back to read only use the same update procedure but allowedOperations = 'vf'

Happy days.

Return to “Everything vCO / vRO”