Either eForm page properties must define Approval User = DA, or the User query must be disabled.

User SD enters valid data, then clicks "Submit".

A message indicates success and asks if User SD wants to create a new Document.

User SD chooses "No", and the Submitted Document is rendered as readonly with only New and Print operations.

Document Status changes to Pending Approval.

User DA logs on, opens the eForm Manager, uses the "My Approval Documents" query find User SD's data entry Document containing SDE Form 1, then opens the Document.

Note that as an Approver, DA can edit data. Approve and Reject buttons are added.

From here, the Approver can Approve or Reject in accordance with the Conditions for Document Approval (see Document Approval and Rejection in the eForms Document Reference). Status transitions occur as described in the eForms Document Reference.

Either the eForm page properties must define Approval User = DA, or the User query must be disabled.

User1 logs on, opens the eForm Manager, then creates a new Document using DDE Form 1.

User1 enters valid data, then clicks "Submit".

A message indicates success and asks if User1 wants to create a new Document.

User1 chooses "No", and the Submitted Document is rendered as readonly with only New and Print operations.

User2 logs on, opens the eForm Manager, and finds User1's DDE data entry Document containing DDE Form 1.

After selecting the Document, a dialog asks if he wants to perform Second Data Entry.

Choosing Second Data Entry loads the Document as it did for User1. The Document Panel shows the status as Submitted/Pending, i.e., User1 Submitted it, and it's Pending for User2. The # symbol is appended to the Document Id, indicating that a Submit was previously done on this Document.

User2 enters a data value that conflicts with User1 (inducing a discrepancy), then clicks "Submit". Note that some values may always cause discrepancies, such as a Date Field.

As was the case with User1, "Submit" validates the fields, and a message indicates success and asks if User1 wants to create a new Document. User2 chooses "No", and the Submitted Document is rendered as readonly with only New and Print operations.

Because DDE Form 1 was configured to not provide discrepancy alerts to User2, User2 has no idea if he matches User1's data.

User DR logs on, opens the eForm Manager, uses the "My Reconciliation Documents" Query to find the Document, then opens it.

The Document opens in reconciliation mode. the discrepancies outlined in red, and described in the Review Panel at the right.

For each discrepancy, the Review Panel provides these choices:

User DR can also Acknowledge the discrepancy (in which case, presumably the Approver deals with it). Note that Annotations and Followups can be made to the Fields and Document.

After reconciliation, User DR clicks Submit. The Review Panel shows that the value was reconciled by DR.

Note that Document Status is now "Pending Approval".

User1 repeats steps 2 and 3 from DDE Example 1 (logs on and opens the eForm Manager), but then he creates a new Document using DDE Form 2.

User2 repeats steps 3 through 5 from DDE Example 1 (enters conflicting data), but using DDE Form 2.

A message is displayed to User2 indicating that it could not be Submitted because there are reconciliation errors. User2 is now getting feedback. This is in contrast to Example 1, where he was given no indication of reconciliation errors. User2 clicks OK.

The Review Panel shows that discrepancies exist... but does not reveal User1's data.

User2 cannot Submit data if discrepancies exist. He can "Acknowledge" (accept) existence of the discrepancies by clicking the green checkmark on the Review Panel tab. He is asked if he wants to override the discrepancies.

User2 clicks Yes, and the Review Panel records the Acknowledgement.

As in step 6 of DDE Example1, User2 clicks Submit, answers "No" to creating a New Document, and the Document transitions to "Pending Approval".

User1 repeats steps 2 and 3 from DDE Example 1 (logs on and opens the eForm Manager), but then he creates a new Document using DDE Form 3.

User2 repeats steps 3 through 5 from DDE Example 1 (enters conflicting data), but using DDE Form 3.

As in Example 2, a message is displayed to User2 indicating that it could not be Submitted because there are reconciliation errors. User2 clicks OK.

The difference is that User2 is not only notified of discrepancies, he can also see User1's entered data in the Review Panel... as well as Reconcile the discrepancies.

Here, User2 can choose either value, or choose "Override both entries" and enter a different value. Then, clicks the green arrow to Reconcile.

Regardless of the choice, User2 is returned to the eForm Manager in Search mode with a status of Pending Approval (as in step 6 of Double Double Data Entry Example 1).