Role: 00000168

Abbreviation: Manager

• ORG_OBEJCT (reference field RHOBJECTS-OBJECT )

• OType (reference field OBJEC-OTYPE ) and ObjId (reference field OBJEC-REALO )

All three role parameters are elements in the role container. The contents of ORG_OBJECT are evaluated with priority. If ORG_OBJECT is not passed, the role parameters OType and ObjId are evaluated.

• ORG_OBJECT contains either the specification of a person, a position or an organizational unit in the composite form P <8-digit number> , S <8-digit number> or O <8-digit number> , or the specification of a user in the composite form US<12-character user name> .
• OType (reference field OBJEC-OTYPE ) contains the ID of the object in a 2-character field. The following are allowed:

• ObjId contains either the number of the person, position or organizational unit, or the user name in a 12-character field.

In the demo example, the role is used to find the superior of the initiator of the workflow starting from the initiator. The user name of the initiator is stored in a 14-character field with reference to RHOBJECTS-OBJECT in the element _WF_Initiator of the workflow container. The binding is therefore defined to the element ORG_OBJECT of the role container for the relevant step.

The company's organizational plan is evaluated during role resolution. This takes into account either direct reporting structures between positions (position "reports to" position, relationship A/B002 ) or the designation of chief positions (position "manages" organizational unit, relationship A/B012 ) in the organizational units.

The relevant relationships must have been created at the appropriate points when the organizational plan was set up.