Functional positions allow you to access the Person information for individuals who have been assigned to these positions. You can access this information both for the default functional positions, and for those that have been configured for a particular implementation.
Functional positions are defined through the module selection Organization Designer > Functional Positions. Each functional position is associated with a particular entity—this may be a service, a service group, or an organizational unit.
Once the position has been defined, you may assign a person to the position through the Positions page for the organizational unit, or on the General tab for the service or service group. Some sample usages include:
Use Requisition.Customer.HomeOU.BudgetManager.Email to access the email address of the Budget Manager of the customer’s home organizational unit.
Use Performer.HomeOU.ParentOU.Manager.FirstName to access the first name of the Manager of the parent organizational unit of the task performer’s home organizational unit.
Default functional positions may have spaces in the position name, for example, “Budget Manager”. The space is omitted with the functional position is used within a namespace reference.
User-specified functional positions may not include spaces. The namespace reference must prefix the functional position with the keyword “Position” as in the following example:
#Service.ServiceDefinition.Position.EscalationManager.Email#
For all of the functional positions, you have access to all the variables defined in the Person table above. If no person variable is included, the expression returns the person’s database ID.
You can access information about Home OU, Parent OU, or Client OU functional positions from any person role that you can access in either the Requisition or the Service context. Information about Service and Service Group functional positions is only available in the Service context.
When using these expressions to include dynamic data in emails and task names, you must add the pound separator (‘#’) at the beginning and end of the expression, for example:
#Customer.HomeOU.Manager.Email#