| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
Yes, you can edit an already published workflow. From Automation >> Workflows, open your workflow in the Workflow Designer, edit it and save it as a draft while making changes. The older version of the Automation workflow will continue to apply on the tickets to which it has already applied, or to any new matching tickets created while the Workflow is in a Draft state. Once you complete making all the changes, publish the Automation workflow again. Once published, the latest version of the workflow will apply only to new tickets created after the workflow is published.
When relating a
Ticket Process Workflow with an Automation Workflow why do I notWorkflow Service as part of Automation Fulfillment, where can I see the Input Parameters listed?
When you are adding an Automation Workflow into a Ticket Workflowskill, you are able to can see your custom workflow in the list of Workflow Services but the Input fields do not show up. The described behaviour is visible in the screenshot below.
This is happening because the Start Activity Data of your Automation Workflow has not been defined. Follow the steps mentioned under Create an Automation Workflow>>Defining the Start Activity Data. For a custom or newly created workflow, if Start Activity Data is not defined then the input parameters defined in Automation Workflow will not be mapped with parameters of Ticket Process workflow. You have to add New/custom workflow's mandatory fields in Start Activity and Json Schema as well. JSON schema does the validation of inputs for a workflow service. This issue is not observed in OOTB workflows because this step is already done for these workflows. . Based on the selected workflow service, you need to specify the mandatory input parameters as shown below.