Using workflows to create relationships in BMC Helix ITSM: Smart IT
This use case describes a sample workflow for setting up relationships between two work orders. It considers a service request for a new employee to order a laptop and laptop case. The laptop and laptop case are represented as individual work orders. The example illustrates the workflow with two work order actions: Create Work Order ID1 and Create Work Order ID2.
To create relationships between BMC Helix Digital Workplace Catalog and BMC Helix ITSM: Smart IT
1. Add the Service Broker Context and Text variables to map questions to relevant fields in the work orders.
2. Add two Create Work Order with Identifier actions on the canvas and map your questions to the relevant fields.
In the following example, the shipping destination is added to each question response:
3. Create relationships between work orders by adding the relevant data to the WOI:Associations form. To do so:
Populate the Build Input Set action with the values in the table.
For each field, use the database name from Developer Studio and put the key and values into double quotes.
Key (1-7) | Value (1-7) |
---|---|
Form Name01 | WOI:WorkOrder |
Request ID01 | <Create Work Order with ID1><Output><Work Order ID> |
Request Type01 | Work Order |
Request Description01 | <Context ><Service><Service Name> |
Form Name02 | WOI:WorkOrder |
Request ID02 | <Create Work Order with ID2><Output><Work Order ID> |
Association Type01 | Related to |
- Populate the Create Entry action by adding the output to the Field Values key and Process Correlation ID to the Correlation ID key.
4. Add the Receive Task action to wait for a signal from one of the work orders.
5. Add two Track External Activity actions to capture a Completed or Cancelled status from both work orders in BMC Helix ITSM: Smart IT. For each Track External Activity action, use the relevant work order ID variable from the Create Work Order with Identifiers actions. The Track External Activity action is only supported with BMC Helix ITSM applications (Incident, Work Order, Change, SRM Request).
The following table illustrates the parameters for the Track External Activity action:
Parameter | Value |
---|---|
Request ID | SB Context -> Service Request -> Service Request ID |
Process Correlation ID | General -> Process Correlation ID |
Connection | Connection |
Internal Connection Id Expr | Blank |
Sub-Catalog External ID | Blank |
External Activity Type | WOI:WorkOrder |
External Activity ID | Created Work Order with Identifier -> Output -> Instance ID |
External Activity Display ID | Created Work Order with Identifier -> Output -> WO Number |
6. Add an exclusive gateway with two conditions on the Expression for Condition page:
The first condition completes the service request if both work orders are completed.
Use the Activity Sub Status variable from the Track External Activity1 and Track External Activity2 actions.
- The second condition cancels the service request if one of the work orders is canceled.
7. End the workflow by using the Set Service Request Status action that will reflect the Completed or Cancelled statuses.
8. Add questions to the workflow.
In the following example, conditional questions are set up that will automatically select the relevant laptop case depending on the type of laptop.
9. In the
BMC Helix Digital Workplace
end user console, open the service request, select a laptop type, and submit the service request:
10. In BMC Helix ITSM: Smart IT, select Console > Ticket Console. Both work orders are created in BMC Helix ITSM: Smart IT.