Planning workstates

Build 1501 on 14/Nov/2017  This topic last edited on: 1/Sep/2014, at 12:01

A GN4 Systems Administrator freely plan and define the purpose, the usage and the list of workstates in an early phase of the installation of GN4, according to the needs of the publisher.

_caution Since workstates are server wide, therefore, equal for all the titles on the same editorial server, in a multi-title configurations, agree the workstates structure with all publications.

_important Take into account that, while unlimited colors are available for workstates, to be able to easily distinguish workstates, the number of colors is much less.

The plan should contain:

the number and names of workstates required for folder objects, such as articles, images and multimedia

the number and names of workstates required for pages

the number and names of workstates required for editions

the number and names of workstates required for calendar objects, such as events and tasks.

the colors of workstates for each category

_noteNotes

It is not possible to change the ID of the workstate, except by direct editing of the SQL database, however, it is recommended not to do it, because it can cause serious malfunctioning of the editorial procedures.

The number of workstates for folder objects, such as articles, images and multimedia should not be greater than the number of different folder types, e.g.; text editing, subbing, pagination, ready, because you can assign workstates for folder objects only to folders.

The number of workstates for calendar objects should not be greater than the number of different calendar types, e.g.; text editing, subbing, pagination, ready, because you can assign workstates for calendar objects only to calendars.

The number of workstates for pages and editions may be any, because they are assigned manually.