Example
|
Phase 0: Prepare for Publish: constructs context Phase 1: Validate and Remove Empty Content Phase 2: Traverse and build context Phase 3A: Perform extractions (concurrent with 3B) Phase 3B: Perform renditions (concurrent with 3A) Phase 4: Generate TOCs Phase 5: Render and Extract Generated TOCs Phase 6: Recalculate Checksums Phase 7: Bulk Volumize and Refresh Volumes Phase 8: Generate Auto TOCs on Volumes Phase 9: Render and Extract generated auto TOCs on Volumes Phase 10A: Generate Publish Readiness Report (concurrent with 10B) Phase 10B: Generate Link Inspector Report (concurrent with 10A) Phase 11: Finish Prepare for Publish: update statuses, determine overall success |
The Prepare to Publish phases (options) run in the order shown in the list (which can be seen in the Job Request page - phases that can run at the same time are labeled a/b of the same number). When the Prepare to Publish is canceled, the currently running phase will finish and then the Prepare to Publish will stop and any subsequent selected phases will not be executed. The exceptions to this are the pairs of phases, which must both be completed before the Prepare to Publish will be canceled.
Maximum Job Message Length
Be aware that some information in job messages is cut due to limit in characters. All job messages are truncated at 2000 characters. Because of this limit, you may not see the entire set of information that is generated by a job message.
For example, if you run Remove Empty Assembly Leaf Elements a job message listing all of the empty leafs and folders that were deleted is generated. Ennov InSight can only display the first 2000 characters in the job message, so you may not see the entire list of deleted empty leafs and folders.
Publishing Summary Query
The Publishing Summary Query displays the assembly elements in a tree hierarchy that you can export to a comma-separated file (CSV). You can import the CSV file into Microsoft Excel spreadsheet for further analysis. The Publishing Summary Query displays each component in the assembly, its types and sub-types, and indicates leaf options:
— Whether a leaf has at least one child document
— Whether the leaf has any overridden attributes with renditions
Generate a Publishing Summary Query
The Publishing Summary Query displays the assembly elements in a tree hierarchy that you can export to a comma-separated file (CSV). You can import the CSV file into Microsoft Excel spreadsheet for further analysis.
To generate a Publishing Summary query:
- Click a link for the assembly you want to publish.
- From the action toolbar, choose Publishing Summary Query. The Publishing Summary query opens.
- When you are finished reviewing the summary query, click Back.
Publishing Readiness Query
The Publishing Readiness Query enables you to view your assembly metadata at a glance and find predicted errors and warnings that may occur during publishing if an issue is not remedied.
The following information is included in the query results:
— The assembly name
— Element types and subtypes
— Default attributes that have been overridden
— Whether each leaf element includes at least one assigned document
— Whether documents are set to Use Native File
— Whether PDF renditions are available for each assigned document
— Output location information
— Number of bound documents and total documents
When you generate the query, you choose the columns that appear in the query results. You can export the query results to a Microsoft Excel spreadsheet for further analysis. The table in Publishing Readiness Query Attributes describes the information you can include in the query.
Warning: Always run a DMS Synchronization before refreshing the Publishing Readiness query, Link Inspector query, and other queries. Ennov InSight uses the data available in the Ennov InSight database, and relies on DMS Synchronization to ensure this information matches what is in the DMS for each document.
Publishing Readiness Query Filters
You use the filters in the Publishing Readiness query to return details about the assembly. The required filters are indicated by an asterisk (*).
| Column | Description |
| Assembly * | The current assembly is selected by default. You can select the other assembly, if needed. |
| Column | Description |
| Query Type |
The following types are available for selection: — Electronic — Paper The Electronic type is selected by default. Deselect, or add the other type, if needed. |
| Leaf Operation |
The following operation types are available for selection: — append — delete — new — replace You can select multiple operations. |
| Object Type |
All types are selected by default: — Cover Page — Document Folder — Leaf — Slip Sheet — Table of Contents — Volume You can deselect any type, if needed. |
|
Filter on Elements that have Errors |
The Yes and No values are available for selection, Yes is selected by default. You can change the value, if needed. |
| Display Columns * | You can select the columns you want to be displayed in the Publishing Readiness Query results. You also can change the columns order. |
| Sort Order |
You can select how to sort the columns in the query results table. The values available for selection are: — The list of all columns with an ascending or descending options. For example: Element Type - DESC. — Order - ASC — Order - DESC The ascending order (Order - ASC) is selected by default. You can deselect or add the other types, is needed. |
Publishing Readiness Query Attributes
You can use the attributes to describe the Publishing Readiness of an assembly. The attributes are valid for all elements of an assembly, unless otherwise noted.
| Column Name | Description |
| Actual Page Count | The actual number of pages in the element. |
| All Pages Included | Indicates whether all pages in documents are to be published. |
| Application Version | An eCTD attribute. |
| Assembly Level | The relative level in the assembly where the element has been assigned. For example: the assembly root is 0, folders under the root are 1, the first element in folders is 2, and so on. Aligned TOCs and special sheets are assigned numerically, immediately after the element to which they are assigned in the order they appear, from left to right. Volumes are level 1 for a Paper Report Type, and folders are level 1 for an eCTD Report Type. |
| Element Empty |
Indicates whether the folder or leaf element contains children. If a leaf or folder is empty, it is a candidate for deletion during Prepare To Publish. Leaf files are considered by the system to be empty when they are “default” type, as opposed to “reference” type. Default leafs are considered by the system to be empty when the leaf contains no child documents. — If a default type leaf contains a planned or placeholder document, it is considered not empty. — If a default type leaf has aligned TOCs or Special Sheets, it is still considered empty. — A Leaf Operation with a value of DELETE will be marked as empty, but will not be deleted as part of Prepare for Publishing (both eCTD and Paper). Valid for Folders and Leafs and Volumes. |
| Element Name | Inherited from the Element Name provided in the element attributes. If there is no “Element Name” the system provides a value of NA. |
| Element Number |
Elements may contain an element number in addition to the element name, and sometimes instead of an element name. In these instances, an element number is provided. Element Number is valid for volumes, folders and leaf elements only. For leaf elements, the value should also contain the parent folder number. |
| Element Path | The location of the element in the assembly, including ancestry. (Element Path is similar in concept to "breadcrumbs".) Generations (levels in the assembly) are separated by backslashes (or some other character) in the Element Path. Valid for all elements except volumes. |
| Column Name | Description |
| Element Type | Describes the element. For example: Assembly Root, Folder, Leaf, Reference Leaf, Volume, Document, TOC, Cover Page, Tab, Slip Sheet, Placeholder. |
| Error and Warning Count | Indicates the number of errors detected. |
| Error and Warning Details | Detailed information about errors and warnings. |
| Extended Attributes | Lists extended attributes for the element. |
| Extended Subtype | Describes the subtype for the element. |
| Extracts Exist |
The “Extracts Exist” value pertains to the system’s captured data about the document’s PDF Rendition bookmarks. This value is assigned by the system as a default value and can be overridden in document element attributes. — If the Extracts Exist value is set to Y (Yes), the system pulls the extracts from the PDF Rendition and populates those values for use in TOC generation. — If the Extracts Exist value is set to N (No), the system does not pull the extracts from the PDF Rendition; any previously pulled extracts are used in the creation of TOCs. |
| Font Library | The repository data file for the fonts. |
|
Has Open Activities |
Indicates whether there are active activities associated with the node. |
| Included in Page Numbering | Indicates the application of page numbers to the documents, cover pages, TOCs, and the system’s inclusion of those elements in page number calculations for other elements. |
| Inherited Attributes | Lists the inherited attributes for an element. |
|
In Process Rendition Status |
Indicates that status of an in-process rendition for: — Bound documents (in the case of leafs) — Bound documents encapsulated by a leaf element Leaf Elements flagged for native file will have a value of N/A or blank. Reference Leaf Elements will have a value of N/A or blank. A value of Yes indicates that the in-process rendition is current, while a value of No indicates that a new inprocess rendition should be created to reflect changes to the documents. |
| Language | The language used in the assembly. |
| Leaf ID | An eCTD attribute, valid for leaf elements only. The leaf ID number. |
| Column Name | Description |
| Leaf Status | The value of the Leaf Status attribute from the leaf element. Valid for a leaf element only. |
| Modified File | An eCTD attribute, valid for leaf elements only. Indicates that a file has been modified. |
| Operation | An eCTD attribute, valid for leaf elements only. New, Replace, Append, and Delete are leaf operations. If the operation on a leaf is New and the leaf has a value for modified file, an error is reported indicating Inconsistent Lifecycle; a new leaf cannot have a modified file value. If the operation on a leaf is Replace, Append, or Delete, and the modified file attribute does not have a value, an error is reported indicating Inconsistent Lifecycle; a modified leaf must indicate its modified file. |
| Order | A system generated value depicting the order from top to bottom for the element. |
| Output Filename | The name the output file receives at publishing time. Inherited from the Element Name provided in the element attributes. If there is no “Output Filename” associated with the element, the system will provide a value of NA. Valid for Volumes and Leaf Files. |
| Note: Underscores are stripped out of file names instead of being converted into dashes in the output file name. | |
| Output Path | Lists the repository path to where the element is published. Inherited from the Element Name provided in the element attributes. If there is no “Output Path” associated with the element, the system provides a value of NA. Output Path is valid for Volumes and Leaf Files. |
| Output Channel | Indicates the output channel: Paper Output Channel, Electronic Output Channel, eCTD Output Channel. |
| Overwritten Attributes | Indicates the values for Folder and Leaf attributes that would otherwise be inherited from a parent or root defined attributes, but have been overwritten by the user. |
| Planned Page Count | Indicates the total number of planned pages represented by this element. |
| Rendition Exists |
Indicates whether a PDF rendition is associated with the element. The “Rendition Exists” value pertains to the presence of a current PDF Rendition for the bound document. This value is assigned by the system in document element attributes. The value of “Rendition Exists” is set by the system for PDF renditions created. Valid for documents. |
| Column Name | Description |
| Rendition File Size | Indicates the file size of the leaf file or volume. |
| Section | The folder or leaf in the assembly that is being queried. |
| Tab Text | Provides the resolved Tab Text (if known by the system). |
| Use Native File | Indicates whether to use native file format or to create a PDF for output. |
Generate a Publishing Readiness Query
The Publishing Readiness Query enables you to view your assembly metadata at a glance and find predicted errors and warnings that may occur during publishing if an issue is not remedied.
Warning: Always run a DMS synchronization before refreshing the Publishing Readiness query, Link Inspector query, and other queries. Ennov InSight uses the data available in the Ennov InSight database, and relies on DMS synchronization to ensure this information matches what is in the DMS for each document.
To generate a Publishing Readiness query:
- Click a link for the assembly you want to publish.
The Assembly Attributes page opens.
- Right-click the assembly root and choose Publishing Readiness Query. The Publishing Readiness Query dialog box opens.
- Under Selected Columns, choose any data you do not want to include in the query and move it to the Available Columns box.
- Optionally choose selected columns and click up or down to change the order in which columns appear in the query.
- Do one of the following:
Option Action To generate the query results: Click Search. To clear your choices and start again: Click Reset. To save your choices as a query that you can use again: Click .png)
. - Do one of the following:
| Option | Action |
| To return to the Publishing Readiness Query page: | Click Back. |
| To export the query results to a comma-separated file: | Click  . |
Browse for an Assembly
Use the tabs and buttons in the dialog box to locate and select the assembly for which you want to generate the Publishing Readiness query.
To select an assembly:
- Click the tab for the entity type you want to choose.
- Select the entity, and then do one of the following:
| Option | Action |
|
To choose one of the following: — All shows all entities. — Current includes all entities with a status of current. — Submitted includes all entities that have been submitted to the regulatory agency. — Approved includes all entities that have been approved by the regulatory agency. |
Click the Show Versions arrow. |
| To see the content of the entity you choose: | Click the Show button. |
Publishing Requests
This feature enables you to query tasks that are directly or indirectly associated with publishing. You can use Job requests to view the status of the operations such as publishing jobs and print or view an output log from a completed job list.
For all publishing jobs:
— Documents are rendered (for customers who have licenses for rendering and publishing services).
— Links are resolved.
— Rendered documents are concatenated.
— Variables are resolved.
— TOCs may be regenerated.
— Overlay preferences are calculated and applied.
— Special sheets are inserted as appropriate.
— Output files are created in the document repository with the appropriate names, locations, and metadata. — Any errors and warnings are noted in the job requests.
— Ennov InSight Publisher will not re-render or re-extract documents that have been checked in as the same version in a DMS. However, you can manually re-render and re-extract documents by right-clicking on any document and creating renditions and extractions or using Force New Renditions and Extractions functionality. This will refresh all links, bookmarks, and page count data as well as rendering the document.
— When you publish .pdf document that has a rendition, source .pdf document, not the rendition is used for publishing.