Validation of Data Related to the Notification Upload Staging Records

As mentioned above, the sole purpose of the Initiate Workflow Process (WFPRINIT) is to successfully create a workflow process. Once a workflow process is created, the NUS status is set to Complete.

At this point, neither the extension record, the context collection nor the characteristics collection have been processed. It is the responsibility of the first event in the workflow process to validate the fields in the extension record, the context collection and/or the characteristics collection. This algorithm will decide what to do when a problem is detected with the data. Some possible options are

• Set the algorithm status to Fail. Use this option when a critical error is detected, which probably cannot be fixed by a user. This will cause the remaining events to be canceled.
• Set the algorithm status to Error. Use this option when an error is detected, which can be corrected by a user. This will cause an exception record to be created. The user should be able to correct the source data in the extension record, the context collection or the characteristics collection, change the status back to Pending and rerun the Workflow Event Activation process. Note that if the validation algorithm uses this option, the ability to rerun this event should be handled by the coding of this algorithm. It should prevent duplicate logic from being performed.
• Send a To Do list entry and continue the workflow process by setting the algorithm status to Complete. Use this option when someone should be alerted of an unusual condition, but the process should not be halted. For this option, the To Do Type and User to use for posting the To Do entry should be parameters to the algorithm.