The StepWorkflow package now also includes a sanity process to check whether all configurations are fine. The sanity workflow contains the following sections:
URN check. Verifies that urn values required for StepWorkflow exist. It does this based on the values in the config file with the "urn" tag. It verifies they each exist, and the test is considered SUCCESS if and FAILED if it doesn't.
Workflow map files. Goes through the StepWorkflow.map file and verifies that it can access each workflow file in the map file. It also verifies that the workflow identifier in the map file matches the one in the workflow file.
Access to Product 360. The config file has to get field and update field descriptor values to verify the connection to Product 360. First, it does a GET and verifies the response. Then it uses the same value to do a POST. Using the same value makes sure nothing is changed for the sanity test but also verifies the connection.
The sanity test also allows for a task to be created and/or an email sent out. For the task and email, the sanity test is labeled a SUCCESS if no tests fail. Otherwise, it is considered FAILED and the following error is displayed: