Prerequisites

When you manage a PDS in GPP, certain conditions apply:

— You must have the licenses and privileges to use the GPP features, a PDM license with at least WRITE privileges, and WRITE privileges for each affected PDS entity.

— The event must be open.

— The project must have been created in the GPP wizard as a Create New Applications - Package Set Registration project.

— A PDS template must be available for the product selected.

— None of the countries associated with the events tied to the project have an actual status date for a status of Approved, Not Approved, or Withdrawn (or the equivalent statuses mapped by your data manager for your application).

— If the product has an associated PDS, the GPP wizard replaces the entire PDS with an updated PDS until the event is submitted or approved.

— All the PDSs associated with the events for the project have only Pending details (or the equivalent status mapped by your data manager).

To manage the PDS associated with the project in GPP:

1. On the Home page, click Projects.

   Your projects are listed on the Projects page.

2. Click the name of the project that you want to manage.

   The Project Attributes page appears.

3. Click Associate.

   The Manage PDS wizard opens to the Select Product page.

4. Select a product.
5. Click Next.

   The Select PDS Template page appears.

6. Select the PDS template you want to use to create a PDS for the product selected.

   Note: If you entered a comment in the Add Comment field of the template, the comment is not carried forward to the PDS that you create.

7. Click Next.

   The wizard displays a confirmation message indicating that a PDS will be created and associated with the project events.

8. Click Next.

   The wizard opens the Summary page that summarizes the actions taken.

9. Click Finish.

When you finish this procedure:

— Ennov InSight creates a PDS from the selected PDS template for each application associated with the project and automatically associates the new PDS with the event associated with the project.

— The product selected is automatically associated with the project applications and events, if the product was not associated with the application before the wizard was run.

— The product is automatically associated with the project events, if the product was associated with the application before the wizard was run, but not previously associated with the project events.

— Any existing PDSs for the selected product that were associated with project events before the wizard was run are disassociated from the project events.

— The previous PDSs are deleted from the system, if only one event was associated with the PDS before the wizard was run.

Leaf Updates for Assemblies

Use the Leaf Update for Assemblies wizard to update "list of document assemblies" for existing projects that have associated planned sequences.

Limited functionality around assemblies has been extended to Ennov InSight customers with an SPT license that enables you to centrally manage changes to documents for the purpose of notifying your regional publishing centers of the changes.

Using the Ennov InSight sequence and assembly functionality, you can create a list of leafs (documents) for each regional application. After the "assemblies" (the list of documents) are locked and lifecycled as sequence assemblies, you can use a GPP project to create new planned sequences for the regional center applications, and then use the Leaf Update for Assemblies wizard to update the leafs for the applications using a predefined template of New, Replace, and Delete operations.

Assemblies should not contain any folder elements. They should contain leaf elements and documents only.

The updates appear in the new working "assembly" created under the planned sequence for each application included in the GPP project.

Note: To determine which applications need updated leaf assemblies, open a sequence assembly that contains one of the documents to be updated. Select the document and run the View Where Used query. Select the Show for Sequence Assemblies option to see all instances for which the document was used. Use this information to create associations between the project and sequences. See the topic Global Project Planning for more information.

After using GPP to create planned sequences, the wizard will create a new working assembly under the planned sequence using the structure of the predefined assembly template you select in the wizard. The predefined assembly template should include the documents to be updated and the leaf operations to be performed on the documents. The wizard performs the leaf operations on documents whose names match exactly in both the "list of documents assembly" and the assembly template.

When the wizard applies the template to a sequence assembly, the following rules are applied for adding leafs or updating the leaf operation status based on a comparison of the leafs contained in the target (existing) assembly and the template.

Assembly Templates

An assembly template enables you to set up an assembly structure that you can use to create similar assemblies.

The template can include the elements and metadata that are common to the assemblies you create.

You must have any of the following modules to perform assembly template activities:

— Electronic Lifecycle Publishing (ELP)

— Registered Document Analysis (RDA)

— Submission Planning and Tracking (SPT)

— Paper Review Publishing (PRP)

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.