Step 2: Creating a Publication Channel

Note: Per Brand, only one Publication Channel of type Print can be set up.

Step . In the Name field, enter a name.

Step 4. In the Description field, enter a description.

Step 5. From the Publication Channel Type list, choose Print.

Step 6. From the Publish System list, choose Enterprise (this is the default setting which does not use a publishing system).

Step 7. Leave the Suggestion Provider option set to None.

Step 8. Click Create.

New items appear on the page:

• An additional property named 'Current Issue' appears below the Publication Channel Type property. Since Issues still need to be set up, we will come back to setting this option later in the process.
• Below the Publication Channel properties area, sections for adding Editions and Issues appear. We will add these now.

Figure: After clicking Create, additional options appear.

Creating Editions

Step 9. Click Add Edition.

The Edition Maintenance page appears.

Step 10. Enter a name in the Name box.

Step 11. (Optional) Enter a description in the Description box.

Step 12. Click Update.

The Publication Channel Maintenance page appears with the newly created Edition added to the Editions menu.

Step 13. (Optional) Add additional Editions as required.

Step 14. (Optional) In the Order box on the Publication Channel Maintenance page, enter an order number for each Edition and click Reorder. This will determine in which order the Editions are displayed in the client application interfaces.

Note: We recommend using a unique order number in order to prevent technical issues when a search is performed.

Creating Issues

Step 15. On the Publication Channel Maintenance page, click Add Issue.

The Issue Maintenance page appears.

Step 16. Fill out the details.

Note: At the most basic level, only a name needs to be entered; all other options can also be set at a later stage by modifying the created Issue.

• Name. Name of the Issue.
• Publication Date. Date (and time, if required) when the Issue needs to be published by.
• Deadline. Date (and time, if required) when the Issue needs to be finished by.

Tip: Instead of entering a date, enter the number of days, hours, and/or minutes before the publication date should be reached and click the Recalculate icon. This will automatically calculate the Deadline based on the entered Publication Date.

• Expected Pages. Number of expected pages.
• Subject. This feature is currently not functional.
• Description. Description of the Issue.
• Active. Use to deactivate the Issue. This will hide the Issue and all objects assigned to the Issue from the users without actually removing the Issue from the system.
• Overrule Brand. Use to determine if the new Issue should have its own Categories, Workflow, and User Authorization definitions. After selecting this option, click the Update button to display the options for setting the Categories, Workflow, and Authorizations for this Issue.
• Reading Direction. Only available when Overrule Brand is active (and after clicking Update). Determines whether the pages in the Issue are displayed left to right or right to left (reversed) when viewed in the Publication Overview of Content Station.
• Activate Relative Deadlines. (Since Enterprise 9.2) Only available when Overrule Brand is active (and after clicking Update). Activates the functionality for assigning deadlines to Categories and Workflow Statuses. When selected, the 'Time Settings' icon appears.
• Time Settings. Only available when Overrule Brand is active (and after clicking Update), and (since Enterprise 9.2) after clicking 'Activate Relative Deadlines'. Displays the Relative Deadline page. Leave this setting for now, it is covered in a later step.
• Deadlines. (Since Enterprise 9.2 only available when the option 'Activate Relative Deadlines' is selected on the Brand Maintenance page.) Displays the Issue Deadlines page. Leave this setting for now, it is covered in a later step.

Step 17. Click Update.

Finishing the setup

Step 18. Click the arrow at the bottom of the page to return to the Publication Channel Maintenance page.

Step 19. (Optional) Add additional Issues as needed.

Step 20. Click the arrow at the bottom of the page to return to the Brand Maintenance page.

Step 21. (Optional) Add additional Publication Channels as needed.

Step 22. (Optional, only if multiple Publication Channels have been created) From the Default Publication Channel list at the top of the Brand Maintenance page, choose the default Publication Channel that should act as the default print channel used by InDesign/InCopy.

Note: In order for this feature to work properly, it is imperative that an order sequence for the created Issues is correctly specified on the Publication Channel Maintenance page. If this is not done (or not done correctly), Enterprise may not be able to properly determine the Previous and Next issues.

Figure: The Default Publication Channel list.

Step 23. Click Update.

Step 24. (Optional, only if the Overruled Brand option has been selected) In order for the Overruled Issue to be visible in Content Station, enable the Enterprise Server plug-in named Content Station Overrule Compatibility.

Info: Adobe AEM was formerly known as Adobe DPS (2015).

Step 3. In the Name field, enter a name that is unique within that Brand.

Step 4. In the Description field, enter a description.

Step 5. From the Publication Channel Type list, choose dps2.

Step 6. From the Publish System list, choose Adobe AEM.

Step 7. Leave the Suggestion Provider option set to None, it is not used for Adobe AEM.

Step 8. Click Create.

An additional section named Adobe AEM appears as well as sections for creating Editions and Issues.

Filling out the Adobe AEM section

Note: The Project field is a read-only field and is automatically filled by Enterprise (this occurs at a later stage during the integration process).

Step 9. From the Default Article Access list, choose from the following options:

• Metered. Enables a user to preview an article for free, but only as long as the total number of free articles that can be viewed for that publication has not yet been reached. Once that total is reached, the user is prompted to purchase the publication or a subscription.

Note: Setting the total number of free articles is done in the account administration panel of Adobe AEM.

• Protected. Protects the story from sharing it through social media in the following ways:

• Viewing a representation of the story in a desktop browser.
• Sharing the story through Facebook, Adobe AEM, e-mail and by Copy Link.

Sharing is done by making a URL available:

• For unprotected stories, this URL links to a representation of the story which can be viewed in a supported desktop browser or on a smartphone or tablet.
• For protected stories, this URL links to the publication URL (a URL that contains information about the publication).

• Free. Makes the story available to all users for free.

Step 10. Select the check box Create Collections. This makes sure that when a layout is checked in, a Collection is automatically created when that Collection does not yet exist.

Creating Editions

Editions represent the output device that is published to. In Adobe AEM, output devices are of a generic type such as a smartphone or a tablet, and not for a specific device such as an iPhone 6 or Samsung Galaxy S4.

An Edition should therefore be created for each of these output device types.

Step 11. Click Add Edition.

The Edition Maintenance page appears.

Step 12. Enter the name "phones" in the Name box.

Step 13. (Optional) Enter a description in the Description box.

Step 14. Click Update.

The Publication Channel Maintenance page appears with the newly created Edition added to the Editions menu.

Step 15. Add another Edition named tablets.

Step 16. (Optional) In the Order box on the Publication Channel Maintenance page, enter an order number for each Edition and click Reorder. This will determine in which order the Editions are displayed in the client application interfaces.

Creating Issues

Step 17. On the Publication Channel Maintenance page, click Add Issue.

The Issue Maintenance page appears.

Step 18. Fill out the details.

Note: At the most basic level, only a name needs to be entered; all other options can also be set at a later stage by modifying the created Issue.

• Name. Name of the Issue.
• Publication Date. Date (and time, if required) when the Issue needs to be published by.
• Deadline. Date (and time, if required) when the Issue needs to be finished by.

Tip: Instead of entering a date, enter the number of days, hours, and/or minutes before the publication date should be reached and click the Recalculate icon. This will automatically calculate the Deadline based on the entered Publication Date.

• Expected Pages. Number of expected pages.
• Subject. This feature is currently not functional.
• Description. The description of the issue; appears in the Library of the Content Viewer.

• Active. Use to deactivate the Issue. This will hide the Issue and all objects assigned to the Issue from the users without actually removing the Issue from the system.

• Overrule Brand. Use to determine if the new Issue should have its own deadline, Category, Workflow, and User Authorization definitions. After selecting this option, click the Update button to display the options for setting the Categories, Workflow, and Authorizations for this Issue.

Step 19. Click Update.

Finishing the setup

Step 20. Click the arrow at the bottom of the page to return to the Publication Channel Maintenance page.

Step 21. (Optional) Add additional Issues as needed.

Step 22. Click the arrow at the bottom of the page to return to the Brand Maintenance page.

Step 23. (Optional) Add additional Publication Channels as needed.

Step 24. (Optional, only if multiple Publication Channels have been created) From the Default Publication Channel list at the top of the Brand Maintenance page, choose the default Publication Channel that should act as the default AEM channel.

Note: In order for this feature to work properly, it is imperative that an order sequence for the created Issues is correctly specified on the Publication Channel Maintenance page. If this is not done (or not done correctly), Enterprise may not be able to properly determine the Previous and Next issues.

Figure: The Default Publication Channel list.

Step 25. Click Update.

Step 26. (Optional, only if the Overruled Brand option has been selected) In order for the Overruled Issue to be visible in Content Station, enable the Enterprise Server plug-in named Content Station Overrule Compatibility.

Step 3. In the Name field, enter a name.

Step 4. In the Description field, enter a description.

Step 5. From the Publication Channel Type list, choose DPS.

Step 6. From the Publish System list, choose Adobe DPS.

Step 7. Leave the Suggestion Provider option set to None.

Step 8. Click Create.

New items appear on the page:

• An additional property named 'Current Issue' appears below the Publication Channel Type property. Since Issues still need to be set up, we will come back to setting this option later in the process.
• Below the Publication Channel properties area, sections for adding Editions and Issues appear. We will add these now.

Figure: After clicking Create, additional options appear.

Creating Editions

In Enterprise, Editions represent the device that is published to, such as an iPad, a Galaxy, a Playbook, and so on. An Edition should therefore be created for each output device.

Step 9. Click Add Edition.

The Edition Maintenance page appears.

Step 10. Enter a name in the Name box.

Notes: The name must match the corresponding Device name, as defined on the Output Device Maintenance page. The name should be descriptive, such as “Apple iPad”, “Samsung Galaxy”, and so on, especially because the name also appears in the Editions panel in InDesign and the Digital Publishing application in Content Station.

Step 11. (Optional) Enter a description in the Description box.

Step 12. Click Update.

The Publication Channel Maintenance page appears with the newly created Edition added to the Editions menu.

Step 13. (Optional) Add additional Editions as required.

Step 14. In the Order box on the Publication Channel Maintenance page, enter an order number for each Edition and click Reorder. This will determine in which order the Editions are displayed in the client application interfaces.

Notes: When a layout has multiple devices assigned (in the form of Editions), the first Edition that is assigned to the layout is used as the primary device. The Landscape Layout Width setting of this primary device (as set on the Output Device Maintenance page) is used for determining whether the layout should be treated as a layout in landscape orientation or portrait orientation. The number of Editions assigned to the layout could of course be different from the total number of devices configured. For example, assume that the following devices have been configured with the following order numbers: 10 iPad 20 Galaxy 30 Playbook If for a layout only the Galaxy and Playbook Editions have been assigned, then the Galaxy is considered as the primary device, even though the iPad Edition precedes it in the configuration.

Creating Issues

Step 15. On the Publication Channel Maintenance page, click Add Issue.

The Issue Maintenance page appears.

Step 16. Fill out the details.

Note: At the most basic level, only a name needs to be entered; all other options can also be set at a later stage by modifying the created Issue.

• Name. Name of the Issue.
• Publication Date. Date (and time, if required) when the Issue needs to be published by.
• Deadline. Date (and time, if required) when the Issue needs to be finished by.

Tip: Instead of entering a date, enter the number of days, hours, and/or minutes before the publication date should be reached and click the Recalculate icon. This will automatically calculate the Deadline based on the entered Publication Date.

• Expected Pages. Number of expected pages.
• Subject. This feature is currently not functional.
• Description. The description of the issue; appears in the Library of the Content Viewer.

• Publication title. The title that will appear at the top of each issue in the Library and in the top Navigation bar of the Content Viewer.

Tip: For best results, use no more than 35 characters.

• DPS Cover Date. The cover date of the publication.

• DPS Product ID. The unique ID of the product.

Notes: It is highly recommended to use a Product ID that is in lower case characters only. Although the use of upper case characters is allowed, certain scenarios are known in which they are the cause of technical issues. If your folio is a retail version, make sure that your Product ID matches the Product ID specified during the In App Purchase process for iPad apps or the In App Billing process for Android apps. If you specify a different Product ID, the folio fails to appear in your custom viewer app

Tip: For best results, use the com.publisher.publication.issue format (such as com.adobepress.dps_tips.july) to specify the Product ID.

• Page orientation. Defines which page orientation is to be used in the Content Viewer:
• Landscape only
• Portrait only
• Landscape and portrait.

Note: The Content Viewer uses this setting to show the issue in the set orientation; this allows having issues with different orientation settings within the same Reader App.

• Page navigation. Defines how the pages are navigated:
• Horizontal: all pages of all stories are placed next to each other.
• Horizontal and vertical: stories are placed next to each other while their pages are placed above each other.

• Reading direction. Specifies if the reading direction should be left-to-right or right-to-left.

• Volume number. The volume number of the publication. Appears in the Navigation top bar of the Adobe Content Viewer.

• DPS Filter. For assigning a filter value to an Issue. This allows users of the Adobe Content Viewer to filter the issues by this value in the Store and Library (such as by language or product.)

• DPS Target Viewer Version. For setting the minimum version of the Content Viewer that the user needs to have installed in order to view the issue. Set to blank if no minimum installed version should be forced.

• Active. Use to deactivate the Issue. This will hide the Issue and all objects assigned to the Issue from the users without actually removing the Issue from the system.

• Overrule Brand. Use to determine if the new Issue should have its own deadline, Category, Workflow, and User Authorization definitions. After selecting this option, click the Update button to display the options for setting the Categories, Workflow, and Authorizations for this Issue.

• Reading Direction. Only available when Overrule Brand is active (and after clicking Update). Determines whether the pages in the Issue are displayed left to right or right to left (reversed) when viewed in the Brand Overview of Content Station.

• Activate Relative Deadlines. (Since Enterprise 9.2) Only available when Overrule Brand is active (and after clicking Update). Activates the functionality for assigning deadlines to Categories and Workflow Statuses. When selected, the 'Time Settings' icon appears.
• Time Settings. Only available when Overrule Brand is active (and after clicking Update), and (since Enterprise 9.2) after clicking 'Activate Relative Deadlines'. Displays the Relative Deadline page. Leave this setting for now, it is covered in a later step.
• Deadlines. (Since Enterprise 9.2 only available when the option 'Activate Relative Deadlines' is selected on the Brand Maintenance page.) Displays the Issue Deadlines page. Leave this setting for now, it is covered in a later step.

Step 17. Click Update.

Finishing the setup

Step 18. Click the arrow at the bottom of the page to return to the Publication Channel Maintenance page.

Step 19. (Optional) Add additional Issues as needed.

Step 20. Click the arrow at the bottom of the page to return to the Brand Maintenance page.

Step 21. (Optional) Add additional Publication Channels as needed.

Step 22. (Optional, only if multiple Publication Channels have been created) From the Default Publication Channel list at the top of the Brand Maintenance page, choose the default Publication Channel that should act as the default DPS channel.

Note: In order for this feature to work properly, it is imperative that an order sequence for the created Issues is correctly specified on the Publication Channel Maintenance page. If this is not done (or not done correctly), Enterprise may not be able to properly determine the Previous and Next issues.

Figure: The Default Publication Channel list.

Step 23. Click Update.

Step 24. (Optional, only if the Overruled Brand option has been selected) In order for the Overruled Issue to be visible in Content Station, enable the Enterprise Server plug-in named Content Station Overrule Compatibility.

Step 3. In the Name field, enter a name.

Step 4. In the Description field, enter a description.

Step 5. From the Publication Channel Type list, choose Web.

Step 6. From the Publish System list, choose Drupal 6.

Step 7. Leave the Suggestion Provider option set to None.

Step 8. Click Create.

New items appear on the page:

• An additional property named 'Current Issue' appears below the Publication Channel Type property. Since Issues still need to be set up, we will come back to setting this option later in the process.
• Below the Publication Channel properties area, a section for adding Issues appears. We will add these now.

Creating Issues

Step 9. Click Add Issue.

The Issue Maintenance page appears.

Step 10. Fill out the details.

Note: At the most basic level, only a name needs to be entered; all other options can also be set at a later stage by modifying the created Issue.

• Name. Name of the Issue.

• Subject. This feature is currently not functional.
• Description. Description of the Issue.
• Active. Use to deactivate the Issue. This will hide the Issue and all objects assigned to the Issue from the users without actually removing the Issue from the system.

Step 11. Click Update.

Finishing the setup

Step 12. Click the arrow at the bottom of the page to return to the Publication Channel Maintenance page.

Step 13. (Optional) Add additional Issues as needed.

Step 14. Click the arrow at the bottom of the page to return to the Brand Maintenance page.

Step 15. (Optional) Add additional Publication Channels as needed.

Step 16. (Optional, only if multiple Publication Channels have been created) From the Default Publication Channel list at the top of the Brand Maintenance page, choose the default Publication Channel that should act as the default print channel used by InDesign/InCopy.

Figure: The Default Publication Channel list.

Step 17. Click Update.

Step 3. In the Name field, enter a name.

Step 4. In the Description field, enter a description.

Step 5. From the Publication Channel Type list, choose Web.

Step 6. From the Publish System list, choose Drupal 7 — Publish Forms.

Step 7. (Optional, only when tags should be automatically suggested. See About adding tags to Web articles). From the Suggestion Provider list, choose the provider for suggesting tags.

Info: This feature requires Enterprise Server version 9.1 or higher.

Note: The default Suggestion Provider in Enterprise is the one from OpenCalais.

Step 8. Click Create.

New items appear on the page:

• An additional property named 'Current Issue' appears below the Publication Channel Type property. Since Issues still need to be set up, we will come back to setting this option later in the process.
• Options for the Drupal account appear. We will set these next.
• Below the Publication Channel properties area, a section for adding Issues appears. We will add these in a moment.

Drupal account settings

Step 9. Set the options for the Drupal account:

• Web Site URL. The URL of your Drupal site.

Note: Make sure that the URL ends with a forward slash "/".

Example: http://127.0.0.1/drupal/

• Consumer Key. The consumer key as set up on Drupal.

• Consumer Secret. The consumer secret as generated on Drupal.

• Certificate. (Optional, required for HTTPS (SSL) connections only.) The full file path of the local CA certificate file (in PEM format). See the SSL SDK for how to generate certificates.

Creating Issues

Step 10. Click Add Issue.

The Issue Maintenance page appears.

Step 11. Fill out the details.

Note: At the most basic level, only a name needs to be entered; all other options can also be set at a later stage by modifying the created Issue.

• Name. Name of the Issue.

• Subject. This feature is currently not functional.
• Description. Description of the Issue.
• Active. Use to deactivate the Issue. This will hide the Issue and all objects assigned to the Issue from the users without actually removing the Issue from the system

Step 12. Click Update.

Finishing the setup

Step 13. Click the arrow at the bottom of the page to return to the Publication Channel Maintenance page.

Step 14. (Optional) Add additional Issues as needed.

Step 15. Click the arrow at the bottom of the page to return to the Brand Maintenance page.

Step 16. (Optional) Add additional Publication Channels as needed.

Step 17. (Optional, only if multiple Publication Channels have been created) From the Default Publication Channel list at the top of the Brand Maintenance page, choose the default Publication Channel that should act as the default Drupal 6 channel.

Note: In order for this feature to work properly, it is imperative that an order sequence for the created Issues is correctly specified on the Publication Channel Maintenance page. If this is not done (or not done correctly), Enterprise may not be able to properly determine the Previous and Next issues.

Figure: The Default Publication Channel list.

Step 18. Click Update.

Info: This feature requires Enterprise Server version 9.1 or higher.

Step 3. In the Name field, enter a name.

Step 4. In the Description field, enter a description.

Step 5. From the Publication Channel Type list, choose Web.

Step 6. From the Publish System list, choose Facebook — Publish Forms.

Step 7. Leave the Suggestion Provider option set to None.

Step 8. Click Create.

New items appear on the page:

• An additional property named 'Current Issue' appears below the Publication Channel Type property. Since Issues still need to be set up, we will come back to setting this option later in the process.
• Options for the Facebook account appear.
• Below the Publication Channel properties area, a section for adding Issues appears. We will add these in a moment.

Facebook account settings

Step 9. Set the options for the Facebook account:

• Application ID: Obtain this from the Basic settings page for your app on https://developers.facebook.com/apps.
• Application Secret: Obtain this from the Basic settings page for your app on https://developers.facebook.com/apps.
• Page ID: Access your Facebook page, click Edit Page > Update Page Info.

Step 10. Click Update.

Creating Issues

Step 11. Click Add Issue.

The Issue Maintenance page appears.

Step 12. Fill out the details.

Note: At the most basic level, only a name needs to be entered; all other options can also be set at a later stage by modifying the created Issue.

• Name. Name of the Issue.

• Subject. This feature is currently not functional.
• Description. Description of the Issue.
• Active. Use to deactivate the Issue. This will hide the Issue and all objects assigned to the Issue from the users without actually removing the Issue from the system.

Step 13. Click Update.

Finishing the setup

Step 14. Click the arrow at the bottom of the page to return to the Publication Channel Maintenance page.

Step 15. (Optional) Add additional Issues as needed.

Step 16. Click the arrow at the bottom of the page to return to the Brand Maintenance page.

Step 17. (Optional) Add additional Publication Channels as needed.

Step 18. (Optional, only if multiple Publication Channels have been created) From the Default Publication Channel list at the top of the Brand Maintenance page, choose the default Publication Channel that should act as the default Facebook channel.

Note: In order for this feature to work properly, it is imperative that an order sequence for the created Issues is correctly specified on the Publication Channel Maintenance page. If this is not done (or not done correctly), Enterprise may not be able to properly determine the Previous and Next issues.

Figure: The Default Publication Channel list.

Step 19. Click Update.

Info: This feature requires Enterprise Server version 9.1 or higher.

Step 3. In the Name field, enter a name.

Step 4. In the Description field, enter a description.

Step 5. From the Publication Channel Type list, choose Web.

Step 6. From the Publish System list, choose Twitter Publishing Connector.

Step 7. Leave the Suggestion Provider option set to None.

Step 8. Click Create.

New items appear on the page:

• An additional property named 'Current Issue' appears below the Publication Channel Type property. Since Issues still need to be set up, we will come back to setting this option later in the process.

• Below the Publication Channel properties area, a section for adding Issues appears.We will add these now.

Creating Issues

Step 9. Click Add Issue.

The Issue Maintenance page appears.

Step 10. Fill out the details.

Note: At the most basic level, only a name needs to be entered; all other options can also be set at a later stage by modifying the created Issue.

• Name. Name of the Issue.

• Subject. This feature is currently not functional.

• Description. Description of the Issue.

• Active. Use to deactivate the Issue. This will hide the Issue and all objects assigned to the Issue from the users without actually removing the Issue from the system.

• Consumer Key: Obtain this from the Application Details page for your app on https://dev.twitter.com.

• Consumer Secret: Obtain this from the Application Details page for your app on https://dev.twitter.com.

Step 11. Click Update.

Finishing the setup

Step 12. Click the arrow at the bottom of the page to return to the Publication Channel Maintenance page.

Step 13. (Optional) Add additional Issues as needed.

Step 14. Click the arrow at the bottom of the page to return to the Brand Maintenance page.

Step 15. (Optional) Add additional Publication Channels as needed.

Step 16. (Optional, only if multiple Publication Channels have been created) From the Default Publication Channel list at the top of the Brand Maintenance page, choose the default Publication Channel that should act as the default Twitter channel.

Note: In order for this feature to work properly, it is imperative that an order sequence for the created Issues is correctly specified on the Publication Channel Maintenance page. If this is not done (or not done correctly), Enterprise may not be able to properly determine the Previous and Next issues.

Figure: The Default Publication Channel list.

Step 17. Click Update.

Info: This feature requires Enterprise Server version 9.2 or higher.

Step 3. In the Name field, enter a name.

Step 4. In the Description field, enter a description.

Step 5. From the Publication Channel Type list, choose Web.

Step 6. From the Publish System list, choose WordPress Publishing Connector.

Note: When this option is not available, make sure that the WordPress Enterprise Server plug-in is installed and enabled.

Step 7. (Optional, only when the auto-complete feature for tags is going to be used. See Linking WordPress tags to a Suggestion Provider). From the Suggestion Provider list, choose the provider for suggesting tags.

Note: The default Suggestion Provider in Enterprise is the one from OpenCalais.

Step 8. Click Create.

The Issues section appears.

Step 9. Click Add Issue.

The Issue Maintenance page appears.

Step 10. Fill out the details.

• Name. Name of the Issue.

• Subject. This feature is currently not functional.

• Description. Description of the Issue.

• Active. Use to deactivate the Issue. This will hide the Issue and all objects assigned to the Issue from the users without actually removing the Issue from the system.

Step 11. Click Update.

Finishing the setup

Step 12. Click the arrow at the bottom of the page to return to the Publication Channel Maintenance page.

Step 13. (Optional) Add additional Issues as needed.

Step 14. Click the arrow at the bottom of the page to return to the Brand Maintenance page.

Step 15. (Optional) Add additional Publication Channels as needed.

Step 16. (Optional, only if multiple Publication Channels have been created) From the Default Publication Channel list at the top of the Brand Maintenance page, choose the default Publication Channel that should act as the default WordPress channel.

Note: In order for this feature to work properly, it is imperative that an order sequence for the created Issues is correctly specified on the Publication Channel Maintenance page. If this is not done (or not done correctly), Enterprise may not be able to properly determine the Previous and Next issues.

Figure: The Default Publication Channel list.

Step 17. Click Update.