...
...
...
...
...
...
Screen Location: Space Tools → > Document Management → > Document Management tab → > Workflow Action Menu (Ellipsis) → > Initialize States
| Table of Contents | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
This option, chosen from the ellipsis actions menu on a workflow in the document management dashboard, allows you to transition all content for the associated workflow in to into a specific state within that workflow.
...
Select the desired state from the drop-down list and choose the Initialize states button. All content that the workflow is applied to will be transitioned to the selected state.
The workflow must be enabled for the Initialize states button to be visible.
When would I want to do this?
The most common use is after applying a workflow which that uses same-space publishing to a large amount of already-published content in order to force it directly in to into the Published (final=true) workflow state to ensure view-only users can access it.
...
When a workflow is first applied to a page in Space Modespace mode, only the link to the workflow is created (and any page restrictions, if using Samesame-space publishing, are applied).
The page (or blog post) itself won't actually transition in to into the initial workflow state, despite it appearing that way when you look at the Workflow Status Bar. workflow status bar.
| Info |
|---|
If you look at the Activity Report - Content (Document Activity Report in data center app from 7.0+) for such pages, |
...
there are no workflow-specific entries listed. These pages are referred to as "unprocessed". |
Unprocessed pages may cause some unexpected behavior. For example
...
As soon as any workflow-related action occurs, such as changing states or working on tasks, new entries will be added to the Activity Report (Document Activity Report in data center app from v7.0+) and the page will be considered "processed" by the workflow.
...
If you tick the "Override current state" checkbox, the transition will also be applied to content that is considered "processed".
The global advanced configuration setting Workflow action impersonation user group can be used when initialising states with override fails because the creator and last modifier of a page is a deleted user. A global administrator can use this setting when there is no other way to impersonate the user.
See also:
...
If the current workflow state of a document is the same as the selected state to Initialize States, workflow trigger actions related to a state change will not be implemented as these require a transition into the state.