Documentation Center

New features and enhancements in Contenta S1000D 5.10

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

S1000D Issue 5.0 Support

Several Contenta S1000D tools have been enhanced to improve support for S1000D Issue 5.0.
  • The following enhancements have been made to support the infoNameVariant element introduced in Issue 5.0.
    • Upload Content and Arbortext and Oxygen Check In tools populate or update the Information Name Variant DM property field when uploading or checking in an Issue 5.0 DM that contains an infoNameVariant tag.
    • A new Information Name Variant field has been added to CSV files. The sample CSV file for Issue 5.0, DMRL-sample_S1000D_50.csv, includes Information Name Variant examples.
    • Upload Codes extracts and imports the Information Name Variant (when present) in a CSV or Issue 5.0 DMRL file.
    • The Insert Reference editor plug-in includes infoNameVariant in dmRef markup if the referencing and referenced DMs are Issue 5.0 and the infoNameVariant element exists in the referenced DM.
    • The Clip Reference tool inserts the infoNameVariant (when present) into the code block for a 5.0 Data Module dmRef.
    • Manage Programs inserts the Information Name Variant (when present) into the exported CSV or Issue 5.0 DMRL file.
    • Manage DMRL contains an Information Name Variant column and displays that data when present. In addition, the export link in the Manage DMRL and Manage IRL user interfaces is now labeled EXPORT CSV.
    • LiveContent Preview displays the infoNameVariant as part of the Data Module title in the Task tab (when displaying a 5.0 DM that includes an infoNameVariant).
    • When publishing to LiveContent S1000D, S1000D Publish displays the infoNameVariant (if it exists) with the infoName wherever it appears if the user selects the TechName and InfoName or InfoName Only option for ToC Title Display.
    • Before publishing to XPP, updated XPP style files must be extracted from the delivered s1kdXppCssStyles.zip and copied to your XPP style library. Then, when publishing to XPP, S1000D Publish displays the infoNameVariant (if it exists) as part of the Data Module title in the Publication TOC, LOEDM, and 5.0 Data Modules.
  • The following tools have been enhanced to support longer issue numbers introduced in Issue 5.0.

    • PM Builder allows 3-5 digit issue numbers in the PM Properties form.

    • Upload Codes allows 3-5 digit issue numbers in an Issue 5.0 DMRL's identAndStatusSection and in dmRefs in the content section.

    • Manage Programs allows 3-5 digit issue numbers when validating the Export DMRL form for an Issue 5.0 DMRL, and inserts longer issue numbers into the Issue 5.0 DMRL XML file.

  • The following tools have been enhanced to support the optional Control Authority Group section introduced in Issue 5.0.

    • PM Builder preserves the controlAuthorityGroup section in the identAndStatusSection of Issue 5.0 Publication Modules. PM Builder detects controlAuthorityRefs attributes on pmEntry, dmRef, or pmRef tags in the content section of Issue 5.0 PMs and handles these as unsupported markup.

    • Upload Codes detects the controlAuthorityGroup section in Issue 5.0 DMRLs and stores this XML markup in the CSDB.

    • Manage Programs displays a new Control Authority Group field in the Export DMRL form, pre-populates this field with stored XML markup (when present), and inserts the controlAuthorityGroup section into the Issue 5.0 DMRL XML file.

    • LiveContent Preview suppresses the controlAuthorityGroup section (the same handling as similar sections such as dataRestrictions) when displaying an Issue 5.0 Data Module.

    • DDN Export displays a new Control Authority Group field where a user may enter optional controlAuthorityGroup XML markup. DDN Export inserts this markup (when present) into the Issue 5.0 DDN XML file.

    • When publishing to XPP, S1000D Publish suppresses the controlAuthorityGroup section but resolves controlAuthorityRefs attributes on selected tags, displaying several types of controlled data, marked with a yellow flag note symbol per S1000D specification guidelines and examples. Updated XPP style files must be extracted from the delivered s1kdXppCssStyles.zip and copied to your XPP style library. Selected tags include para, listItem, notePara, warningAndCautionPara, proceduralStep, isolationStep, and isolationProcedureEnd. This work may be extended to additional tags as needed.

  • Contenta S1000D Foundation Suite has been updated to create Issue 5.0 Data Modules.
For more information about these enhancements, refer to the following topics in the Contenta S1000D documentation.

Enhanced CGM support for Oxygen XML Author

Contenta S1000D now provides support for redlining, hotspotting, and enhanced display of CGM graphics in Oxygen XML Author. CGMs exported when a Data Module is checked out for hotspotting or redlining are temporarily converted to SVG format. This temporary conversion has no effect on the source graphic or checkout/checkin.

For more information about these enhancements, refer to Exporting and displaying graphics when you check out a module in the Contenta S1000D documentation.

Enhanced CIR support

Contenta S1000D now supports reuse of the following CIR reference types in Arbortext Editor or Oxygen XML Author for S1000D Issue 4.1 or later.
  • Access Point
  • Caution (previously supported in Arbortext Editor only)
  • Circuit Breaker
  • Control Indicator
  • Enterprise
  • Functional Item
  • NATO Stock Number
  • Part
  • Supply
  • Supply Requirement
  • Tool
  • Warning (previously supported in Arbortext Editor only)
  • Zone

For Issue 4.1 and later, items can be inserted only from a CIR; inserting reusable components from a CSDB reusable component directory is no longer supported for these issues.

To help make locating reusable items stored in CIR DMs easier, the Insert Reusable Component tool allows you to enter a search string (consisting of plain text or an XSLT 3.x regular expression) to filter search results, displaying only CIRs whose content or attributes contain the specified value. You can customize the search criteria by CIR type by modifying the ReusableComponentSearchConfig.xml configuration file in the Contenta_home\web\cw_common\custom\S1000D_config directory on the Contenta Web server.

To customize inserted markup and display of search results by CIR type, contact RWS Professional Services.

For more information about these enhancements, refer to Inserting items from a CIR or a CSDB reusable components repository in the Contenta S1000D documentation.

Contenta S1000D Publish enhancements

Contenta S1000D now supports filtering of available publish configuration files in the S1000D Publish UI. Adding a new, optional PubConfigFiles AppData setting (under the {Global} > Settings > CaS_Publish key) causes only specified publish configuration files to be displayed in the Configurations drop down. If this setting is not present, all available publish configuration files are displayed.

When publishing from Contenta S1000D to LiveContent S1000D, you can now optionally specify custom versions of the LiveContent extra configuration file and front matter XSL file. To enable this enhancement, the following properties have been added to the delivered PublishConfiguration.xml and PublishConfiguration_Unix.xml files.
  • LiveContent_ExtraConfig defines the path of the extra configuration file ([contenta_view_install_dir]/templates/conf/system/s1000d.xml by default).
  • LiveContent_FrontMatter defines the path of the XSL file used to generate IETM front matter ([Contenta_root_dir]/encaps/S1000D/LiveContent_FrontMatter.xsl by default).
In the delivered configuration files, these properties reference the two default LiveContent configuration files; edit their values if you want to use custom files.
For more information about these enhancements, refer to the following topics in the Contenta S1000D documentation.

Updated DDN Export user interface

The DDN Export UI has been updated to include all parts of the identAndStatusSection. Fields in this UI have been reordered to better match the order in the XML and to place required fields before optional fields. User-entered data in the new fields is validated similarly to validation of existing user-supplied data.

New fields include the following.
  • BREX DM Ref: required in Issue 4.1 or higher
  • Derivative Class. Ref ID: optional, available in Issue 4.2 or higher

  • Control Authority Group: optional, available in Issue 5.0 or higher, enter XML markup: <controlAuthorityGroup>...</controlAuthorityGroup>

  • Data Restrictions: optional, available in Issue 2.0 or higher, enter XML markup: <dataRestrictions>...</dataRestrictions> or <datarest>...</datarest>

  • Remarks: optional, available in all S1000D Issues, enter XML markup: <remarks>...</remarks>

Contenta S1000D database upgrade changes

There is no Contenta S1000D database upgrade for Contenta S1000D 5.11. Customers upgrading from Contenta S1000D5.8 or earlier must run the Contenta S1000D 5.9 database upgrade program; see the 5.9 Release Notes for more information.