Form template and form policy field mapping
A general outline of mapping is noted below. Mapping with workflow policies requires a strong understanding of the Process Engine.
Document Policy
Part of the document policy includes mapping rules between published form template cells and form data properties. If the name of a published cell is identical to the form data subclass property name, then mapping automatically occurs when the document policy is created. If the published cell name does not have a corresponding name or you want to edit an existing mapping, then you can manually map form template cells to form data properties when you create the document policy.
Workflow Policy
Workflow Policies include mapping rules between published form template cells, workflow data fields, and form data properties. If the name of a published cell is identical to the name of the workflow data field or the form data subclass property name, then mapping automatically occurs when the workflow policy is created. If the published cell name does not have a corresponding name or you want to edit an existing mapping, then you can manually map form template cells to workflow fields and form data properties when you create the workflow policy.
Fields
You can choose which cells on the form to publish so that mapping with custom form data document subclass properties is enabled.
When mapping steps in a workflow to a workflow policy (depending on which processor is used), both built-in and custom fields are available.
When mapping between properties of a document class/entry template and a form template, both built-in and custom fields are available.
When mapping between router regions and a step processor, only specific fields are available. If you are designing a form for a workflow policy and you want to include router information, you can draw workflow data fields on the form such as:
- F_Subject (string): the name of the workflow .
- F_StepDescription (string): a description or instruction for the step.
- F_Deadline (date): the date and time that this work item is due.
- F_Reminder (date): a message triggered by the deadline if the work is overdue.
- F_StepName (string): the name of the current step.
- F_Comment (string): initialized to null every time the work item moves to the next step; allows the users participating in a step to share information about the step; comments can only be viewed from the Tracker window.
Feedback