We are developing a BarTender document that is operated through Print Portal using BarTender Designer 12.0.1 Enterprise (build 12.0/253640).

The workflow consists of a sequence of Data Entry Forms. On each form, the operator enters/scans one pallet ID and six item IDs. Syntax validation of each individual field is handled successfully using the data source transformation settings.

In addition, we need to validate the values entered on one form against values entered on previous forms. For example:

• The pallet ID must not have been used on a previous pallet.
• An item ID must not appear more than once on the same pallet.
• An item ID must not already have been entered on a previous pallet.

We have successfully implemented the actual validation using SQL, a database table and VBScript. Duplicate conditions are detected correctly and the corresponding validation result can be stored in the database.

The difficulty is the user interaction in Print Portal after a validation error is detected.

Ideally, when the operator completes a Data Entry Form and a duplicate is detected, we need one of the following behaviours:

1. Prevent navigation to the next Data Entry Form and allow the operator to correct the values on the current form, or
2. Allow navigation to the next form, display a clear validation error there, and let the operator use Back to return to the previous form and correct the data.

We have not found a reliable way in Print Portal to either block the transition after the validation is performed, or to display the newly generated validation result on the following form. The validation result itself in the database is correct.

Could you please advise what the recommended/supported BarTender architecture is for cross-form validation in Print Portal?

In particular:

• Is there a supported event/action that can validate entered values and prevent moving to the next Data Entry Form?
• If validation must occur after the current form is closed, what is the recommended way to display that result on the following form?
• Is there a supported way to force a data source/control on the following form to refresh/re-evaluate when that form is shown again after using Back?

Our main requirement is that the operator must be able to correct the most recently entered pallet data without restarting the entire Print Portal print job.