Controlling Default Service Orders with Role Conditions

description this article explains how to configure default service orders so they only run when users meet specific role based conditions this is achieved by adding conditions directly to the default service order configuration use case an organisation has a service called building access , which creates a ticket or process to grant users access to a specific location retail department users are provisioned with multiple default services during the create user process the requirement is the default service order should only run if the user is a member of a specific department role (e g , retail department), and is a member of a location role (e g , a retail store such as ponsonby) solution 1\ add role conditions to the default service order you can add conditions to a default service order to ensure it only applies when the user is assigned specific roles for example cppcopyeditdefaultuserserviceorder ponsonby where ponsonby is the role name for the required location if multiple roles are involved, you can include multiple conditions to ensure the service only runs when all required roles are present 2\ implementation considerations ensure the roles you reference in the condition are assigned before the default service order evaluation occurs if role assignment and default service order evaluation happen in the same process, confirm the sequence supports this dependency test in a non production environment to validate the logic before deploying example workflow identify the role names required for your condition (e g , retaildepartment , ponsonby ) edit the default service order configuration to include the role condition using the defaultuserserviceorder rolename syntax save and test the configuration to confirm the service order runs only for users who have both roles