Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

User Role mapping is the process whereby users or groups are dynamically mapped to security roles, user Role Mapping is a key step in the ERP implementation process. The completion of this work creates the framework that allows users to access the system, identifies the system components for which each user.

Data Table

Sr. No.

Current State

Action

Next State

Actors

SLA (if applicable)

1

 

Create and Approve

Approved

Accounts Assistant

NA

2

 

Forward

Pending for Approval

Accounts Assistant

NA

3

Pending for Approval

Verify and Approve

Approved

Accounts Supervisor

NA

4

Pending for Approval

Save

Pending for Approval

Accounts Supervisor

NA

5

Pending for Approval

Reject

Rejected

Accounts Supervisor

NA

6

Pending for Approval

Send Back to Assistant

Rejected for Review

Accounts Supervisor

NA

7

Rejected for Review

Forward

Pending for Approval

Accounts Assistant

NA

8

Rejected for Review

Cancel

Rejected

Accounts Assistant

NA

Note: Data given in the table is a sample data.

Procedure

Data Definition

Sr No

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

1

Current State

Text

Yes

The Current State indicates the stage at which the process of the workflow in progress.

2

Action

Text

Yes

The Action indicates the workflow in progress from one stage to another stage

3

Next State

Text

Yes

The Next State is process in the workflow when a action is completed (Example: assigning the for approval from one person to next person)

4

Actors

Text

Yes

The Actors are the different hierarchy of people with designation who are authorized for initiate, approval or rejecting the process.

5

SLA (if applicable)

Number

No

The SLA indicates the timeframe within which the action to be completed

Step to fill data

  1. Download the data template attached to this page.

  2. Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.

  3. Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.

  4. Identify all different types of grievances on the basis of ULB’s functions.

  5. Start filling the data starting from serial no. and complete a record at once. repeat this exercise till the entire data is filled into a template.

  6. Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

To see common checklist refer to the page Checklist consisting of all the activities which are to be followed to ensure completeness and quality of data.

Entity Specific Checklist

Please discuss with a relevant department head before finalizing the workflow.

Attachments

Enclosed Sample Template refer to “Role action Sate mapping” tab.

View file
nameWorkflowTemplate_V2.xlsx