Content Publication

The majority of content publication services have interfaces that allow for differentiated publication of each registered content. Various parameters can be specified:

Publication Period: This field defines the date and time when the content will be published on the portal and removed from it, changing its status to archived;
Highlight: When determining the importance of a content, the editor must clarify whether it is a highlight or not, allowing the system to direct it to an appropriate interface, such as, for example, a main news highlight, where only the most recent highlighted content is displayed, with maximum priority;
Highlight Expiration Date: Defines the date and time when the content will cease to be a highlight. From the date specified here, the Highlight field will automatically change its value (the highlight field will be unchecked);
Publication to instances: On certain occasions, it is interesting to be able to publish the same content across multiple channels that contain the same instance of the primary service. For this, the “Instances” field is provided, which allows the content editor to define other instances of the solution where they wish for a specific content to also be published. Thus, the same content becomes shared among the instances, although its maintenance is only possible through the primary instance. The number in “parentheses” indicates how many instances the same content has been published. By default, the value is equal to “1” corresponding to the publication for the own instance.
For example: A news published in a company's news section can also be presented in the Alerts channel, requiring only that the user clicks on the Instances button and chooses the relevant channel for Alerts that contains the service instance of News.

The figure below shows that the channel containing the primary instance is selected by default, as it is not possible to publish to the own instance. Following the previous example, the editor must select the section Portal/Documentation/Alerts/News, since Portal/Documentation/Alerts corresponds to the channel where the service instance is; and News corresponds to the name of the service instance.
Notes
1. For an editor to publish content to two instances of the same service, it is necessary to have the same access permissions in both instances of the service;
2. The content will be published normally on the pages of the channel whose instances received the publication, unless accessing the pages of the channel that contains the primary instance.
  This behavior is related to search. When searching for content published in multiple instances, as many contents as there are instances will be returned, and when accessing them, the details page of the channel containing the primary instance will not be displayed, but rather the instance that received the publication.
3. The list of available instances is displayed according to the Area Tags defined/inherited by the service instance. That is, only instances that have common Area Tags will be available in the listing. If the instance does not inherit any Area Tag and does not have any Area Tag defined in its own instance, it will not be visible to any other instance.
Publication for users, groups or segmentations: This functionality allows the editor to publish each of the registered contents for different users, groups, or segmentations. Nevertheless, users referenced directly or indirectly (through groups and/or segmentations) will only see such contents if they have permission to access the service instance of such content. However, if the user is in the access control of the service instance either directly or indirectly but is not on the content's publication list, directly or indirectly, they will not be able to view it. By default, the group "All registered users" will receive the publication of the contents (except for those users who are also in this group having permission in the access control).
Notes
1. The selected groups and/or users must have viewing permissions for the service instance in its access control.
2. The content of the list of groups and users is displayed according to:
  - Global groups and users;
  - Local groups and users of channels that have common Area Tags with the current instance.
  - Segmentations registered in instances of the Customer Experience service that have common Area Tags with the current instance.
    
    Attention!
    Segmentations should not be used for security purposes, such as limiting access to sensitive content, as they also apply to unauthenticated users. They should only be used for purposes of improving experience, such as directing non-sensitive content in a personalized manner.
Comments:Allows all those responsible for the content to exchange information about its changes. The number in parentheses indicates the number of comments for that content.