Orchestration Template

An orchestration template is a reusable sequence of actions that the product carries out as a single unit. You build a template by connecting blocks, each of which performs one action, and the template runs those blocks along the connections you draw between them. Blocks cover Active Directory (AD), Exchange, Microsoft 365, and Google Workspace actions, along with custom scripts, webhooks, notifications, and database operations, so one template can complete work that spans the directory and the applications around it. Build a template once to define a multi-step process such as user onboarding or offboarding, then reuse it instead of assembling the same sequence each time it is needed.

How orchestration templates work

When you apply an orchestration template, it acts on the objects supplied to it, and each block reports success or failure on completion. Each outcome can lead to a different next action, so the template continues along the matching route instead of stopping, and a block's output is passed forward as a macro to the blocks that accept macro input. Execution follows the connections, including loops. A block that repeats more than 15 times in a single run stops and reports an infinite loop error.

Prerequisites

• Configure the Microsoft 365 or Google Workspace tenant in ADManager Plus before you use any cloud action block.
• Configure the webhook template, notification template, custom script, or database connection you need, so that is available for selection in the corresponding block.

Note: Cloud actions apply only to Microsoft 365 and Google Workspace users who are synchronized through directory sync.

Steps to create a new orchestration template

1. Navigate to Automation > Configuration > Orchestration Template.
2. Click the + Create New Template button.
3. Enter a suitable Template Name and Description for the template.
4. To create your own custom Orchestration Template, drag and drop the required orchestration blocks. While creating the template:
   • All blocks must be connected to the start block, either directly or indirectly through other blocks.
   • Each block can have multiple input connections, and flow arrows can be adjusted as needed to align with your logic. Appropriate action items can also be defined for both success and failure scenarios.
5. Click Save once the template has been created. If you wish to undo all the changes made to the template, click Clear to start over.

Orchestration blocks

Note: Outputs from previous blocks can be passed as inputs to subsequent blocks. These outputs will be available as macros only in the following blocks:

• Decision Based on Previous Block Result
• Decision Based on Criteria
• Custom Script
• Webhook
• Notification
• Database Operations
• Modify User
• Reset Password