about us      downloads      documentation      contact      home 
 products
 antHR
 workflow studio
 technical toolkits
 content entry
 workflow
 security
 hierarchy
 concepts
 how tos
 reference
 FAQs
previous: Line management  next: Adding extra notifications

How to: Multiple user workflow authoring - Changing the approver

  Step 1 : Summary
  Step 2 : Creating users
  Step 3 : Line management
  Step 4 : Changing the approver
  Step 5 : Adding extra notifications
  Step 6 : Next steps

Change the responsible user for the approve/reject activity - (page 4 of 6)

Level: intermediate
Required reading: Simple workflow
Recommended reading: Managing staff, Managing relationships

In this step we will change the user who approves the holiday request. First double click on the holiday request workflow in the hierarchy, this will bring up the workflow editing view.

Then double click on the activity that represents the Yes/No question within the workflow. The "Edit properties" dialog is shown.

At the bottom of this dialog is the "Responsible" field. This field represents the user who is responible for this activity.
Right click on this field and select "Relationship", and the "Select responsible" dialog is displayed.

Select "Relationship type" to be "Line management" as we are interested in selecting the line manager of the requestor.
Select "Relationship direction" to be "B to A". This specifies that the requestor represents person B in the relationship and we want user A. If we specified "A to B" we would get the reports of the requestor rather than the manager.
In "User" enter "Creator", as we want to get the manager of the person who created this workflow (ie requested the holiday).
Finally in the default user, select "DB/Ann" as she is the CEO in our example so approves all holiday for anyone who does not have a manager specified.

See responsible script for more examples of how to use the "Responsible" field.


 

Did you find this article helpful? Comments on this page are welcome and can only help us improve the quality of our documentation.
© Ant Organisation Ltd, 2003