Documentation Center

New features and enhancements in Contenta S1000D 5.5

This section lists features and enhancements that were introduced in Contenta S1000D 5.5.

Publish S1000D content to a third-party output format

In addition to publishing S1000D content to LiveContent S1000D or XPP, you can now publish S1000D content to a third-party output format (IETP viewer or PDF publishing engine), or to the file system.

Complementing the existing outputs in the Format section of the Contenta S1000D Publish UI (PDF 8.5x11, PDF A4, and LiveContent) is the new Contenta to File System output format, which lets you to publish S1000D modules and graphics from the Contenta CSDB to the file system, pre-process them (resolve references, apply applicability, and so on), optionally call a Perl script to perform additional actions, and optionally zip up the publish export directory.

You may add additional output formats similar to the Contenta to File System output format to publish to a third-party IETP viewer or third-party PDF publish engine by copying the delivered S1000D_PublishFromFileSystem.pl sample Perl script and saving it as to a new name, adding custom actions to it, or executing a program in a different language such as Java.

See Chapter 9 "Publishing S1000D Content" in the SDL Contenta S1000D User Guide for detailed instructions.

Publish Incremental Changes to IETPs

You can now update an existing IETP by publishing a change package containing only those objects that have changed. To support this functionality, a new PubManager object type has been added to the Contenta CSDB along with sample PubManager templates for Issues 3.0, 4.0, and 4.1. You create a PubManager object for each change package to list its contents and required metadata; this information is stored in XML conforming to a new pubManager schema delivered with Contenta S1000D. The S1000D Publish tool has been enhanced to allow you to select a change package to be applied to the PM and whether you want to optimize publish for size or speed. See the Publishing chapter in the Contenta S1000D User Guide for detailed information.

Exclude source XML from an IETP

When publishing from Contenta S1000D to LiveContent S1000D, you can now exclude the source XML from an IETP. To enable this functionality, a new LiveContent S1000D configuration property, LiveContent_IncludeSourceXmlInIetmDeliverable has been added to the Contenta S1000D publish configuration file. Set the value of this property to false to publish an IETP without its source XML. This property must be set to the same value (true or false) when performing a full publish as it is when performing an incremental update; that is you can exclude the XML source for an incremental update only if the full IETP has been published without it. The default value for this setting is true.

S1000D Publish change to Publications list

If the user selects a PM before running publish, the Publications list contains only the selected PM. To see a list of all PMs in the CSDB, select a Configuration before running publish.

S1000D Publish Export Directory naming enhancement

The S1000D Publish export directory name now includes the Publication Module issue number and issue date. The following lists examples of both old and new names.
  • Old name:

    PMC-SAMPLEBIKE-XYENT-00041-02.20160630111213-12345

  • New name:

    PMC-SAMPLEBIKE-XYENT-00041-02-001-20010130.20160630111213-12345

    where 001 is the issue number, and 20010130 is the year, month, and day in the issue date.

Using S1000D Upload to import Word, Excel, and PowerPoint files into the CSDB

You can now use the S1000D Upload tool (instead of the Dynamic Import tool) to import Word, Excel, and PowerPoint files into your Contenta S1000D databases (CSDBs). This lets you store auxiliary or supporting information such as costing spreadsheets, lists of tasks to be completed, and business rules.

Both older and current file types are supported:
ApplicationCurrent file typeLegacy file type
Word.docx.doc
Excel.xlsx.xls
PowerPoint.pptx.ppt

The MIME Type property field is set based on the file extension of the file being uploaded. See the "AppData settings for SDL Contenta S1000D tools" topic in the SDL Contenta S1000D User Guide if you want to view the MIME types that have been set for each type of file.

Contenta clients include the following support for imported Word, Excel, and PowerPoint objects:
SDL Contenta WebSDL Contenta Explorer
Content Check InCheck Out
Content Check OutCheck In
Content FetchEdit <editor>
Content ViewEdit With <editor>
View <editor>
View With <editor>

Once imported, Word, Excel, and PowerPoint objects will reside in the appropriate sub-containers of the Other Docs container of the Configuration.

DDN Export Support for Referenced Objects

DDN Export has always let you create a DDN package that includes the DMs, PMs, SCPMs, and graphics that you dragged into a Dispatcher object, as well as a DDN XML file generated by DDN Export. You now have the option of additionally including objects that are referenced by the objects that you dragged into the Dispatcher object. You may include referenced modules or graphics or both, locked or not, searched for recursively or not. DDN Export also creates a new referenced object log file that reports each object that was exported as well as any objects that are missing or inaccessible (such as objects in a configuration that is not on your desktop).

This enhanced capability lets you easily:
  • Reuse DMs into your Dispatcher, and also include the graphics referenced by those DMs.
  • Reuse a PM into your Dispatcher, and export the entire publication by including referenced, nested PMs, DMs, and graphics recursively.

See Chapter 6, "Working with DDNs" in the SDL Contenta S1000D User Guide for more information.

Changes to Contenta S1000D Upload Functionality

Contenta S1000D now uses HTML5 to support upload functionality and no longer relies on an applet. DDNs can no longer be uploaded directly; instead, you must manually upload the objects in a DDN. To do so, navigate to the folder on your file system containing the DDN whose contents you want to upload, and drag the files (excluding the DDN XML file) onto the box in the Upload UI.

Previously, DDN upload functionality included an option, Unlock objects associated with this DDN, which allowed you to unlock any locked objects associated with the DDN being uploaded. Because direct upload of a DDN is no longer supported, you must now manually unlock any such objects in Contenta Web or Contenta Explorer.

For further information about uploading the contents of a DDN, refer to the SDL Contenta S1000D User Guide.

Contenta and Contenta S1000D Java API and Web Services API

Contenta Web now uses the Contenta Java API instead of COM or CORBA API. Contenta CORBA API is desupported and Contenta COM API is deprecated as of this release.

For further information about the Contenta and Contenta S1000D Java and WS APIs, refer to the SDL Contenta 5.5 Release Notes and the following API reference documents:
  • SDL Contenta and Contenta S1000D Web Services API Programmer Guide
  • SDL Contenta and Contenta S1000D Perl Java API Wrapper Programmer Guide

Contenta S1000D Database Upgrade Changes

This section lists the changes made to your existing Contenta S1000D databases when you upgrade them to Contenta S1000D 5.5.
  • A new object type, PubManager, has been added:
    • Object type name: PubManager
    • Object type template: PModule
    • Icon name: PModule
    • Can be created by: Container, Project, ContentRoutingProject, Model, Issuer, PMNumber
  • The default value for the Document Type property on PubManager objects is pubManager. The following new PubManager properties have been added:
    • Change Package Name
    • Change Package Issue Number
    • Change Package Start Date
    • Full Revision Issue Number
  • A new document type, pubManager, has been added in AppData along with the keys and values required for editing in Arbortext Editor using the PM versions of Contenta S1000D adapters.
  • A new top-level container object, Publication Management, has been added to the S1000D configuration. This container follows a hierarchy structure parallel to that of the existing Publication Modules container (Model > Issuer > PMNumber), except that the PMNumbers in this new hierarchy contain PubManager objects (instead of PMs).
  • The following PubManager object templates are delivered in the Publication Management container:
    • PubMan-SAMPLEBIKE-XYENT-00030-01_002
    • PubMan-SAMPLEBIKE-XYENT-00040-01_002
    • PubMan-SAMPLEBIKE-XYENT-00041-01_002
  • Container, Project, and ContentRoutingProject objects can now create Excel, PowerPoint, and Word objects.
  • Dynamic Import client and web tools have been removed from the Excel, PowerPoint, Word, and ZIP objects.
  • The following MIME types have been added to AppData:
    Key: {Global} > mimetypeMappings:
    • Name: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Value: .docx
    • Name: application/vnd.openxmlformats-officedocument.presentationml.presentation, Value: .pptx
    • Name: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, Value: .xlsx
  • The value for the Contenta S1000D database schema version AppData setting has been changed to CaS_5.5:
    Key: {Global} > DB Schema:
    • Name: ContentaS1000D
    • Value: CaS_5.5
Upgrade customers must first run the Contenta upgrade_55 database program, then run the Contenta S1000D upgrade_S1000D_55.pl database program to upgrade their Contenta S1000D databases. New customers must dbimport the appropriate s1000d.dmp file, which is located at:
  • Contenta_home/S1000D_samples/databases/Contenta55_MSSQLServer_database
  • Contenta_home/S1000D_samples/databases/Contenta55_Oracle11g_database
  • Contenta_home/S1000D_samples/databases/Contenta55_Oracle12c_database