Joiner Mover Leaver QuickLink, Form and Workflow XML Files Required for Contractor Employees

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Even though we have achieve Joiner Mover Leaver QuickLink, Form and Workflow Required for Contractor Employees using Rapid Setup but this is a very specific client requirement they want this customization.

Could you please help me in providing Joiner Mover Leaver QuickLink, Form and Workflow working xml files for Contractor Employees ?

2

Hi @manikandaprabhu_cg ,
Please go through this 8.4 IdentityIQ Rapid Setup Guide - Compass (sailpoint.com). it will be helpful to you.

3

Hi,
you dont need active the rapidsetup for contractor, if it is active, it is active for all types of identities. It depends on the configuration. In global configuration of RS, for each operation you can configure the starting conditions for joiner, mover and leaver, so you can include all type of IDN or dont check the type.

About Quicklink, form and workflow what are you referring to?

4

@manikandaprabhu_cg You can check files under

IIQ\WEB-INF\config\rapidsetup\rsworkflows.xml

You have to customize this workflow. logic should be around.

identityName should be not null then it coming through trigger. So you can create a quicklink that will launch this workflow, in this flow identityName should be null.

  • You can create a form to select identity
  • build identity Model
  • on submit follow the same flow.

For IdentityModel Look for this thread,

How can I create quicklink to search identity exist in sailpoint - IdentityIQ (IIQ) / IIQ Discussion and Questions - SailPoint Developer Community

Check if that works.

6

First I need to create a quick link, second should fill a form like Employee Details like Name, Status and then based on certain criteria Joiner, Mover and Leaver workflow should trigger and provisioning should be happening for Contractor Employees. Certain Criteria also should be filled in a form

High Level Process

  1. Department Admin logs into SailPoint and creates a contractor record (based on contractor type) using the SailPoint form (Contractor Form screen will be shared).​
  2. SailPoint sends a work item/notification to the Line Manager for approval.​
  3. Line Manager evaluates and verifies the requested data:​
  • If the request is rejected, SailPoint notifies the Department Admin team with rejection comments.​
  • If the request is approved, SailPoint triggers the joiner flow for the new user.​
  1. SailPoint generates a User ID, email ID (unique value based on business logic and contractor type), and a password based on password policy.​
  2. SailPoint creates AD and Azure AD accounts with the default values.​
  3. SailPoint assigns roles and birthright access based on the employee code/number.​
  4. SailPoint updates the HR database with the generated User ID and email ID.​
  5. Email notifications with the generated user credentials are sent to the Department Admin and Line Manager​
  6. Audit record will be created in Sailpoint​
7

@manikandaprabhu_cg we can design like below,’

a. Keep Joiner WF will handle from Point 4 to 9. So we have common process for Joiner.

b. For Point 1 to 3, I will create custom WF, that will be handle
- Quick Link
- Form to Create Contractor Record as new user attribute
- Approval
- Once approved, refresh that identity with process event check → it will kick the joiner trigger.
- Your joiner should handle all BR roles as per need for Contractor.

Let me know you need more insight.

Thanks,
Pravin

1 Like
8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.