Add New Role Ticket Tree

Portal User Guide › Role Definition Tickets › Add New Role Ticket Tree

Add New Role Ticket Tree

This process is started by the manager who made the Self-Service request (the Self-Service Manager). When an instruction to begin an Approval Process is given, the CA RCM generates a hierarchal Approver Process ticket tree. The Self-Service Request a New Role Definition (Add New Role) task tickets are generated in stages.

1: Select Accountable: A Task ticket sent to the Self-Service task manager.
2: Role Approver: An Add Role ticket sent to the Role manager.
3: Link Approval Process sub-trees: One Link Entity-Role parent and one Link Entity-Role approver ticket for each request made during the original Self-Service task. The parent ticket is always assigned to the Role manager.

The Add New role ticket tree is constructed as follows:

Stage 1:


Ticket			Description
Approval Root ticket			This ticket is identical to other Approval Process Approval Root tickets. For more information see Self-Service Approval Root Ticket
	Self-Service Main Request Parent Ticket		An Add Role parent ticket sent to the Self-Service task manager. For more information see Role Definition Main Request Parent Ticket
		Select Accountable	A Task ticket sent to the Self-Service task manager. For more information see Select Accountable Ticket (Add New Role).

After the Self-Service task manager has selected a person who will be accountable for this role (stage 1), stage 2 begins and a new ticket is generated:

Stage 2:


Ticket			Description
Approval Root ticket			Same ticket.
	Self-Service Main Request Parent Ticket		Same ticket
		Select Accountable	This Task ticket has been completed and is currently archived
		Approver Ticket	The Role Approver ticket. This is an Add Role approver ticket. It is sent to the Role manager. It contains all the requests to add a link between the new role and other entities. For more information see Role Approver Ticket (Add Role).

Note: If the role manager rejects the request submitted in the Role Approver ticket, the Approval Process ends and the relevant emails and info-tickets are generated.

After the Role manager has approved the enrollment of all the users in the Approver ticket, stage 3 begins and a new set of tickets is generated.

Stage 3 (Includes examples of possible Request sub-trees for an Add Role ticket tree):


Ticket				Description
Approval Root ticket				Same ticket.
	Self-Service Main Request Parent Ticket			Same ticket
		Select Accountable		This Task ticket has been completed and is currently archived
		Approver Ticket		This Role Approver ticket has been completed and is now archived
		Self-Service Request Parent ticket		A Link User-Role parent ticket
			Approver Ticket	Only one ticket. A Link User-Role approver ticket
		Self-Service Request Parent ticket		A Link Role-Resource parent ticket
			Approver Ticket	Only one. A Link Role-Resource approver ticket

The number of Link User-[Entity] sub-trees depends on the number of role-entity requests that were originally submitted. If a request was made to enroll 10 users to a role, then there will be 10 Link User-Role subtrees generated during the third stage of the Add New Role Approval Process.

The Link Entity-Role parent and approver tickets are standard tickets.

More information:

Introducing the Requests Table

Self-Service Request New Role Parent Ticket

Self-Service Request New Role Approver Ticket

Email CA Technologies about this topic