Editing the 0. Entered Step

For example, as a user creates a change request, the only values that can be selected for the workflow control property are those specified for the “O. Entered” step on its “Next Steps” tab.

“0. Entered” is never used as a “Next Step” for any workflow step. That means that users cannot select “0. Entered” as the value for the workflow control property. “0. Entered” can have no links directed to it—only from it. Because no item ever displays this status, there is no reason to set notifications, participants, dynamic defaults, or a duration for this step. They will never be enforced.

While “0. Entered” is never the selected value for the workflow control property in the APE, there always is a selected value. This can cause some initial design confusion. As you create the settings for steps that correspond to values of the workflow control property, be aware that, when a user creates an item, settings assigned to both “0. Entered” and the step that corresponds to the currently selected value of the workflow control property affect the workflow.

For example, suppose that the only “Next Step” for “0. Entered” is “1. New”. As the user creates a new change request, the default value (in fact the only possible value) for the workflow control property is “1. New”. However, the form field settings assigned to both the “0. Entered” and the “1. New” steps affect the APE. If “0. Entered” requires the Type field and the “1. New” step requires the Platform field, both Type and Platform will be required. Notifications, participants, dynamic defaults, and duration come only from the “1. New” step.