Invalid Digital Processes

See how to fix an invalid digital process.

If you created a new digital process but the validation shows that the process is invalid, check the following possible reasons:

• Proper configuration and reference to Make scenarios

• JSON document syntax errors

Errors in referencing to Make scenario

It's possible that you have a wrong reference to a Make scenario that was either deleted or modified.

Reference to a deleted Make scenario

Check if your digital process does not reference a scenario that had been deleted. If it does, you should see a red error with a Scenario deleted notification message at the location (digital process step) where the scenario was used.

To resolve this error, remove the reference to the deleted scenario from your digital process step.

Reference to a modified Make scenario

If a Make scenario was modified, it may no longer meet the requirements of its intended context. In such a situation, the OE UI doesn't show it in the list scenarios available for your digital process. You're not able to use the scenario in your process' steps.

This occurs when:

• The scenario no longer sends output event information through the Start New Orchestration module

• The scenario no longer sends output event information through the Completion Event module

• The scenario no longer receives incoming calls through the Trigger Event Make module

To resolve the errors, make sure the modified Make scenario meets the requirements of the intented context and check if all the input and output modules are configured properly, with correct events setup.

To learn more about the modules, see OE Make Modules documentation.

JSON syntax

As the digital processes are designed using OE UI, it doesn't usally happen that any syntactic errors occur. However, if it turns out that your digital process doesn't work, and you checked all the OE and Make settings but the errors still occur, you may need to review the JSON document to ensure it adheres to proper structure and formatting.