Setup: Labs - Process Workflow Iterator
How to use Labs
Features in Labs are temporary. You do not need to test each feature. If your organization might benefit from a new feature and/or enhancement, go to Setup > Labs. In the list of available features, toggle the feature to On.
Some features in Labs are interconnected. You may activate more than one feature simultaneously to maximize the benefit of new Labs offerings.
As new features prove successful, SolarWinds will permanently integrate them into Service Desk. Likewise, if a feature is found to not be beneficial, it will be deleted permanently.
Enable features in Labs
-
Navigate to Setup > Labs.
ESM customers: navigate to Organization > Setup > Labs. -
In the list of available features, toggle the feature(s) of your choice to On.
Introduction to the Process Workflow Iterator
The Process Workflow Iterator allows you to create workflows that can natively iterate over a list of items stored in a custom field, for example, a JSON array. The Iterator then executes a reusable block of actions for each item.
Advanced and Premier customers can use the Iterator for many use cases, for example, in:
-
Approval processes. For each entry in a JSON array of approvers, the Iterator can initiate an approval step with the approver’s attributes referenced as
{{attribute_name}}. -
Configuration processes. For each item in a JSON array of configuration changes, the Iterator can create or update related records, referencing fields like
{{ci_id}},{{planned_start}}, and{{planned_end}}. -
Notification processes. For each stakeholder object in a JSON list, the Iterator can send a tailored notification email using
{{name}},{{email}}, and{{role}}. -
Ticket management processes. For each line item in a JSON-based request, for example, catalog items or cost centers, the Iterator can create a corresponding child incident, task, or change, using
{{item_code}},{{quantity}}, and{{owner}}. -
Runtime processes. For each defined maintenance window object in a list, the Iterator can schedule or trigger a specific action chain at runtime.
The Iterator's actions are captured in the audit log.
How it works
The Iterator looks for the JSON array that triggers the actions. For example, if you are using it for an approval process, it looks for the first approver's attributes. It then performs the action(s) identified, for example, it could notify the approver that action is required. If that is the only action to be performed, it looks for the next approver, and notifies that approver. The iterator loops through all of the approvers and performs the same action for each.
Set up a process workflow using the Iterator
-
Navigate to . . . .
-