Page Comparison

Anchor
top top

A workflow determines the state(s) that a content item can have. The state of a content item determines whether it is visible on the frontend front-end of your website, whether it can be edited and by whom, and so forth. A workflow also determines the order that states can be moved through. For example, consider the simple workflow "Planned - Published". When a content item is first created, it is in the "Planned" state. Content items in the "Planned" state are not visible on the website frontendfront-end. When the workflow state of a content item is changed from "Planned" to "Published", it becomes visible on the website frontendfront-end. Depending on your organization, you might want to create more complicated workflows that add intermediate steps such as "Ready for Review", "Review in Progress", "Review Completed" and so forth. As content items pass through different workflow states, specific roles have specific rights to modify a content item's settings and/or content. A workflow model also defines the order that the states must be transitioned through. For example, it can enforce the condition that a content item can only move from the "Planned" state to the "Ready for review" and not directly from "Planned" to "Published".

...

The workflow model is assigned at the level of the content item. At this level, it also determines which roles are allowed to perform specific activities. Because items in the Content Repository are unstructured, individual Content Repository items of the same type, such as an article, each use a different workflow model. The workflow model "Planned - Published" comes standard with XperienCentral. It is possible to change this workflow model or to add new workflow models.

...

A state is the position the content item is currently in. In XperienCentral the state of an object is either "Public" or "Not public". The list of current states appears in the "States" section:



When an object is in a "Public" state, it can be visible on the frontend front-end of the website. When it is in a "Not public" state, it cannot be visible on the frontend front-end of the website.

Adding States

...

1. Click [Add New Activity]. The new activity will appear at the bottom of the list of the workflow model.
2. Enter a meaningful name for the activity in the "Activity Name" field.
3. In the "Permissions" section, select a permission from the drop-down list. These are the permissions that this activity is allowed to perform.
4. Click [Apply].
5. Repeat the steps above for each permission that you want to grant the activity. The permissions are added to the list. For example:
   
   
   
   

Deleting Activities

To delete an activity, click [Delete] to the right of the activity namefollow these steps:

1. Select the "Delete" checkbox next to the activity you want to delete. For example:
   
   
   Image Added
   
   
   
2. Click [Delete]:
   
   
   Image Modified
   
   
   The activity is deleted.

Back to top

 

...

Actions

Actions determine the flow between statuses. When the status of a content item is changed from one to another, an action determines which activity becomes the new active activity. When the new activity becomes active, its set of permissions determines what tasks can be performed on content items. With every state change, a content item becomes subject to a new activity. An activity may have multiple subsequent activities, but only one activity can be chosen as the next step in the workflow. A workflow action defines a source activity, a destination activity and the condition of the transition. Workflow actions are defined in the "Actions" section of an activity, where the source activity is the current activity, the destination activity is the "Go to activity" and the condition is the "When changed to the status" field.

...