Skip to main content

 

 

 

Template:OutSystems/Documentation_KB/Breadcrumb_New_Layout

 

 

Template:OutSystems/OSLanguageSwitcher

 

 

 

OutSystems

How to set up the end users hierarchy

The goal of this document is to guide IT users through the setup of the end users hierarchy in Workflow Builder.

When building the workflow app, the Workflow Builder users can assign tasks in the workflow to specific roles. For example, one employee acting as a requester, and a manager acting as an approver. They have to inform you about the roles they created so that you could create them hierarchically in LifeTime.

Workflow Builder generates for each app a set of groups, roles, and sample users (in the development environment only) that you need to use for the user and access management. The roles and groups generated are associated with each application and have the following structure:

Roles
<AppName>Requester
<AppName>Operator
<AppName>Administrator
Groups Roles in group Sample users in group
WB | <AppName> | Requesters <AppName>Requester Requester
WB | <AppName> | <GroupName> <AppName>Operator <GroupName>
WB | <AppName> | Administrator <AppName>Administrator Administrator

The <AppName>Administrator role enables an end user to manage all the request and tasks of the app, by doing the following:

  • See every request and associated task, and check for assignment warnings, for example a task is assigned to a group without any users.

  • Reassign tasks to themself or to another user belonging to group assigned to the task.

Using the example of an Expense Approval app with validation with the procurement and finance groups, the roles, groups, and sample users created in the development environment are:

Roles
ExpenseApprovalRequester
ExpenseApprovalOperator
ExpenseApprovalAdministrator
Groups Roles in group Sample users in group
WB | Expense Approval | Requester ExpenseApprovalRequester Requester
WB | Expense Approval | Procurement ExpenseApprovalOperator Procurement
WB | Expense Approval | Finance ExpenseApprovalOperator Finance
WB | Expense Approval | Administrator ExpenseApprovalAdministrator Administrator

Configuring the hierarchy integration

To configure the hierarchy integration you need to use the Case_Configurations_API from Case Management Framework.

  1. Use the ImportUserHierarchy_GetSample API to get the template you need for importing data.

  2. Use the UserHierarchy_Import method, to bulk import the user records you need, by mentioning those users.

  3. Use the ImportUserHierarchy_GetStatus method to return the status of the bulk operation and errors, if any.

  4. Click on the Enable hierarchy switch to enable the end users hierarchy capability.

    Users governance model