Integrate > Micro Focus Operations Orchestration (OO) > Automated fulfillment of request tasks > Add an OO flow link to a request task

Add an OO flow link to a request task

User roles: Request Manager, Request Coordinator

Before you can add an OO flow link to a request task, make sure that you have already enabled the OO flow automation for request tasks. For details, see Enable OO flow automation for request tasks.

You can add OO flow links to the request tasks by planning tasks in request models or directly in request records. Then, the requests will contain the request tasks associated with the OO flows that you defined.

To add an OO flow link to a request task in a request model, follow these steps:

Note If you want to add an OO flow link directly to a request task from a request record instead of request model, open the task planner from the request record.

  1. Log on to the Service Manager Web client.
  2. Click Request Fulfillment > Configuration > Request Models.
  3. Search for and open the request model record that you want to modify.
  4. Go to the Task Information section, and then click OO Flow Configuration. The OO Flow Configuration form is displayed.

  5. Select an OO flow in the Select Path field, and then click Add Link. The OO Flow Details form is displayed.

  6. Type a name for the OO flow link.
  7. Select the Execute Automatically check box if you want to execute the OO flow automatically. Otherwise, clear the check box so that you can manually execute the OO flow by clicking Execute OO Flow from the request task records.

  8. In the General Parameters section and the Secure Parameters section, complete the fields listed in the following table for each parameter as necessary.

    Field Value Description
    Parameter Name

    Name of an input for the operations of the OO flow; can be entered by the user running the flow, or set to a specific value, or obtained from information gathered by another step of the OO flow

    		 An OO field.
    Required? true or false

    An OO field that indicates whether the parameter is required or not.
    Default Value Default value of the parameter

    A custom field.

    If the Value field is not configured for the parameter, or if no value is available in the Value field, the default value is used when the OO flow is launched.

    Note This field is not the same field in OO.

    Value Type

    Available Types are:

    • Additional Properties
    • Parent File
    • Current File
    • User Options
    • JavaScript

    Select one from the drop-down list.

    A custom field.

    The value type defines where the OO flow parameter value can be retrieved when the OO flow is launched.
    Value The available fields based on the selected value type. Select one from the drop-down list.

    A custom field.

    The value of the selected field will be used to launch the OO flow.

    Note If Join Table is set to true, this "Value" is used to match the "Join Table Field" to identify the corresponding value for the specified "Select Field", which is then used to launch the OO flow.

     
    Join Table? true or false

    A custom field.

    If it is set to true, Join Table Name is required.

     
    Join Table Name

    All available table names. Select one from the drop-down list.

    A custom field.

    Select the join table name. For example, if the value type is "Parent File" (in request task planner, the Parent File is "request") and the value is "Affected Service", when the Join Table is selected, you may select the Join Table Name as "device".
    Join Table Field

    Available fields based on the selected Join Table Name. Select one from the drop-down list.

    A custom field.

    The field list of the selected Join Table. The value of this field should match the value of the "Value" field. For example, "CI Identifier" should be selected in Join Table Field if "Affected Service" is selected as the "Value" of the Parent File value type.
    Select Field

    A field other than the Join Table Field in the Join Table.

    Select one from the drop-down list.

    A custom field.

    The value of the selected field will be used to launch the OO flow when Join Table is used.

     

  9. In the Secure Parameters section, complete the fields for security parameters as necessary.

    Field Value Description
    Field Name

    Name of the security parameter

    		 An OO field.
    Required? true or false An OO field that indicates whether the parameter is required or not.
    Default Value Default value of the parameter

    A custom field.

    If the Value field is not configured for the parameter, or if no value is available in the Value field, the default value is used when the OO flow is launched.

    Note This field is not the same field in OO.

  10. Click Add. The OO flow link is added. 

  11. Click Save and Exit, and then go back to the Task Information section in the request model.

  12. Click Edit to open the task planner.
  13. Select or create a request task that is in the "Automation" task category.
  14. In the OO Flow Link drop-down list, select the OO flow link that you added.
  15. Click Save. The OO flow link is now added to the request task of the request model. The requests that use this request model will contain the request task with the OO flow link that you defined.

Related topics

Automated fulfillment of request tasks

Add an Operations Orchestration integration

Enable OO flow automation for request tasks

Execute an OO flow from a request task