Each user is assigned an approval level. Each service that requires approval is also assigned an approval level. When a service uses an Approval Process of “System approval process,” the approval level assigned to the service determines how high up the management hierarchy subsequent approvals should go. You can add to and alter the list of approval levels.
Note: Once an added approval level numeric value is used, it should not be removed from the list.
For more information on approval processes, see the Integration Guide.
The approval level values are maintained in a file named approval_shared.xml. This file can be different based on the language chosen for the system and will be located in a different folder for each language. For example, for English (icusen), the approval_shared.xml file is located in the %USM_HOME%\view\webapps\usm\locale\icusen folder.
The approval_shared.xml file looks like this:
<?xml version="1.0" encoding="UTF-8"?> <shared> <approval_level> <option value='0'>Level 0</option> <option value='10'>Level 10</option> <option value='20'>Level 20</option> <option value='30'>Level 30</option> <option value='40'>Level 40</option> <option value='50'>Level 50</option> </approval_level> </shared>
You can edit this file to add values or change the spelling of existing values.
To add an approval level
Example
To add a new approval level named “Director,” alter the approval_shared.xml file as shown below in bold.
<?xml version="1.0" encoding="UTF-8"?> <shared> <approval_level> <option value='0'>Level 0</option> <option value='10'>Level 10</option> <option value='20'>Level 20</option> <option value='30'>Level 30</option> <option value='40'>Level 40</option> <option value='50'>Level 50</option> <option value='51'>Director</option> </approval_level> </shared>
| Copyright © 2010 CA. All rights reserved. | Email CA Technologies about this topic |