Workflow Handling on Bundle Update
SuiteBundler updates bundled workflows in a target account using the following rules:
-
If states or transitions are modified in an unlocked workflow in the source account, NetSuite updates states and transitions previously installed in the target account with the states and transitions from the source account. NetSuite also adds any new states or transitions in the source account to the target account. If a state or transition with the same name exists in the source and target accounts, NetSuite duplicates the state or transition in the target account.
For example, after you install a bundle, you create a new state “state10” in both source and target account and then update the bundle. In the target account workflow, two states named “state10” will appear, one created directly in the target account and the other installed by the bundle update.
-
If states or transitions, or any aspect of the workflow objects, are modified in the target account, updating the bundle will revert the changes back to what the source dictates.
-
If states or transitions are deleted in a target account, they will be replaced during a bundle update.
-
If you delete any state or transition in the source, but use them in the target, you will be unable to remove these states or transitions in the target account if the workflow is running in the target account and is currently referencing that state. Bundle authors should advise their customers to make these states or transitions inactive if they are not meant to be used any longer.
Workflow instances and history logs are not copied to target accounts when a bundle is updated.
Workflow release status is not updated in the target account when a bundle is updated or copied. You can set your preferred workflow release status in the target account manually.
For more information, see Bundling a Workflow.
Merge Handling for Reinstallation of Bundled Workflow in Target Production Account from Sandbox
The following handling prevents duplication of workflow states in cases where a bundled workflow is installed in a target account, and the same workflow is later installed again in that same account. For example, this case would apply to installation of a bundled workflow from Sandbox to Production where the sandbox account is a direct clone of the target production account.
When the same workflow is reinstalled in the target account and Merge Data is selected during installation:
-
Workflow states are merged based on matching script IDs.
-
Actions are merged based on matching script IDs and workflow state IDs.
-
Transitions are merged based on matching script ID of source and target state and database ID, meaning merge occurs only if the transition was originally created in sandbox as result of a Production refresh. If a transition was manually created in both Sandbox and Production, it is not merged.
In all other cases, such as when a bundle is installed from a production account into another production account, or from a sandbox account to a non-owning production account, states, actions, and transitions are duplicated without regard to script IDs.