Table of Contents

Draft mode of case processes


Only available versions of this content are shown in the dropdown

When you add a process to your case life cycle, by default the process is in draft mode. Draft mode provides an option to test the case type before you advance with your application development, even if processes in your case life cycle contain configuration issues.

For example, you can test how a Loan request case type behaves at run time even before you configure the views with fields that users use to provide information.

Every process that you add to your case life cycle is automatically put into draft mode. As a result, you can preview and run a case to check the run-time behavior, even if some of the processes contain errors. When you want to deploy your application in a production environment, to correctly migrate processes you need to turn draft mode off. Because you can add multiple processes to every case type in your application, App Studio and Dev Studio automatically turn draft mode off for every process that has no errors. Consequently, you save time as you avoid having to manually turn off draft mode in Dev Studio for every single process.

To ensure that the status of draft mode changes when you save your case type, if any of your processes contain errors, Case Designer displays a list of issues that you need to fix before deployment. The list navigates you to the relevant processes and provides a short description of each issue, as in the following examples:

Warning about errors in processes
The edit case types screen showing a warning about errors in
Window with a list of errors
A window showing a list of errors that need to be addressed.

Did you find this content helpful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.