When to create a new workflow version

Guidewire recommends, as a general rule, that you create a new workflow version under most circumstances if you modify a workflow. For example:

• If you add a new step to the workflow, then create a new workflow version.
• If you remove an existing step from the workflow, then create a new workflow version.
• If you change the step type, for example, from Manual to an automatic step type, then create a new workflow version.

More specifically, for each workflow, PolicyCenter does the following:

• Records the current step of an active workflow in the database. Each change to the basic structure of a workflow requires a new version.
• Records the branch that an active workflow selects in the database. A change to the Branch ID requires a new version.
• Records the activity associated with an Activity step in the database. A change to an Activity definition requires a new version.
• Records the trigger activity that occurs in an active workflow in the database. A removal of a trigger requires a new workflow version.
• Records the messageID of each workflow message in the database. A modification to a MessageStep requires a new workflow version.

If you do modify a workflow, be aware that:

• If you convert a manual step to an automatic step, it can cause issues for an active workflow.
• If you reduce a timeout value, any active workflows that have already hit that step will only wait the previously calculated time.