OpenText Exstream™

Design and Production CE 24.1.0

Release Notes

Product Released: 2024-01-26

 Caution
Cautions help you avoid irreversible problems. Read this information carefully
and follow all instructions.

Important
Important notes help you avoid major problems.

Note
Notes provide additional information.

Tip
Tips suggest quicker or easier ways of performing a task.

2 Design and Production 24.1.0 Release Notes

Contents
1 Introduction ..................................................................................................................................... 4
1.1 Release Notes revision history .................................................................................................. 4

2 About Design and Production 24.1.0 ............................................................................................ 4

2.1 New features .............................................................................................................................. 4
2.2 Discontinued and deprecated features and platforms ............................................................... 4

3 Packaging and documentation ..................................................................................................... 5

3.1 Delivery information ................................................................................................................... 5
Installation packages..................................................................................................... 5
3.2 Related documentation .............................................................................................................. 6
Related videos .............................................................................................................. 6

4 Supported environments and compatibility ................................................................................ 7

4.1 Design and Production support .................................................................................................. 7
Design environment ...................................................................................................... 7
Production environment ................................................................................................ 7
Design and tracking databases ..................................................................................... 7

5 Installation and upgrade notes ..................................................................................................... 9

5.1 Installation notes ........................................................................................................................ 9
5.2 Upgrade notes .......................................................................................................................... 11

6 Fixed issues .................................................................................................................................. 11

6.1 In version 24.1.0 ....................................................................................................................... 11

7 Known issues................................................................................................................................13

8 Contact information .....................................................................................................................16

3
1 Introduction
These Release Notes provide an overview of Design and Production 24.1.0 including new features,
delivery information, supported platforms, and fixed issues.

OpenText recommends that you read these Release Notes in conjunction with the documentation
included with the software package. If any conflicts exist, the Release Notes supersede the other
documentation.

We also recommend that you check My Support for any patches or documentation updates that may
have been posted after the initial release of this product.

1.1 Release Notes revision history

Revision date Sections revised Description of revisions

2024-01-26 First release All new content

2 About Design and Production 24.1.0

This section provides an overview of Design and Production 24.1.0.

Design and Production, a component of the Exstream customer communication management

solution, provides a desktop design environment for creating customer communications that are
produced using the Exstream production engine.

• Designer provides the graphic design interface for creating the design layouts for Design
Manager applications. Designers use this interface to design and format content for pages and
messages, create graphic elements, insert variables to customize documents, and put together
the overall look and feel for customer communications.
• Design Manager lets users create and manage the design objects that make up a Design
Manager application, including design templates, data files, variables, output, output queues, and
the production equipment used by the Exstream engine to produce customer output. Additionally,
system administrators use Design Manager to perform administration tasks, such as managing
users and design groups and defining design components.

2.1 New features

There are no new features introduced in Design and Production 24.1.0.

2.2 Discontinued and deprecated features and platforms

No features or platforms have been discontinued in this release.

The following platform has been deprecated:

• PostgreSQL 12 (as of 24.1)

• IBM AIX (RISC) 7.2 TL4 and earlier (as of 23.4)

• HP-UX Itanium 11i v3 and later (64-bit) (as of 22.4)

4 Design and Production 24.1.0 Release Notes

3 Packaging and documentation
Downloads and documentation for Design and Production are available on My Support.

3.1 Delivery information

Exstream installation packages are in the 24.1.0 Exstream software download area on My Support.

Installation packages
The following table lists the required installation packages for Design and Production. For information
about downloading and installing the containerized Exstream deployment, see the OpenText
Exstream (Cloud-Native) Cloud Deployment Guide for this version of Exstream.

Table 1: Installation packages

Component Installation package Description
Design and Production designer_x64_<version>.zip Traditional installer that
contains the Design and
Production desktop
tools, which provide a
design environment for
creating customer
communications that
are produced using the
Exstream production
engine.
Design and Production • advancedbarchart-<version>.zip Installation packages
add-ins • advancedlinechart-<version>.zip that contain advanced
• advancedpiechart-<version>.zip chart add-ins for
Designer.

Advanced charts are not

supported in
applications that are
fulfilled using the
Orchestration service in
the containerized
Exstream deployment.

5
Component Installation package Description
Exstream engine • engine_<version>_<platform>_db.zip ZIP files that contain the
• engine_<version>_<platform>_sb.zip engines that are used to
preview
communications and
produce customer
output.

Engine ZIP files are

available for the
following platforms:

• 64-bit AIX, HPUX,

Linux, Windows,
and z/OS
• 32-bit Solaris and
z/OS

Containerized Exstream
deployments support
only 64-bit Linux
engines, version 20.2 or
higher.

3.2 Related documentation

Documentation for Design and Production is available on My Support. End user help can be accessed
from Design Manager or Designer, by pressing F1 or clicking Help > Search Documentation.

The documentation for Design and Production includes:

• Installation, Upgrade, and Administration Guide

• Containerized Deployment Licensing Guide
• Design and Import Guide
• DXF Reference Guide
• Logic and Data Guide
• Output, Production, and Delivery Guide
• Switch Reference Guide
• Advanced Bar Chart Add-In Guide
• Advanced Line Chart Add-In Guide
• Advanced Pie Chart Add-In Guide

Note
Using the OpenText Private Help Server to host in-software help is not
supported in this release.

Related videos
For additional video content, see the Exstream videos page on My Support.

6 Design and Production 24.1.0 Release Notes

4 Supported environments and compatibility
This section provides details about supported platforms, systems, and versions.

4.1 Design and Production support

This section provides information about the operating systems and databases that are supported for
Design and Production.

Design environment
The following operating systems can be used with the design environment:

Table 2: Supported operating systems for design

Platform Supported operating systems Required hardware and software
Windows • Microsoft Windows 10 (64-bit) – 22H2 • 64-bit only
• Microsoft Windows 11 (64-bit) – 22H2 • Minimum screen resolution of
1366x768
• Add-ins work best with monitors that
are set to a resolution of 1920 x 1080.
• 4GB RAM (minimum 2GB)
• 10GB free disk space (minimum
800MB)
• You must have enough disk space to
handle all of the production files that
you use in design and test
applications. The actual space
needed depends on the size of the
files used.
• Microsoft Visual C++ 2013 and 2022
Redistributable Package.
• Microsoft .NET Framework version
4.6.1 or later

Production environment
The following operating systems can be used with the production environment:

Table 3: Supported operating systems for production

Platform Supported operating systems
Windows • Microsoft Windows 10 (64-bit)
• Microsoft Windows Server 2016
• Microsoft Windows Server 2019
• Microsoft Windows Server 2022

z/OS • z/OS 2.2 and later

UNIX • IBM AIX (RISC) 7.2 TL0 and later (64-bit
only)
• IBM AIX (RISC) 7.3 TL5 and later (64-bit
only)
Linux • SuSE version 15 (Intel) and later
• Red Hat ES 8 (Intel) and later

Design and tracking databases

The following database platforms can be used with Design and Production:

7
Table 4: Supported databases
Platform Supported operating systems
DB2 • Linux, UNIX, and Windows
o DB2 11.5
• z/OS
o DB2 12
Microsoft Access • Microsoft Access 2019
• Microsoft Access 2021
• Microsoft Access for Office 365
Microsoft SQL Server • Microsoft SQL Server 2014
• Microsoft SQL Server 2016
• Microsoft SQL Server 2017
• Microsoft SQL Server 2019
Oracle • Oracle 19c
PostgreSQL • PostgreSQL 12
• PostgreSQL 13
• PostgreSQL 14
• PostgreSQL 15

Table 5: Database options

On-premise Cloud (Containerized)
• Non-containerized • AWS RDS support for
o PostgreSQL o PostgreSQL
o Oracle
• Containerized o MS SQL Server 2017
o PostgreSQL o Amzon Aurora
o Oracle • GCP Cloud SQL support for
o MS SQL Server o PostgreSQL
o MS SQL Server

Note
If you are considering using Design Manager in a cloud environment,
keep in mind that proximity from the Designer Software to the Designer
Database is vital. Operation of the Design Manager software from a
local installation to a database in the cloud (Oracle RDS, for example),
is likely to result in unacceptable performance.
Currently there is no official support for using Design Manager in a
cloud VM configuration, though we fully expect it to be operationally
acceptable. OpenText is in the process of validating cloud-based
databases for future support, but this is with the caveat that the
software was never intended to be used in this manner, and
performance issues will not be considered an issue that OpenText
would address as a defect. Configuration and use of the thick-client
Design and Production software in a cloud environment is done without
OpenText support.
For more information, please refer to the Knowledgebase article
KB0796533 on My Support.

8 Design and Production 24.1.0 Release Notes

5 Installation and upgrade notes
This section provides additional installation and upgrade information, including related or third-party
product information and any required critical patches.

5.1 Installation notes

For information about installing Design, see the OpenText Exstream (Cloud-Native) CE Cloud
Deployment Guide.

For additional information about installation and upgrade considerations for Design and Production,
see the OpenText Exstream Design and Production CE Installation, Upgrade, and Administration
Guide.

Note
Beginning with the 22.2.0 release, the licensing information for
Exstream has been removed from the Design and Production Online
Help and is now available as a standalone PDF on My Support.

The default paths for the design environment directory locations are provided in the following table:

Table 6: Directory locations

Directory Default path
Default installation C:\Program Files\OpenText\Exstream\Exstream <version>
Public C:\Users\Public\Documents\OpenText
Versioned public C:\Users\Public\Documents\OpenText\Exstream <version>
Personal C:\Users\username\Documents\OpenText
Versioned personal C:\Users\username\Documents\OpenText\Exstream <version>

Some files in the Design and Production desktop design environment might be stored in different
locations depending on which operating system you use. The following table describes where specific
components store different types of files in relation to the base path:

Table 7: Design environnement file locations

Component Directory Stored files
Application Report Default installation The application report uses the installation directory
to specify the full path to the app_en-US.xsl file.
Versioned personal In the command line, any application reports without
a specified location are assumed to be in the
versioned personal directory. When the application
report is generated, the HTML file is stored in the
versioned personal directory.
Custom Spelling Personal Exstream custom dictionaries are stored in the
(Designer) personal directory.
Database and Versioned personal When you run database maintenance or the database
Maintenance Fixes fix routines, the log files are written to the versioned
public directory.
Database Public The Database Administrator utility stores log files in
Administrator Utility the public directory.
Design Manager Default installation Design Manager uses the installation directory to
specify the full path to the engine executable
(engine.exe) when running the engine from the
design environment.

9
Component Directory Stored files
Versioned public When running the engine in the design environment,
Design Manager uses the versioned public directory
to specify the full path to the message resource file if
the MSGRESOURCE engine switch is not specified
in a control file.
Versioned personal The versioned personal directory is the working
directory when the engine is run from Design
Manager. Any output files without a specified location
are stored in the versioned personal directory.
FlexNet Licensing Public When a feature is licensed, the preferred location for
license files is public\Licenses. If public\Licenses
does not exist, the directory is created.
Installation Versioned public During installation, the message resource files are
installed in the versioned public directory. The data
files required for the sample applications are installed
in versioned public\Data files. Exstream and the
engine look for the message resource files in the
versioned public directory. If you want to specify
another directory for the engine, you must use the
MSGRESOURCE engine switch.
Packaging Default installation The packaging process uses the installation directory
to specify the full path to the IBM executables
(installation directory\Color AFP) when it
creates the processes needed to produce AFP
output.
Packaging Versioned public When the packaging process creates the processes
needed to produce AFP output, it expects the AFP
color processing configuration files in the versioned
public directory (versioned public\Color AFP).
When processing images, the packaging process
changes the working directory to the versioned public
directory.

When processing images during packaging, the

working directory is changed to the versioned public
directory (versioned public\Color AFP).
Versioned personal In the command line, any log file, package file,
packaging control file, or engine control file is
assumed to be in the versioned personal directory.
When using the interface, if the location of the
package file name is not specified, the package file is
created in the versioned personal directory. When
building a print resource file, any output files or report
files without a specified location are created in the
versioned personal directory.

When packaging fonts (build print resource files), if

the location of the output or report file name is not
specified, then the output or report file name is
created in the versioned personal directory.
Unload/Load XOB Versioned personal If the location of a log file or an XOB file is not
specified, then it is assumed to be in the versioned
personal directory.

10 Design and Production 24.1.0 Release Notes

5.2 Upgrade notes
To access the most current features available with Exstream, OpenText recommends that you use an
Exstream (Cloud-Native) deployment. However, there are some situations that might require you to
upgrade only Design and Production using an Exstream (Server-Based) deployment.

When deciding which product release version to use for a Design and Production upgrade, keep the
following considerations in mind:

• If you are upgrading a classic—or standalone—version of Exstream Design and Production in

conjunction with any of the following products and you wish to continue using those products,
then you must upgrade to an Exstream (Server-Based) version of Design and Production:
o Communications Server (including Tier Transactional)
o Exstream Application Manager
o Live
• If you upgrade your existing classic (standalone) version of Exstream Design and Production to
the version within an Exstream (Cloud-Native) release, then you should use only Cloud-Native
version releases for upgrading from that point. In other words, OpenText recommends that you
not switch back and forth between the Server-Based and Cloud-Native release types, because
using different types of product installers will cause database serialization issues, resulting in an
incompatible database. Instead, you should wait for the next version release for the specific
release type that you have chosen.

6 Fixed issues
This section provides information about past issues that have been fixed in this release.

6.1 In version 24.1.0

Issue number Description

DNP-80877 AFP FIle size is too large with png image
DNP-80856 Boolean Variables
DNP-80868 Conflict between French GUI of Design Manager and DBCS package in the DAS
- packages are not correctly flagged as DBCS in DAS (impossible to associate a
DBCS engine)
DNP-80583 apache/xerces-c 3.2.3 CVE-2023-37536
DNP-78510 Harfbuzz cannot be built on z/OS
DNP-80871 £ currency symbol missing from Advanced Bar Chart output
DNP-80905 'Unable to run a Job - The engine run was terminated for the following reason:
SIGABRT'
DNP-80895 Batch Jobs are failing due to The engine run was terminated for the following
reason: SIGTRAP error.
DNP-80855 Missing pages when using application consolidator
DNP-80851 Template design distorts reading order
DNP-80543 PDF text is not displayed when accessibility is turned on and Type1 fonts are in
use.
DNP-80483 Contents of ADA tags in PDF output are no longer appearing
DNP-80858 Engine crashing, when importing pdf

11
 Issue number Description
DNP-80859 Error "EX009000E (1) INTERNAL ERROR: (ID = Invalid AFP Image size)" when
using "Use outline font metrics" option
DNP-80835 Readability dialog graphics incorrectly read by screen reader
DNP-80585 Images in table type dialog incorrectly read by screen reader
DNP-80867 Copyright date not up to in the Czech Language legal notice
DNP-80817 Unable to print the PDF generated using Acroform
DNP-80693 Issues with sub-packages engine run
DNP-80586 Table type dialog radio buttons provide no context to a screen reader

DNP-80588 Focus order in table type dialog is incorrect

DNP-80802 Changing object to "split and flow" causes object to disappear
DNP-80501 Editable pdf import should not allow user to edit output file

DNP-80675 Engine crash while processing large input files

DNP-80587 Unable to close Add-in dialog without use of mouse pointer
DNP-80180 Variable values not set correctly on Banner Pages during Post Processing
DNP-80782 Engine crashing when passing through RTF text
DNP-80686 Images are missing in the PDF output from Post-sort processing using new build
DNP-80759 OT job is failing with SIGSEGV error
DNP-76524 AFP missing landscape PDF placeholder pages with 'used resources only'
DNP-80699 Recent Build has Introduced an Unexpected Change in HTML Output
DNP-80719 Engine code error 139
DNP-80189 Table with radio buttons not coming out in XML output
DNP-80703 Additional tag in output when using DOC_LEVELTAG
DNP-80683 TIFF placeholder images are not being output correctly
DNP-80595 Array not printed in the correct order
DNP-80593 Engine crashes while running on Windows
DNP-80560 Engine creates HTML output with lines exceeding length of 998 characters
(excluding CR/LF) : it does not meet standard RFC 5322
DNP-80679 Label Chart Issues
DNP-80520 PS fails to distill
DNP-80561 Engine crash
DNP-80197 OpenSSL 1.1.1u BDSA-2023-1866
DNP-78749 Xpdf 4.04 CVE-2022-36561
DNP-80638 Addendum to DNP-80591 (Missing tag content with French driver file)
DNP-80591 Text not tagged with Exstream Engine 16.6.70 Build: 205125 and switch
DOC_LEVEL_TAGGING
DNP-80531 ADA Read Order is incorrect on flow page of PDF
DNP-80505 'Production Job Failing for reason "The engine run was terminated by a SIGKILL
signal”
DNP-80467 Version 23.2.0 composes some tables differently after upgrade from version
21.2.0 - software defect.
DNP-80538 Editable pdf feature error
DNP-80544 Accessibility read order issue with -DOC_LEVEL_TAGGING switch.

12 Design and Production 24.1.0 Release Notes

 Issue number Description
DNP-80576 Flow area read order not respected in pdf
DNP-80562 Engine crash when importing pdfs at runtime
DNP-78849 Serpentine table with conditionally colored rows not working
DNP-80457 Accessibility tags incorrect in PDF Passthru Output

7 Known issues
Table 8: Known issues in version 24.1.0
Related feature Summary
Accessibility When you use the environment keyboard shortcut (press the 'e' key) to
navigate to the Environment heading, you cannot use the RIGHT arrow
key to expand it.
To expand the Environment heading without using the mouse, you can
either press the UP and DOWN arrow keys to navigate to the
Environment heading and expand it by pressing the RIGHT arrow key, or
you can press ALT + V and, from the View menu, select Library View >
Environment View.
Adjusted table cells Adjusted table cells that are designed in container views will appear at the
width of the column in which they are placed when rendered in Empower
or HTML outputs.
Advanced charts When you use a DBCS Linux engine to produce AFP, HTML, PDF, PDF/A,
or PostScript output from an application that contains advanced charts,
and if you receive an engine message related to advanced charts, font
names in the engine message are not displayed correctly. Font names in
your output are not affected and the output appears as expected.
Bleeds If you design content that is allowed to bleed, keep in mind that Exstream
does not support text bleeds. If a design object that contains text (such as
a table or text box) overlaps the edge of the design area, then the text is
cropped at the design area margin. However, any fill, color, or embedded
object (such as an image or shape) that is also applied to the same design
object is allowed to bleed.
Complex text Because you cannot change the encoding for rule analysis reports, any
languages non-ASCII characters in variable names or values do not appear correctly
in the report.
Complex text Record indicators that contain Cambodian (Khmer) text do not appear as
languages expected in the Edit Panel in Design Manager or in output produced by the
engine. Section names that contain Cambodian (Khmer) text appear as
expected.
Complex text You cannot use Cambodian (Khmer) text in XML element names.
languages
Complex text When viewing Thai HTML output in Internet Explorer, the Baht symbol (฿)
languages will sometimes appear separately from its associated numbers. For
example, sometimes the Baht symbol will be the last character on a line
and the associated numbers will be the first characters on the next line.
Complex text In accessible PDF output that contains complex language text such as
languages Cambodian (Khmer) and Farsi, the engine applies all accessibility features
as expected, and assistive technology tools that support complex text
languages can read the document correctly. However, some complex
language text characters might not appear as expected in the Adobe
Acrobat Tags panel.

13
 Related feature Summary
Complex text When using non-European numbers to populate the values for integer,
languages float, date, and currency variables, you receive invalid variable errors when
you test data maps or run the engine. To avoid this issue, do not use non-
European numbers to populate the values for integer, float, date, and
currency variables.
Complex text When you map data that contains Cambodian (Khmer) text, the
languages Cambodian (Khmer) characters do not appear as expected. This is strictly
a cosmetic issue and does not affect your data.
Complex text When you paste complex text characters onto a page in Designer, the
languages characters disappear after you press the space bar on your keyboard. This
problem occurs when you attempt to paste characters into an object in
Designer that does not have the necessary font specified. For example,
you would see this issue if you attempted to paste Cambodian (Khmer)
text into a text box for which you have the Times New Roman font
currently selected. To avoid this problem, make sure that you select the
appropriate font for an object in Designer before you paste complex text
characters.
Complex text For right-to-left languages, if your design uses a date array or integer array
languages variable, and you set the value of the array element to All, print as list or
All, blanks (in Designer, in the variable properties, on the Variable Use
tab, in the Array element to use drop-down list), then the engine
produces output in which the elements of the array are in left- to-right
order.
Complex text On an Arabic language layer, if you change a single-column text box to a
languages multi-column text box and then undo that change, some text in the box will
suddenly move to the beginning of the text box.
Complex text If you are working on an right-to-left language layer, using tab stops with
languages English text on that layer can cause the English words to break incorrectly.
Complex text You cannot use Cambodian (Khmer) text to name a variable or function in
languages Design Manager.
Dynamically Exstream supports dynamic content import for standard designs only. If
importing DXF files you dynamically import a DXF file that contains a standard design and
container designs at run time, only the standard design is imported into the
final output and any container designs are ignored.
Flowing document If you place a DOCX or DXF placeholder variable directly on a page, and
placeholders you use the -ALLOW_PLACEHOLDER_ CONTENT_TO_FLOW=YES
engine switch in the control file, then the resulting output will contain only
the variable design sample text (as it appears in Designer), instead of the
imported DOCX file.
The message file will contain the following message:
Message: Invalid use of a DXF placeholder variable <VariableName>. You
cannot import a DXF application using a placeholder variable.
Grid layout The draw order for objects within a grid layout container is determined first
containers and draw by the object’s z-order, and then by the order of the cell in which the object
order is placed. Because draw order within a grid layout container is different
from the remainder of the design, if you include an absolute position
container in a grid layout container cell, the objects within the absolute
position container cannot overlap the grid layout container.
If you want an object to overlap the grid layout container, the absolute
position container must not be a child of the grid layout container.
HPUX 64-bit engine In order to correctly parse XML input, the 64-bit HPUX engine must use a
valid UTF-8 locale (for example, EN_ US.UTF-8).

14 Design and Production 24.1.0 Release Notes

Related feature Summary
HTML5 Producing HTML5 output that contains multiple customers in the same file
causes design objects that are shared to have the same element IDs for
every customer in the file. While these files will still open in a browser,
when you run validation against an HTML output file that contains multiple
customers in the same file, the validation will fail.
However, you can split the customers before validation to avoid this
behavior.
HTML-based When you produce responsive output from a container design that includes
responsive output an embedded image that is set to fit the parent object, the image
sometimes does not honor the proportions of the parent object in
responsively resized output.
If you use the Fit image to object setting for an embedded image, you
should use an image that has the same aspect ratio as the parent object.
Licensing • In non-English versions of the Welcome to Design and Production
guide, the Web Services Interface module is incorrectly listed as a
requirement for Empower documents. Instead, you must have the
Engine as a Web Service (EWS) module.
ODBC access on AIX • On the 32-bit and 64-bit SBCS and DBCS AIX engines, updating or
inserting on a driver file using the unixODBC driver is not supported at
this time.
• On the 32-bit and 64-bit DBCS AIX engines, updating or inserting on
a driver file using the DataDirect driver is not supported at this time.
ODBC access on On the 64-bit DBCS HPUX Itanium engine, ODBC access using the
HPUX Itanium DataDirect driver is not supported at this time.
ODBC access on On the 32-bit and 64-bit DBCS Linux engines, ODBC access using the
Linux DataDirect and unixODBC drivers is not supported at this time.
ODBC access on On the 32-bit DBCS SUN engine, updating or inserting on a driver file
SUN using the DataDirect driver is not supported at this time.
ODBC access on When running the engine on z/OS using the IBM DB2 CLI driver for ODBC
z/OS access, keep the following in mind:
• The DBCS engine on z/OS does not currently support ODBC access
to DB2 z/OS databases.
• The SBCS engine on z/OS cannot perform update, insert, or write
actions from ODBC data files on DB2 z/OS databases.
Packaging to DAS When you try to package and upload to DAS an application that contains a
web service data file, the packaging process fails because web service
data files are not supported in containerized deployments of Exstream.
To avoid this issue, update the data file to use File as the File source
type.
Paragraphs If your design uses empty paragraphs—that is, paragraphs that do not
contain text, such as those used to create white space, or those that
contain only embedded objects, tables, or images—when you create
HTML output, the engine removes the paragraph breaks associated with
the empty paragraphs. In the resulting output, the engine converts the
paragraph breaks to line breaks that inherit the properties (including
spacing, alignment, and so on) of the nearest non-empty paragraph that
precedes them. Keep in mind that, if your design contains several
consecutive empty paragraphs, the nearest non-empty paragraph might
actually be several paragraphs earlier.
As a workaround, you can add a non-breaking space to any empty
paragraphs so that the engine will honor any settings that you apply to
those paragraphs.
PDF Accessibility • When you use the PAGELABELVAR engine switch and the
'SYS_PageInDocument' variable, the percent sign does not appear in
the navigation feature in Adobe Acrobat Reader.
• If the PAGELABELVAR switch returns a negative value, the value
does not appear as expected in the navigation feature in Adobe
Acrobat Reader.

15
 Related feature Summary
Preview in external • In Designer, when you launch the preview in external viewer feature,
viewer a design page that is controlled by jurisdictions is always excluded
from the preview output, and in some instances, that design page is
incorrectly reported as not being a part of the application.
• In Designer, when you launch the preview in external viewer feature
multiple times, the Viewers list and the Preview button are inactive in
the Preview dialog box. To enable these controls, you must select a
package profile from the Package Profile drop-down list, even if a
package profile is already selected.
• In Design Manager, you can use the new Archived file package
directory setting (accessed from the Tools > Options menu), to
specify the global path to the directory that stores archived package
files. This path is used for all of the design databases that are used by
the current Windows user on a workstation.
When the user drops a design database, files that are in the archived
package directory are automatically deleted for the current Windows user
on the workstation. If another user has created a personal archived
package directory, files in the personal directory must be manually deleted
using the UUID of the database.
For databases that are managed by EAM, the location of the archived
package directory is specified in the settings that are stored on the EAM
server for the EAM Design Service user. If the EAM Design Service is
logged in as the default user (the Network Service user), it is likely that no
archived package directory has been specified. In this case, if the EAM
Design Service drops a database, archived package files are not deleted
automatically, and must be deleted manually.
If, however, another user is specified for the EAM Design Service login,
and the user has specified the path to the archived package directory,
there is a different outcome. In this case, if the EAM Design Service drops
a database, the files in the user-defined archived package directory are
automatically deleted, and the user does not receive a prompt asking
whether to keep the files.
XML In both HPUX and Linux environments, when you produce XML
(composed) output (composed) output, certain characters—such as full-width dashes and
numbers—do not appear correctly in the resulting output.
XML (multi-channel) Design and Production does not support external resources in Multi-
output Channel XML output on z/OS.

XML (multi-channel) The Run XSLT engine option on Multi-Channel XML output and XML data
output XML data files files is currently not supported by the Windows 64-bit engine due to a
limitation with the internal XALAN XSLT engine. When running the 64-bit
Exstream Windows production engine, you must use a third-party XSLT
engine that supports the Windows 64-bit operating system in order to
transform your Multi-Channel XML output or XML data files.

8 Contact information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1

For more information, visit the OpenText or My Support websites.

16 Design and Production 24.1.0 Release Notes

© 2024 Open Text

Patents may cover this product, see https://www.opentext.com/patents.

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept
no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication.

17