Return
-
Title
HOW TO: Triggering an Automation Workflow and passing parameters via custom scripts or the Active Roles ADSI Provider -
Description
How is it possible to pass a parameter to an Automation Workflow and start it via a custom script or the Active Roles ADSI Provider? -
Cause
Defect ID 303434 has been created to add this information into the Active Roles SDK. -
Resolution
Triggering an unparameterized Automation Workflow that is very simple. Using any Active Roles client or the Active Roles ADSI Provider, write a TRUE value to the boolean triggering named edsvaStartWorkflow
For example, this simple PowerShell script leverages the Active Roles ADSI Provider in order to set this value:
$Workflow = [adsi]("EDMS://CN=TestWorkflow,CN=Custom,CN=Workflow,CN=Policies,CN=Configuration")$Workflow.edsvaStartWorkflow = $TRUE$Workflow.SetInfo()Passing a parameter to an Automation Workflow requires passing a value to the edsvaWorkflowRunParameterValues attribute.This attribute requires a string value formatted as XML.For example, the following PowerShell script will pass the value Go to a parameter named TestParameter and trigger the Automation Workflow:$workflowParams = @"<RunParameterValues xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:schemas-quest-com:ActiveRolesServer:WorkflowParameters"><RunParameterValue name="TestParameter" syntax="String"><Values><Value isEncrypted="false"><RawValue>Go</RawValue></Value></Values></RunParameterValue></RunParameterValues>"@$Workflow = [adsi]("EDMS://CN=TestWorkflow,CN=Custom,CN=Workflow,CN=Policies,CN=Configuration")$Workflow.edsvaWorkflowRunParameterValues = $workflowParams$Workflow.edsvaStartWorkflow = $TRUE$Workflow.SetInfo() -
Change Request
303434