> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/page-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/page-hub/user/page-hub-5.0.0/functionalities.md).

# Functionalities

The Page Hub provides the user with the following functionalities:

1. Create print articles/copies: This feature allows the user to add articles to lists to prepare for print copies of the selected articles in the list.\
   This can be accessed using this button

   ![image-20231213-062448.png](https://api.media.atlassian.com/file/352ffdab-2b1d-4237-9f7d-66fb0e43a787/image?allowAnimated=true\&client=6745454c-8c85-4189-b109-1d42feacaadd\&collection=contentId-9831186734\&height=30\&max-age=2592000\&mode=full-fit\&token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI2NzQ1NDU0Yy04Yzg1LTQxODktYjEwOS0xZDQyZmVhY2FhZGQiLCJhY2Nlc3MiOnsidXJuOmZpbGVzdG9yZTpjb2xsZWN0aW9uOmNvbnRlbnRJZC05ODMxMTg2NzM0IjpbInJlYWQiXX0sImV4cCI6MTcwNDcwMjM5MCwibmJmIjoxNzA0Njk5NTEwfQ.i0QeNKJsmt05LfG-90QsaK6iH7XGLMuGLSy0P5Kj-Cs\&width=35)\
   \
   A user can select the following:<br>

   a. Channel (target channel for the copies)

   b. Publication date (for the target print articles)\
   c. List (to attach print copies to, the list needs to be created before copying)\
   d. Search articles to be copied and whos print copies will be added to the list, selected above\
   e. Create print copies of the selected articles and add to the selected list<br>

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/DsWIe3FwY5T1NrrVYjEv/Create_List.webp" alt=""><figcaption><p>Create a list</p></figcaption></figure>

2. Create Run: A run can be created by a user to overwrite an existing edition or to create a new edition.\ <br>

   a. Select Product - This is the functionality to select a product, which exists in the Publisher software, from the drop down list. The results can be narrowed down by filtering through text search.<br>

   b. Select Date - The user will then select the date for which the Run needs to be executed.<br>

   c. Select Edition - An existing edition needs to be selected if the user wants to overwrite it or else the user will toggle the New Edition toggle button to enter the new edition name

   ![image-20231207-054736.png](https://api.media.atlassian.com/file/6c36534e-8974-40a6-9d84-2cd7821fe460/image?allowAnimated=true\&client=6745454c-8c85-4189-b109-1d42feacaadd\&collection=contentId-9831186734\&height=16\&max-age=2592000\&mode=full-fit\&token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI2NzQ1NDU0Yy04Yzg1LTQxODktYjEwOS0xZDQyZmVhY2FhZGQiLCJhY2Nlc3MiOnsidXJuOmZpbGVzdG9yZTpjb2xsZWN0aW9uOmNvbnRlbnRJZC05ODMxMTg2NzM0IjpbInJlYWQiXX0sImV4cCI6MTcwNDcwMjM5MCwibmJmIjoxNzA0Njk5NTEwfQ.i0QeNKJsmt05LfG-90QsaK6iH7XGLMuGLSy0P5Kj-Cs\&width=29)<br>

   d. Once the Product and Date are selected the corresponding Dial, AdStack and StoryList values available in the Publisher software are available in the dropdown list<br>

   e. The user then selects the Dial, AdStack and StoryList and then the Run button is enabled.

   ![image-20231207-055214.png](https://api.media.atlassian.com/file/65eb30a5-5b09-467c-aaa2-47af007cc24f/image?allowAnimated=true\&client=6745454c-8c85-4189-b109-1d42feacaadd\&collection=contentId-9831186734\&height=31\&max-age=2592000\&mode=full-fit\&token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI2NzQ1NDU0Yy04Yzg1LTQxODktYjEwOS0xZDQyZmVhY2FhZGQiLCJhY2Nlc3MiOnsidXJuOmZpbGVzdG9yZTpjb2xsZWN0aW9uOmNvbnRlbnRJZC05ODMxMTg2NzM0IjpbInJlYWQiXX0sImV4cCI6MTcwNDcwMjM5MCwibmJmIjoxNzA0Njk5NTEwfQ.i0QeNKJsmt05LfG-90QsaK6iH7XGLMuGLSy0P5Kj-Cs\&width=24)<br>

   f. The user can then click the Run button to start a run. While a Run is in progress the user can see the Run go through important Publisher stages which are:

   &#x20; i.  Added

   &#x20; ii.  Fetch

   &#x20; iii.  AdStack

   &#x20; iv.  Block Build

   &#x20; v.  Laydown

   &#x20; vi.  Page Build\
   \
   Each stage have a status color of grey, orange, green and red. They mean the following:\
   Grey - Stage not initiated\
   Orange - Stage in progress\
   Green - Stage completed successfully\
   Red- Stage encountered error

   Along with the statuses the user will also get notification in the Page Hub application and slack notifications can also be configured to send each run details over a pre determined slack channel.\ <br>
3. Publish Artifacts: Once a Run is successfully completed the Publish Artifacts button is then enabled which allows the user to to publish the successfully created Run artifacts (PDF and INDD files) to a predefined location which is configured in the Publisher software side.\
   \
   ***Note:** From Page Hub Version 4.2.0 the Publish artifacts (export) settings are configurable from Page Hub settings under* [*Export tab*](/page-hub/admin/settings/configuration/page-hub-plugin/export-config.md)*.*\
   &#x20; *1. All editions that were run before Page Hub Version 4.2.0 if their pages need to be exported* \
   &#x20;     *again from Page Hub Version 4.2.0 then make sure the run is executed again and file naming* \
   &#x20;     *conventions are not updated in latest run (should be same as old edition)*\
   &#x20;*2. Export configuration needs to be done before using Publish Artifacts after upgrading, since this* \
   &#x20;     *the old export functionality is no longer supported.*<br>

   ![image-20231207-063740.png](https://api.media.atlassian.com/file/3fd4db5f-411a-4416-95c5-b2e9458434db/image?allowAnimated=true\&client=6745454c-8c85-4189-b109-1d42feacaadd\&collection=contentId-9831186734\&height=43\&max-age=2592000\&mode=full-fit\&token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI2NzQ1NDU0Yy04Yzg1LTQxODktYjEwOS0xZDQyZmVhY2FhZGQiLCJhY2Nlc3MiOnsidXJuOmZpbGVzdG9yZTpjb2xsZWN0aW9uOmNvbnRlbnRJZC05ODMxMTg2NzM0IjpbInJlYWQiXX0sImV4cCI6MTcwNDcwMjM5MCwibmJmIjoxNzA0Njk5NTEwfQ.i0QeNKJsmt05LfG-90QsaK6iH7XGLMuGLSy0P5Kj-Cs\&width=60)

   &#x20;

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwssVGUYE79h6mkTDGzzC%2Fuploads%2FF1CShQUEKHWbqKUkyilx%2FStart_New_Run.mp4?alt=media&token=b6d9c256-eda8-447e-a36e-349ae0eb4448>" %}
Start a New Run
{% endembed %}

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwssVGUYE79h6mkTDGzzC%2Fuploads%2Fi5nXV3zSeGpm9XPZvIyi%2FPublish_Artifacts.mp4?alt=media&token=16fe7067-d7e0-42a8-bf64-371bd4f288a7>" %}
Publish Artifacts
{% endembed %}

4. Page Options: There are options on each page for a user to perform actions, the most important features are:

   a.  Freeze Page - This will mark the page as frozen which is used to prevent any updates from Publisher in any upcoming Runs.<br>

   b.  Page - This allows the user to perform three functions:<br>

   &#x20;i.  Check out and download - A user can download the page as INDD file and edit the page locally in Adobe InDesign.<br>

   &#x20;ii.  Upload and check in - A user can upload a page in INDD format. When checking in a locally edited page, the page automatically gets Frozen.<br>

   &#x20;iii.  Reset checkout - A user can reset the checkout that was done on a page.
5. Override Section: Page Action options provide an option to override the section of the Page(s) by selecting the new section from the Section Sub menu.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FizXG8k6g5AsBnbsMlphh%2Fuploads%2FlJzB8N8n1gZdOVAoOS6i%2FPageHub%204.3.0_Section%20override_Stage.webm?alt=media&token=2ba38f1c-e8c4-4f1d-ac3e-7888c199c285>" %}
Override Section
{% endembed %}

6. Configurable Display name for product and page names in Page hub using Page hub configuration.

PageHub now supports configurable display names for products in the product dropdown selector. The transformation is applied as per the new config area, and filtering operates on display names. If a display Product name is missing in config, the original product name is displayed.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/KyWT5VJ2rWRUdS9AigbQ/Display%20product%20name%20PH.png" alt=""><figcaption><p>Display Product name</p></figcaption></figure>

PageHub now supports configurable display names for Pages. The transformation is applied as per the new config area. If a display name config is missing, the Publisher name is displayed as Page names.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/kAKPxkM922q30l9T6k1Z/Display%20page%20name%20PH.png" alt=""><figcaption><p>Display Page name</p></figcaption></figure>

7. UI enhancements on “PageRobot Cloud config” dialogue box in Page hub configuration. In the new UI, the currently available files on the server will be displayed based on the selected organization or product.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/YHdaJEbVr6pV8hBZTdBg/PRC%20UI.png" alt=""><figcaption></figcaption></figure>

8. The width of the StoryList dropdown on PageHub adjusts dynamically based on its content.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/aHF9IYIlVVtHsLHOOlbO/storylist%20dynamic.png" alt=""><figcaption></figcaption></figure>

9. Jumps Visualization on Page Hub - In PageHub, an orange ribbon is used to visualize Jump documents by indicating both Jump start Page and the jump page. It also supports if a jump story needs to go to a double truck Pages.

**Example :** An article starts on page 2 and jumps to page 9. Both pages have the same jump section set and highlighted with orange ribbon.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/v9SHBCM6jAwGLVhwPN2E/Pagehub_Jump.png" alt=""><figcaption><p>Jump Visualization on Page hub</p></figcaption></figure>

#### Important points related to jumps:

| Observation                                                                                                                                                                                                                                                                               | Category    |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
| <p></p><p>The following elements are supported:</p><ul><li>Preamble</li><li>Citation</li><li>Fact</li><li>Byline</li><li>Images</li><li>Kicker</li><li>Image Caption</li><li>Headline</li></ul>                                                                                           | Requirement |
| Jump headline is mandatory for an article to jump from one page to another in the current version.                                                                                                                                                                                        | Requirement |
| If image or any other element coordinates are present but no image exists, the run fails at the PageBuild step due to missing UID.                                                                                                                                                        | Gaps        |
| No error messages are thrown for missing elements in Jump articles, as Flow only uses coordinates and doesn't receive the image UID.                                                                                                                                                      | Gaps        |
| Dummy IDs set in laydown files still lead to PageBuild failures if the image is not actually present.                                                                                                                                                                                     | N/A         |
| When Jump articles of different category (news, sports etc) and of same jump section are placed together on the front page, after section overrides are done, these articles jump to the landing page, but the related articles get removed.                                              | Design      |
| Jump articles have a unique priority (Priority X) that governs their placement.                                                                                                                                                                                                           | Design      |
| New page flag is not mandatory for Jump articles; position in the story list setup determines their placement.                                                                                                                                                                            | Requirement |
| Meta section is not required for Jump articles since the Jump plugin handles their placement.                                                                                                                                                                                             | Design      |
| <p></p><p>If a Jump article does not jump from the front page (source page) to the landing page:</p><ul><li>The orange ribbon will not appear on the jump page.</li><li>metadata.json and getdata API will return "jumpDocument": false.</li></ul>                                        | Design      |
| <p></p><p>A Jump article won't jump to a landing page if:</p><ul><li>It is too small, or If the text line does not exceed the minimum number of line for overset that are configured in the MT setting for JUMP article.</li><li>The jump headline is missing in its jump data.</li></ul> | Requirement |
| <p></p><p>If there are multiple page sections with the same Jump Section name:</p><ul><li>Jump articles are placed on different pages.</li><li>The OC list positions must be distinct for each.</li></ul>                                                                                 | Design      |
| If a Jump article has coordinates configured but the element is not used in the article, the run fails at PageBuild.                                                                                                                                                                      | Gap         |
| Jump start pages can have multiple layout articles of the same Jump section.                                                                                                                                                                                                              | Requirement |
| <p></p><p>All coordinates must be correctly set in the Jump plugin to prevent:</p><ul><li>Overlapping articles</li><li>Incorrect content placement</li></ul>                                                                                                                              | Requirement |
| The Typography InDesign export option that needs to be configured or used for JUMP articles is "inddExportOptions": "single\_and\_multipages".                                                                                                                                            | Design      |
| When configuring the jump headline size or coordinates in the template, Flow selects the nearest available size. If no matching or nearby value is found based on the galleydump sizes, it will not place headline in required formats.                                                   | Gaps        |
| If the landing page does not have enough space to place the jump article, the layout for that page will not be generated, and the article on the source/front page will appear in overset                                                                                                 | Design      |
| If the any element position is not present in the template, then it will be placed on the landing page.                                                                                                                                                                                   | Design      |

## PRC Enhancements in version 4.5.0

* **Download** - You can now download settings from the server related to your product or organization
* **Delete -** Users can now perform deletion operations on server-stored settings for a given product or organization
* Settings dropdown now includes two additional options for ePape&#x72;**:** `epaperStoriesConfig` and `epaperStoriesTemplate`
* Bulk upload, download, and deletion of PRC settings is allowed.
* The product selection dropdown now includes a **‘Select All’** option to facilitate bulk actions across multiple products.
* Multi-select functionality has been introduced in the product selection menu for targeted bulk actions.
* Multi-select capability has been enabled in the settings menu, letting users perform bulk actions across selected settings tied to a product or organization.
* Generic UI changes:
  * Select files button renamed as **Upload**
  * Assignment type renamed as **Settings**
  * Product names list is alphabetically sorted in PRC
* Actions can be performed on PRC as per the below table:

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/HVsIlmwSOfKaNopZWeWS/PRC_4.5.0.png" alt=""><figcaption><p><strong>Tick</strong> means <strong>action</strong> can be performed, <strong>Cross</strong> means action can not be performed</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/gnvrevtumHxdzzfbbTZ6/PRC-upload-download-delete.png" alt=""><figcaption><p>Upload, Download and Delete settings on new UI</p></figcaption></figure>

## Pre Run from PageHub

A blank story "PreRun" will always pe present in story list once user select any product and date , it will allow user to create pages on pagehub before even have an actual story list is created.

Points to remember

* Pre-run story list will always be present in story list once user select any product and date.
* Dial and Adstack will be displayed as usual after selecting product, date and edition.
* Once all the required fields are set to trigger run, user can execute run with story list selected as “PreRun”.
* On successful run, pages gets created without any articles and only ads gets placed on pages as per the Adstack.
* Page hub configuration allows user to set display name for “PreRun” storylist by setting a key in the configuration. “PreRun” will be displayed by default and if display name is added in the configuration then same name will be displayed in the storylist instead of prerun.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/aKdeWKtfIRy7R4lzuhCG/prerun.png" alt=""><figcaption><p>PreRun in Storylist</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/QsaGfhBqE3Ce9g1BIYXD/greekrun.png" alt=""><figcaption><p>Display PreRun name in configuration</p></figcaption></figure>

## PageHub Run Details

Run Details in Pagehub provides a concise summary of the executed run. This enhancement enables user to quickly view the placement status of stories. This determines whether any story included in a storylist is placed on a page after execution. Additionally, the run details will offer key article details at a glance—such as whether the article is DT or MT, if it’s a new page, its priority level, and more.

User can access Run Details once run is executed successfully by clicking this button on the pagehhub. ![](https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/cZP8s2LMXeQW4ywoLvQu/image.png)

Run details will be presented in a pop up, highlighting following details:

1. Product, Date, Edition, Disal, Adstack, Storylist - These details will be same as selected in the pagehub for run.
2. Time: Represents run initiated time.
3. Story Name
4. Placed
5. PageName
6. Priority
7. Section
8. DT/MT
9. New Page
10. Overall status of the Run &#x20;

* "All stories placed" - when all articles in the selected storylist gets placed in run
* "Some stories unplaced" - when some articles left unplaced from the selected storylist in run
* "No Data found" - when the run deatils is not available to display in run details

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/xGc43mJSaZnMwuUMDVjP/Run%20list.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Point to consider:** User needs to do full rerun again after upgrading Pagehub to 4.5.0 version to view run details in. Run Details will not show any data for pre-existing runs of before upgrade and simply show “No data found” when user click on Run Detals button.
{% endhint %}

## Publish artifacts for failed run

Publish artifacts button is now enabled for failed executed runs which allows user to publish pages if they are available from previous run even if the rerun gets failed.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/Dsxw3V0IkXTmJhbB6oNZ/failedrun_PH.png" alt=""><figcaption></figcaption></figure>

### Runlist UI enhancements

In Pagehub version 4.6.0, enhancements were made to the Runlist feature to improve its usability and functionality.

* Warning icon now shown for unplaced articles
* Run List icon replaced with “notes-paper” icon.
* Story name is now clickable link to open the article in Writer.
* Story details are now displayed in order based on page number.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/CDgFpRxBWtQRT9QlnhKq/runlist%20enh.png" alt=""><figcaption></figcaption></figure>

The Runlist button remains disabled after a successful run using the 'Prerun' story list, as there are no actual stories to place. Consequently, the Runlist has no content to display.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/X17QZtsXeoGg6Pu9Cel0/runlist%20button.png" alt=""><figcaption><p>Disabled runlist button for "Prerun" story list</p></figcaption></figure>

## Ad File update notification

A new feature introduced in Pagehub version 4.6.0 allows users to detect Ad file updates within an Adstack. If an Ad file has been modified from the backend in the same Adstack, a notification is triggered when the user attempts to publish artifacts for that Adstack in the executed run from Pagehub.

{% hint style="info" %}
**Prerequisites for using the Ad file Update notification feature**

* Ensure the prod config.json includes "adstackExport":"true" to enable ad updates feature on the Publisher end.
* Make sure "Validate ads" toggle switch is set to ON in the PageHub configuration.
* A policy must be configured for the s3 Adsbucket to enable and support ad update functionality.
  {% endhint %}

This feature is configuration driven using the **"Validate Ads"** toggle button in Page hub configuration.

* When the toggle is turned ON, the system performs an Ad file update comparison check. If any updates are detected, the user is notified during the artifact publishing process.
* When the toggle is turned OFF, the system does not perform any Ad file update comparison check.
* By default, this toggle remains OFF.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/MfRpwVTKz3mx08QC8lps/validate%20Ads.png" alt=""><figcaption></figcaption></figure>

Ad file Update notification pop up appears on Publish artifacts after selecting pages from the run.

Pop up shows the selected page where Ad file update is detected, It allows user to select any one option to continue.

**Proceed**: If user clicks on 'Proceed' button, the popup will close, and the artifacts will be published using the old Ad file on the selected page.

**Cancel**: If user selects the 'Cancel' button, the popup simply closes. To place the updated Ad files on the pages, the user will need to rerun the edition.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/oIEXq3sRp4HdBHA42koA/Ad%20file%20update.jpg" alt=""><figcaption></figcaption></figure>

**Points to remember:**

* System works for Publish artifacts as usual if there is no change in Ad files.
* The file name of the updated Ad. file should remain same as the original file name to do Adfile update comparison check.
* This feature is only applicable for customers using an S3 bucket and does not apply to those with ads stored on a mapped drive.
* A policy must be configured for the `s3Adsbucket` to enable and support ad update functionality.
* For pre-existing runs before upgrade, Ad update notification would not trigger, ensure to rerun after upgrading to Page hub to 4.6.0 version.

### Run Details – Placement status of stories in Page-wise view

In PageHub version 4.7.0, Run Details are displayed in an enhanced page-wise UI, providing additional insights about stories such as stories placed with overset, marked as lead stories, or stories left unplaced on the planned pages.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/c5u30Z3gOn6WB3vprYNP/Run%20details%20as%20Pagelist.png" alt=""><figcaption><p>Run Details new UI</p></figcaption></figure>

* Run Details now open as a side slider instead of a pop-up window.
* Placed and unplaced stories are organized under their respective page numbers using accordion-style sections.
* **Lead Story Icon** – An icon has been added to indicate the lead story on each page.
* **Overset Icon** – Indicates stories placed with overset, shown both at the story level and the corresponding page level.
* **Overset Count** – Displays the number of overset lines in a placed story, indicated by an overset icon.
* **Expand/Collapse Icon** – Enables users to expand all pages to view the status of the stories under it. When collapsed, it hides the story list and display only the pages.
* **Sorting Icon** – Allows sorting of stories by 'Unplaced' or 'Page Number'. Clicking it moves all unplaced stories to the top of the list. By default, stories are sorted by page number
* **Filter** – A dropdown filter has been added to view all stories, only placed stories, or only unplaced stories.
* **Search bar**– A free-text search bar has been added to help users quickly find any story or page or section.
* **Information Icon** – Displays unplaced stories which could not be placed as more pages were not available in the section to place the story.

### Image toning from Page hub

PageHub introduces an advanced Image toning feature currently applicable using Intellitune service. This functionality enables precise post-processing of images to CMYK or Monochrome profiles set for pages that have been successfully built after a PageHub run.

With Image Toning, users can seamlessly convert page images to the desired CMYK or Monochromee profiles based on the [configuration ](/page-hub/admin/settings/configuration/page-hub-plugin/image-toning-config.md)defined in PageHub settings.&#x20;

Steps to apply the valid Image toning setting from config

1. **Product check,** If specific product is available in config, product specific settings would be applied, else default setting will be applied.
2. **totalpages** edition check, when user select an edition in page hub, depending on the total pages of an edition , config will be applied. If no config is available for that totalpages, Image processing will not be applicable for the edition.
3. **days check**, as per the edition selected for image toning, if that day config is available, defined CMYK/Monochrome settings will be applied, If no config is available for that day, Image processing will not be applicable for the edition.
4. **Page level check,** as per the pages selected in an edition for image toning, if that page is added in any profile of CMYK/Monochrome, Image processing will be done on those pages, if pages are not added in then Image processing will not be applicable for those pages.
5. Once all the settings criteria meet, Images on selected pages get converted in to desired CMYK/Monochrome.

**Visual cue on pages for Image toning**

* Icon display on pages applicable for Image toning.
* Icon display for Image toning process Success/Failure
* User can access **"Image Toning"** option from Page action menu and three dots at page level
* Pages will be frozen while the Image toning is in progress, however user can perform any other operations on other pages/editions.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/3bugeXqkSm8TiGsZcbOJ/image.png" alt=""><figcaption></figcaption></figure>

## Ad files update notification without rerun

The enhanced Ad Files Update feature introduced in Pagehub 4.9.0 enables users to preview all available ad updates within an Adstack before publishing. If any ad file in the same Adstack has been modified on the backend, Pagehub now triggers a notification when users check for ad updates—whether for the entire edition at once or for selected pages—ensuring they are aware of changes and update it before proceeding with export artifacts.

{% hint style="info" %}
**Prerequisites for using the Ad file Update notification feature**

* Ensure the prod config.json includes "adstackExport":"true" to enable ad updates feature on the Publisher end.
* Make sure "Validate ads" toggle switch is set to ON in the PageHub configuration.
* A policy must be configured for the s3 Adsbucket to enable and support ad update functionality.
* Ad files must be uploaded at the exact location defined in metadata(**Base Path + Relative Path** structure)
  {% endhint %}

#### **Ad File Update notification workflow on Ad updates option**

When a user selects one or more pages—either individually or using **Select All** within an edition—and clicks **Ad Updates** option from the page action menu, a notification popup appears indicating that updated ad files have been detected.

The popup displays:

* The list of selected pages where an ad file update is available
* The corresponding ad file names
* Action options for the user to proceed

**Update:** When the user selects the Update option, the popup closes and the system immediately begins processing the Ad Files Update for all selected pages. During this process, updated ad files are applied to the pages where changes were detected. Once the update completes, the system displays a status message indicating whether the new ad files were successfully placed, ensuring users receive clear feedback before moving forward with publishing.

**Close**: When user selects the 'Close' button, the popup simply closes.

**Visual cue on pages for Ad updates**

* Icon display for Ad Updates process Success/Failure
* User can access **"Ad Updates"** option from Page action menu and three dots at page level
* Pages will be frozen while the **Ad update** is in progress, however user can perform any other operations on other pages/editions.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/Uls4LLe0NCmbY5G7mKua/Ad%20updates%20pop%20up.png" alt=""><figcaption><p>Ad file update Notification on checking Ad updates</p></figcaption></figure>

#### **Ad File Update notification workflow on Publish Artifacts**

When a user selects one or more pages—either individually or using **Select All** within an edition—and clicks publish artifacts, a notification popup appears indicating that updated ad files have been detected.

The popup displays:

* The list of selected pages where an ad file update is available
* The corresponding ad file names
* Action options for the user to proceed

**Update:** When the user selects the Update option, the system triggers processing the Ad files update for all selected pages. New Ad files will be placed on the pages where changes were detected.

Once the ad files are successfully updated on the selected pages, publishing the artifacts will proceed without triggering any further Ad File update notifications.

**Publish**: If user clicks on 'Publish' button, the popup will close, and the artifacts will be published using the old Ad file on the selected page.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/PwkVWEh6UlgOBTxIdffZ/Ad%20update_publish.png" alt=""><figcaption><p>Ad file update Notification on publish artifacts</p></figcaption></figure>

**Notifications for Ad Updates:**

* **"No New Ads Available"**: When a user selects any page and checks for Ad Updates, the system will display a “No New Ads Available” notification if no ad file changes are detected for the selected page(s).
* **"No Updates available: Ad file is missing or file name has been changed":** When a user selects any page and checks for Ad Updates/Publish artifact, the system will display this notification if ad file has been deleted or Ad file name has been changed for that page.
* **"Adsbucket not available":** When a user selects any page and checks for Ad Updates, the system will display this notification if, **adsbucket** is not available from publisher for that product.

**Points to remember:**

* System works for Publish artifacts as usual if there is no change in Ad files.
* The file name of the updated Ad. file should remain same as the original file name to do Adfile update comparison check.
* This feature is only applicable for customers using an S3 bucket and does not apply to those with ads stored on a mapped drive.
* A policy must be configured for the `s3Adsbucket` to enable and support ad update functionality.

## Run details for all pages within an edition

The enhanced Run Details introduced in Pagehub 4.10.0 allows users to view run information for all pages within an edition—including both the latest run pages and previous runs—in a single Run Details window. Latest and previous runs are distinguished using the user icon and timestamp indicators.

**Additional info display in Run details for each page.**

* **Timestamp :** When the page was executed
* **User:** Who executed the page
* **Story List:** If pages were executed with different story lists in the same edition

1. **Sort by Latest:** A new icon in the run details view allows users to sort pages by the most recent run. When selected, pages from the latest run are moved to the top of the list. By default, pages remain sorted by page number.
2. **User icon(Latest run):** This icon indicates that a page is part of the latest run. It appears only on pages included in the most recent run. On hover, it displays the user and timestamp—showing who executed the page and when with the latest story list.
3. **Timestamp:** This indicator appears on pages that are not part of the latest run but were included in a previous run. It shows when the page was last executed. On hover, it displays the user and associated story list—indicating who executed the page and with which story list.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/jurYudCAr8a9EzlC7q8R/rundetails%20all.png" alt=""><figcaption></figcaption></figure>

## Selectable destinations for artifact publishing

Pagehub v4.10.0 introduces a new feature that allows users to choose the destinations for exporting artifacts. Based on the [destination configuration](/page-hub/admin/settings/configuration/page-hub-plugin/export-config.md#select-destination-to-publish-configuration) defined in the export settings, the system prompts users to select one or more destinations during the publishing process.

{% hint style="info" %}
**Prerequisites for using the select destination feature**

* Ensure Export config have valid configuration for export
* Make sure "Select destination" toggle switch is set to ON in the PageHub configuration.
  {% endhint %}

This feature is configuration driven using the **"Select Destinations"** toggle button in Page hub configuration.

* When the toggle is turned ON, the system prompts the user to select destinations from the available options before publishing artifacts.
* When the toggle is turned OFF, the system does not prompt the user to select destinations and publish artifacts on all destination as per export config.
* By default, this toggle remains OFF.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/utkEuUcwXWgiIB1zrTGN/destination%20toggle.png" alt=""><figcaption></figcaption></figure>

Once the select destination configuration is set in Export config then selecting publish artifact prompts the user by showing popup to select the destinations before publishing artifacts.

Pop up should display following

* All destinations defined in Export config (S3/FTP/SFTP)
* Destination name if Label is added in config, else hostname/bucket name
* Publish and Close

**Publish:** When destination(s) are selected in the pop‑up and **Publish** is clicked, the artifacts are published exclusively to the selected destinations.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/9yPlWgZvlMToyBCBCriU/destinations%20multiple.png" alt=""><figcaption><p>Select destinations to publish pop up</p></figcaption></figure>

## View publish logs for export activity

As part of Pagehub v4.10.0, a new feature enables users to view detailed logs of export activity, including publishing individual pages or entire editions across different formats and destinations.

**Log Access Points:** The latest publish details are available via a Publish Log icon at the page preview level and in Run Details (page name bar). The icon appears for pages published after the latest run, with hover details showing recent export information. Failures are indicated by a red icon.

**Run Details – Publish Logs View:** A new **“Publish Logs”** toggle (default: OFF) is added to the Run Details screen. When enabled, it displays all (latest and previous) publish logs organized by page number in accordion-style sections.

**Log Details:** On expanding the Page accordion, logs are shown in a table with User, Timestamp, Destinations, and Formats—indicating who exported what, where, and when. Failed exports are highlighted with a red format indicator, with hover details showing the failure reason.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/zdaqPRLAdgWFob0NF8wA/publishlog.png" alt=""><figcaption></figcaption></figure>

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDZrqz9xq4gVo05YJuivu%2Fuploads%2F7dcUCyDB8faUhyToU6YJ%2FPublish_Logs%20-%20Copy.webm?alt=media&token=5417508f-f557-4c2c-9356-550e3a92bb9e>" %}

### Run details - publish logs tab view

As part of Pagehub v4.10.1, updates have been made to the Run Details UI:

* The expand/collapse icon has been updated.
* The toggle for Publish Logs has been removed. Run Details and Publish Logs are now displayed as separate tabs.
* The **Run Details** tab displays the run details of the edition.
* The **Publish Logs** tab displays the publish log artifacts of the edition.

<figure><img src="https://content.gitbook.com/content/QnMd5AGOoQD2wDuC4Ndb/blobs/WSvhKxql7rUud2VF1HW9/image.png" alt=""><figcaption></figcaption></figure>

### Quick Edit

**Quick Edit Permission Control**

When the Quick Edit plugin is installed and configured, the required permission `pagehub:quickedit` must be assigned at the organization OR group level.

* Users with the `pagehub:quickedit` permission will see the **"Check Out in Quick Edit"** option in the Page Actions menu within the Page Hub preview.
* Users without the `pagehub:quickedit` permission will not see the **"Check Out in Quick Edit"** option.

<figure><img src="https://3991652910-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQnMd5AGOoQD2wDuC4Ndb%2Fuploads%2FZrHbB6V4bQqWmKMYVZLI%2Fimage.png?alt=media&amp;token=ba494e59-b406-4e89-a0df-031160823547" alt=""><figcaption></figcaption></figure>

**Editing Text with Quick Edit**

From the Page Hub page preview, users can open the page action menu and select **Page > "Check Out with Quick Edit"**. This launches the Quick Edit editor, enabling users to make text corrections directly within the rendered page(.indd) and save changes instantly.

**Editing Headline of the article**

<figure><img src="https://3991652910-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQnMd5AGOoQD2wDuC4Ndb%2Fuploads%2FOfy3tJBqG1AHYCcFm43t%2Fimage.png?alt=media&amp;token=23bb1f17-aec3-439b-a15c-61c5c59fb619" alt=""><figcaption></figcaption></figure>