...
Tip |
---|
To understand how to manage authorization please consult the dedicated page: Authorization. |
Channel and Issue
Create a new Publication Channel from the Brand page in Enterprise.
The exact name of the publication channel used in SCE must be written in the TIMONE System configuration SCE_pub_channel in System > Configurations (Config. Publication) > SCE.
Now, you can create and manage the issues under the channel page.
If you want to synchronize an issue in TIMONE System, you must create a new issue in SCE (same publication and channel) called as the "Prod Code" of the already existent one.
Instead, if you are opening a new issue, you can use TIMONE System to create the issue from the Plan Issue Management Screen, ensuring to check the "Create issue in the prod system" box; this option enables the automatic issue creation in SCE.
Workflow

Editorial Status
SCE layout workflow statuses have to be synchronized through the TIMONE Administration page Production > Mapping of the Workflow Statuses with the TIMONE System Editorial Statuses. This page allows you to match the statuses between the two systems, without making any change to the original configuration.
Sections
Section names in TIMONE System must correspond exactly to the categories of Enterprise.
One of the defined section will be dedicated to ads, this section name need to be written in the SCE_AdvSection configuration.
Templates
All the layout templates created in InDesign have to be assigned to the right publication, issue and section and they must have the same name set in the TIMONE System Administration page Production > Layout Templates.
The advertising templates are simple empty pages, but they have to be called in this specific way: "ADV_<materialformat>" where material format is the exact name of the material format used for the ad.
You need to set the configuration SCE_Advert_name that defines the rule used to build the name of the adv layouts in the production system.
You can build the name using the following patterns:
#publication# - name of the publication;
#issue# - name of the issue;
#edition# - name of the edition (if enabled and the name is different than “*”);
#page# - number of the page where the ad placeholder is allocated (1 digit);
#page??# - number of the page where the ad placeholder is allocatedv (2 digit);
#page???# - number of the page where the ad placeholder is allocated (3 digit);
#jobticket# - job ticket number (just if the booking is placed on the adv format);
#pubCod# - publication ERP code;
#folio# - folio number of the page where the ad placeholder ad is allocated;
#idLayProd# - production ID layout (if present);
#customer# - booking customer name (just if the booking is placed on the adv format);
#product# - booking product name (just if the booking is placed on the adv format);
#format# - adv format code;
#formattext# - adv format notes (if present);
#uid# - univocal ID (suggested to avoid the creation of already existent names).
...