The Out-Of-the-Box Workflow settings

At installation, Content Manager comes with a pre-defined list of user roles, status list, initial statuses, status transitions and inboxes. Those can support a basic use that can help you get familiar with the Workflow.

A given user role can create objects that receive an initial status, change some statuses into others and be notified whenever objects acquire specific statuses. This table shows the list of settings you will find out-of-the-box, it excludes however some specific system or legacy settings.

Table 1. OOB Workflow settings
User roleInitial status: Object typeInitial status: Object statusTransition(s)Inbox(es)
AdministratorAll typesDraftReleased to ExpiredNONE
AuthorAll typesDraftDraft to To be reviewedAuthor receiving each map/topic/image/library with Draft, In translation or Released status.
ReviewerAll typesNONETo be reviewed to [Draft; Released]

Translation approved to [To be translated; Released]

Translation in review to [Translation approved; Translation rejected]

Reviewer receiving each map/topic/image/library with To be reviewed status.

Translated receiving each object with Translation approved status.

TranslatorAll typesNONEIn translation to [Translation approved; To be translated]

To be translated to In translation

Translation approved to To be translated

In Translation receiving each object with In translation status.

Translator receiving each map/topic/image/libraries with To be translated status.

TRANSLATORSERVICEAll typesTo be translatedIn translation to [To be translated; Translation approved; Translation in review]

To be translated to In translation

Translation in review to [To be translated; Translation approved; Translation rejected]

Translation rejected to [To be translated; In translation]

NONE

For the translation part of the flow, we recommend you do not change the out-of-the-box settings: statuses, transitions and all the attributions of the TRANSLATORSERVICE user role. This flow provides optimal compatibility with WorldServer and TMS translation systems.

Transcription of these settings into content-centered business processes
For the authoring part:
  • Objects of any type (map, topic, image, library) can be created by administrators and authors. They are created with the Draft status.
  • If an administrator creates objects, the author is advised in the inbox.
  • After the author drafted the content, he or she pushes the status to To be reviewed.
  • The reviewer is advised of incoming To be reviewed content in the inbox, reviews it and pushes this version to either Draft or Released depending on the outcome of the review.
For the translation part:
  • When a group of released objects are ready for translation, they are sent to the translation service in Content Manager that automatically produces the new language objects (one for each language the object needs to be translated into) and assigns a To be translated status to them.
  • The service or the translator then sets to In translation all objects that are currently being translated. When it is done by the service, the translator is advised in the inbox.
  • When the translator is done with an object, the service pushes it to Translation in review. This can also be carried out through our TMS/World Server solutions.
  • The reviewer is notified in the inbox that objects have been translated, and reviews them. He or she then sets the status of the objects to either Translation approved or Translation rejected.
  • At the appropriate moment, the translation service sets all Translation rejected objects to In translation, which notifies the translator again.

You can start applying this flow prior to any specific customization.