Configures data binding to an XML schema to manage
approvals as votes.
To set up voting, you must map the approvals to the schema for your input form. XPath
indicates a repeating XML node where the children are the user ID and voting status
of an individual user, and whether the user is a mandatory approver.
Navigation
- In AgilePoint Envision, open a process template.
- Navigate to the Premier Extension stencil.
- Drag one of the following AgileShapes, and drop it on the process model:
- To view the entire list of properties, in the Design Tasks pane, click Show Properties.
- On the VotingConfiguration field, click the Ellipses button.
Field Definitions
| Field Name |
Definition |
Schema
|
- Opens the Following Window:
- Select XPath from Attributes Window
- Purpose of this Window:
- Enables you to select a schema node from the XML schema for
your process.
|
XPath
|
- Definition:
- Specifies a group of approvers that are involved at an activity.
- Allowed Values:
-
An XPath to a schema node that represents a group of approvers.
This is a parent node where the children represent individual approvers
within the group.
- Default Value:
- None
- Custom Attributes:
- No
- Example:
- /pd:my/pd:Managers
The Managers node would have child nodes for individual managers.
|
User ID
|
- Definition:
- Specifies the schema node for an individual approver. Usually this field is used
to identify a mandatory approver.
- Allowed Values:
- An XPath to a schema node that represents an approver. This node must
be a child node of the approvers identified in the XPath field.
- Default Value:
- None
- Custom Attributes:
- No
- Example:
- /pd:my/pd:ManagerID
The ManagerID node contains the name of an individual manager.
|
Status
|
- Definition:
- Specifies whether the approver in the User ID field approves or rejects the
activity.
- Allowed Values:
- An XPath to a schema node in Boolean format, such as True or False.
- Default Value:
- None
- Custom Attributes:
- No
- Example:
- /pd:my/pd:Status
The Status node contains the
Boolean value to indicate whether the
activity has been approved or rejected by an approver.
|
Mandatory
|
- Definition:
- Specifies an XPath to a schema node that indicates whether the
approver listed in the User ID field is mandatory.
If the approver is mandatory, and he or she rejects the activity,
the activity is considered rejected, regardless of the voting outcome.
- Allowed Values:
- An XPath to a schema node that represents
a Boolean value indicating whether the approver is mandatory.
- Default Value:
- None
- Custom Attributes:
- No
- Example:
- /pd:my/pd:Mandatory
The Mandatory node contains the Boolean value to indicate whether the approval by an individual manager is essential.
For example, if you specify the following values in an XML schema:
User ID: Kelly and Mandatory=True, then this indicates that Kelly's approval is mandatory.
|
Final Result XPath
|
- Definition:
- Specifies the final result whether an approval activity is approved or rejected.
This is also an Boolean value.
- Allowed Values:
- An XPath to a schema node that represents the final result
of the voting.
The final result can be stored in a custom attribute.
- Default Value:
- None
- Custom Attributes:
- Yes
- Example:
- /pd:my/pd:VotingResult
The VotingResult node stores the Boolean
value to indicate whether the activity is finally
approved or rejected.
|
Set final result as 'Approve' when _ % of the users approved.
|
- Definition:
- Specifies the minimum percentage of approvers required to consider the item approved.
- Allowed Values:
- An integer.
- Default Value:
- None
- Custom Attributes:
- Yes
- Example:
- If you have enter 60, and you have 7 approvers, at least 5 of the approvers would need
to vote Yes for the item to be approved because 4/7=57%, and 5/7=71%.
|
Common Configuration Tasks
