Validating Transformed Form Data

If a form upload staging record is unsuccessful in adding a form, a rollback is performed, the state is changed back to Ready to Load and an error is written to the batch run tree. The lifecycle does not support navigating to Suspended at this point. It is not common for there to be a problem in adding the form because tax forms and registration forms perform minimal validations when creating. It is possible that one of the few required fields is missing (such as Received Date). However, this is more likely pointing out a technical problem with the integration and not something that would occur in production.

In order to try to catch possible form errors earlier in the process where a user can review and update the form or where an implementer can identify an issue in the implementation, the base product Map to Form algorithm (C1-FUS-MPFRM) includes logic to optionally perform a step to validate the form. It uses the business service F1-BOValidate, which receives the target form's business object name and the transformed form data. The service executes schema validation as well as executing the BO validation algorithms. If any validation errors are detected, an issue is logged and the form upload staging record transitions to Suspended. At this point the user is able to fix the form before attempting to validate it again.

Note: Implementations may want to only run this validation during testing or with low volumes as the additional validation per form may have an impact on performance. A Feature Configuration Option is used to indicate if the form validation should be performed or not. Refer to Configuring Transformed Form Validation for more information.