Approval server supporting forms
A set of standard forms and related workflow objects are installed along with Approval Server. Most objects are named with the prefix "AP,". Sample application objects are named with either "AP-Sample" or "AP-Sample2." The standard forms are described in more detail in Adding approvals to an application and Approval server administration forms. The following table introduces some of the basic forms for easy reference.
| Form | Description |
|---|---|
| Approval Central | See Approval Central and Processing approval requests. |
| Detail form | All data about an approval request are stored in the AP:Detail form. You can use this form to determine the status of a request and to see a history of activity on the request for any approval process. |
Signature form | All data about signatures associated with an approval request is stored in the AP:Signature form. Administrators can use this form to review the responses to a request. You should modify signatures only through Approval Central. |
Detail-Signature form | The AP:Detail-Signature join form joins data from the AP:Detail and AP:Signature forms. You link this form to your application's approval request form to create a three-way join form when you add approvals to your application. |
Approval request form | Any application that uses Approval Server must have an approval request form that users open to enter their approval requests. For example, in the sample applications, the application request forms are AP-Sample2:Get Agreement and AP-Sample:Lunch Scheduler. |
Three-way join form | When you link your application to Approval Server, you must create an inner join form by linking your application request form to the AP:Detail-Signature form. Because the AP:Detail-Signature form is also a join form, this join is referred to as a three-way join. For example, in the Get Agreement sample application, the three-way join form is AP-Sample2:Issue Detail Signat. It joins AP-Sample2:Get Agreement with AP:Detail-Signature. If you change the status of a request from an application's three-way join form, the change is not reflected immediately on Approval Central. Users must click a link on Approval Central or refresh the page to see the change. To make such a change visible automatically, application developers must provide a workflow that sends the refresh event to the Approval Central form on the Modify or Close event of the three-way join form. Without such a workflow, the Approval Central form does not know about changes to a request because the status change activity does not occur on the form. |
More Information form | The AP:More Information form stores and displays More Information requests and responses that pertain to the related approval request form. |
Signature authority form | For Parent-Child and Level process types, you create a signature authority form to define the relationships between approvers or levels. For example, the Lunch Scheduler sample application uses the AP-Sample:Signature Authority form. |
Application Pending form | The Application Pending form stores commands from any Application-Command process. Whenever an Application-Command process runs, AR System creates a request in this form that contains details about the command. The Application Dispatcher retrieves commands from this form and passes them to the Approval Server for processing. If the Application Dispatcher is not in use, the Approval Server retrieves commands directly from this form. |
Comments
Log in or register to comment.