Offboard Licenses block

Oomnitza's Offboard Licenses Workflow block allows users to remove both desktop and SaaS Licenses from a user when changes occur within Oomnitza. For example, a user's licenses can be revoked when that user's status changes to Offboarding. The workflow block is organized in 3 tabs: Information, Recipients and Message.

To create an Offboard Licenses block, complete the following steps:

1. From the menu, select Configuration> Workflows > People.
2. Click Add (+). The Begin and End blocks are automatically added to the sandbox.
3. Enter the name and a description of the workflow. 
4. Edit the Begin block. Add rules that will trigger the workflow, for example, the OffBoarding Date equals Current Date.
5. Click the Blocks tab, and drag and drop the Offboard Licenses block onto the canvas.
6. Click the Edit icon.

Information tab

In the Information tab, there are two options:

1. Desktop will remove the user from all assignments to Desktop and Desktop contracts.
2. SaaS will remove the user from all assignments to SaaS Contracts and also set the flag Delete in SaaS in the user's SaaS User record for all SaaS Software that the user is assigned to. This flag can be used to trigger individual SaaS user workflows for each of the SaaS systems such as:
   1. Deleting the user from the underlying SaaS System
   2. Do any additional user clean-up in that SaaS System like reassigning objects to different people
   3. Deactivating the user using the Archive block. 

Recipients tab

1. In the Recipients tab, enter the recipients of the notifications. You have the option to select one or more of the following:
   1. Roles: To send the notification to users by roles you can select all roles, or one or more roles. For example, you may wish to send your notification to all Employees and Administrators in the organization. 
   2. Users: To send the notification to Oomnitza users, type the names of the users that you want to be notified. The users must have been added to the People page in Oomnitza, otherwise, the usernames will not populate.
   3. Fields: Select one or more fields to send the notification to a user referenced in a field value. For example, select Created By to send the notification to a user whose email is referenced in the Created By field. When you run the workflow, all users identified in the workflow trigger (i.e. all offboarded users) with an email referenced in the Created By field will be emailed. You must make sure that the email address is valid and adheres to the proper format, i.e. [e-mail], otherwise, the notification will fail to send.
   4. Emails: To send the notification to a user outside of Oomnitza, such as someone's personal email, select Emails and manually enter the email address. Unlike the Users option mentioned in step 2, you are not limited by any email you can enter in this field. 

Message tab

1. In the Message tab, create your message. To add metadata fields, click Add Metadata.  You can create the body of the message using plain text or HTML.
2. Select the checkbox to include a list of the licenses that were un-associated with that user. That list includes the following fields: Software Name, Contract Name, Contract Type, License Key

Note
You can configure the header and footer of the email by configuring the email.header and email.footer variables in the Global Settings table. Click Configuration > General > Global Settings.

Running the workflow

1. Click Save and connect the blocks
2. Validate the workflow and Launch, so that the workflow is now live in your system.