This is not the latest version of Identity Director documentation.
View available documentation.

Icon

Request/Assign Another Service

Add the Request/Assign Another Service action to deliver or assign another service as part of the workflow of the current service. This makes it possible to deliver or assign dependent services automatically to qualified people.

Services can be part of a so-called "service bundle". This is a service that automatically subscribes to dependent services. With a Request/Assign Another Service action, you can build scenarios like these. For example, you can configure a service Microsoft Office Professional bundle, which installs all Office products, a service Microsoft Office Essentials, which installs only Word, Outlook and PowerPoint and a service Microsoft Office Complete, which installs all Office products including Visio. Other examples are a service bundle for a specific department or job function.

Configuration

Item

Explanation and Tips

Action Name

Optionally specify a friendly name for the action. This name must be unique in the workflow.

Request/assign

Specify whether the other service should be requested or assigned. By default, Request is selected.

  • If you select Assign, the service is delivered, but its workflow isn't executed. For example, if a business owner already approved the delivery of a number of services to end users, you can assign these services to prevent the business owner from having to approve these transactions for a second time.

Wait for delivery workflow to finish

Pause the transaction until the delivery of the specified service has been completed. This is useful if other workflow actions depend on it.

  • Clear the option to let the transaction continue, while the delivery of the other service runs in the background. Although this may result in faster delivery, it may also cause unexpected results: The transaction of the current service may succeed, even if the other service fails.
  • This option is grayed out if you selected Assign in the Request/assign field.

Expiration

Specify when the action expires. If the action hasn't been performed in time, it fails. The expiration time is only considered if you selected the option Wait for delivery workflow to finish.

  • You can use placeholders to make the expiration time for the action dynamic.
    • When the action is executed, the placeholder needs to resolve into an integer (e.g. "9"). Invalid input (e.g. "Nine") causes the action to ignore the expiration time. The transaction continues immediately.

Workflow Detail

Specify the level of detail that is shown when people track the service status. Depending on your configuration of this field, the Label field specifies the status information.

  • Select Default to show the behavior configured at Setup > Behavior.
  • Select Status only to show the status of the service.
  • Select Workflow action to show the status of the action.
  • Select Full details to show the status of the action and its actor.
  • Select Use custom label to configure a custom text.
  • This action adds an exception to the workflow. Alternative workflows are only considered if you select the option Wait for delivery workflow to finish.
  • If a Building Block is created of a service whose workflow contains a Request Another Service action, the specified service is also included.
  • If the current service contains a service attribute that is linked to a service attribute of the requested service, the value is empty: all service attributes are initialized at the beginning of the transaction. In this case, the requested service hasn't been delivered yet at the start of the transaction of the current service.
  • If the requested service contains a service attribute that is linked to a service attribute of the current service, the value is empty: the subscriber to the requested service must already subscribe to the current service before the value of its service attribute can be resolved.
See also