emc documentsciences xpression...emc®documentsciences® xpression® version4.6sp1 upgradeguide...

EMC® Document Sciences®

xPression®

Version 4.6 SP1

Upgrade Guide

EMC CorporationCorporate Headquarters

Hopkinton, MA 01748-91031-508-435-1000www.EMC.com

Legal Notice

Copyright © 2006 — 2016 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATIONMAKES NO REPRESENTATIONSOR WARRANTIES OF ANY KINDWITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLYDISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. Adobe and Adobe PDFLibrary are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. All other trademarksused herein are the property of their respective owners.

Documentation Feedback

Your opinion matters. We want to hear from you regarding our product documentation. If you have feedbackabout how we can make our documentation better or easier to use, please send us your feedback directly [email protected]

Table of Contents

Preface ................................................................................................................................ 9

Chapter 1 Before You Begin ........................................................................................ 11Moving xPresso Documents to the Server........................................................... 11Back Up Database and Server Files .................................................................... 12Remove Font and Cache Agent Services ............................................................. 12Exporting xPression 2.5 Output Profiles ............................................................. 13

Chapter 2 Step One: Upgrade xPression Database ..................................................... 15Upgrading From 4.1 SP1 and Higher Versions .................................................... 15Upgrading From a Version Lower than 4.1 SP1 ................................................... 16Upgrading From xPression 2.x ...................................................................... 16Upgrading From Pre–3.0 SP1 Versions for DB2 Users ...................................... 16

Upgrading xPressForms Database ..................................................................... 17Determining the Database In-Use .................................................................. 17Moving the Database .................................................................................... 17Moving the Database for SQL Server.......................................................... 18Run the DTSWizard.............................................................................. 18Run the Primary Key Scripts ................................................................. 18Reset Identity ....................................................................................... 19

Moving the Database for DB2 .................................................................... 20Export Data.......................................................................................... 20Create Tables........................................................................................ 21Import Data ......................................................................................... 21Reset Identity ....................................................................................... 21

Moving the Database for Oracle................................................................. 22

Chapter 3 Step Two: Uninstall the xPression Server ................................................... 23

Chapter 4 Step Three: Install xPression Server ........................................................... 25Install the xPression Server................................................................................ 25Before Upgrading the Server ......................................................................... 25

Compare Directories ......................................................................................... 26Delay the xRevise Upgrade ............................................................................... 26

Chapter 5 Step Five: Post-Installation Tasks ............................................................... 27Enabling Additional Batchrunner Parameters ..................................................... 27Updating Your Documentum Configuration....................................................... 28Upgrading a JBoss Environment ........................................................................ 28Upgrading xRevise ........................................................................................... 29Removing Old Classpath Settings on WebSphere................................................ 29

Chapter 6 Upgrading xPression Client Applications .................................................... 31

3

Table of Contents

Upgrading xDesign .......................................................................................... 31Upgrading xDesign ...................................................................................... 31Upgrading Word Templates for xDesign ........................................................ 32InstallShield Error When Upgrading xDesign ................................................. 32

Upgrading xPresso for Word ............................................................................. 32Upgrading xPresso for Adobe InDesign ............................................................. 33Displaying Turkish Characters ...................................................................... 33

Upgrading xPresso for Dreamweaver ................................................................ 33Disabling the xPresso for Dreamweaver Extension.......................................... 33Uninstalling xPresso for Dreamweaver .......................................................... 34

About Upgrading xEditor ................................................................................. 34

Chapter 7 Changes for Upgrade Users ........................................................................ 374.6 SP1 Changes ............................................................................................... 37xPression Documentum Edition (DE) and xPression EnterpriseEdition (EE).................................................................................................. 37SSH and TLS Certificates Support .................................................................. 39Changes to Document Naming Conventions .................................................. 39Output of the Documents with Hidden End Mark Property ............................ 39Keep with Next ............................................................................................ 40Changes in Default “Normal” Style ............................................................... 40Number Rounding in JDK............................................................................. 40

4.6 Changes...................................................................................................... 41Table Row Height in xPresso for Word Documents ......................................... 41Pie Chart in Content Loop............................................................................. 41Outputting Spot CMYK Colors ...................................................................... 41Table Width in xDesign Online Editor ............................................................ 41Hyperlink Styles in xEditor ........................................................................... 42

4.5 SP1 Changes ............................................................................................... 42Unmapped Array Items ................................................................................ 42List Indent ................................................................................................... 42Keep with Next ............................................................................................ 42ECM System Password ................................................................................. 43Location of xPresso Schema files.................................................................... 43Category Names Ended with Spaces .............................................................. 43VBA Access Error ......................................................................................... 43Allowing Backwards Compatibility for Metadata Naming Convention ............ 43Resample Images to Output Resolution.......................................................... 44

4.5 Changes...................................................................................................... 44Text Frames.................................................................................................. 45LDAP Issues ................................................................................................ 45PPD Files for AFP Emitter ............................................................................. 45New PDF Emitter ......................................................................................... 46PCL Emitter ................................................................................................. 46User Exits..................................................................................................... 46About AutoInc Fields.................................................................................... 46Different Results of Numeric Calculations for xPresso FunctionVariables ...................................................................................................... 46Single Cell Tables.......................................................................................... 47Table Rows with Exact Height ....................................................................... 47Paragraph Alignment in Tables...................................................................... 47Underline..................................................................................................... 48Empty Paragraphs at the End of Content Items............................................... 48Inserted Images ............................................................................................ 48Hidden Paragraph Marks.............................................................................. 48Subdocument Page Breaks ............................................................................ 48

4

Table of Contents

Table Continuation Text Improvement ........................................................... 48Handling of Variables ................................................................................... 49Character Spacing......................................................................................... 49Font Weight ................................................................................................. 49TIFF Color.................................................................................................... 49Paragraphs With Borders .............................................................................. 49Line Styles ................................................................................................... 49Datamail Documents (4.5) ............................................................................. 50Image Fit Options (4.5).................................................................................. 50Line Spacing Improvements (4.5)................................................................... 50Schematic Log (4.5) ....................................................................................... 50

4.2 Changes...................................................................................................... 50Syntax Error When Using a 3.0 SP1 Output Profile.......................................... 50Using “Space Before” with Multiple Column.................................................. 51Numbered Paragraphs Beginning with White Spaces...................................... 51Font Size of an Empty Paragraph (4.2)............................................................ 51

4.1 SP1 Changes ............................................................................................... 51UTF-8 Non-Compliant XML Causes Error (4.1 SP1) ........................................ 52Migrating Content From Pre–4.1 SP1 Versions ................................................ 52Documents Causing Application Failure ........................................................ 52Line Break Differences in Documents Using Kerning (4.1 SP1)......................... 53Spacing Above Tables (4.1 SP1)...................................................................... 53Length of Underline in Tables is Shorter......................................................... 53Some Variables are Not Replaced................................................................... 53Text Wrapping and Alignment Improvements ................................................ 53New Feature: Remove Empty Paragraphs ...................................................... 54Odd/Even Page Header and Footer Improvements ......................................... 54New Feature: Character Spacing.................................................................... 54Vertical Alignment Improvements ................................................................. 54Table Row Alignment ................................................................................... 54Empty Table Rows ........................................................................................ 55Empty Table Row Spacing............................................................................. 55Y-Position Discrepancy When Using Line Height Exactly................................ 55Justified Text with Leading Spaces ................................................................. 55Empty Table Cells......................................................................................... 55Different Y Position Due to Empty Table Cells ................................................ 56Different Y Position Due to Empty Table Rows ............................................... 56Empty Table Rows with Spanning ................................................................. 56Leading White Space in Numbered Paragraphs .............................................. 56Cell Margins Exceed Cell Width .................................................................... 56

4.1 Changes...................................................................................................... 56Barcode Resolution (4.1)................................................................................ 58Corda Charts (4.1) ........................................................................................ 58Cell Width and Line Breaks (4.1).................................................................... 58Space Before (4.1) ......................................................................................... 58Line Spacing Discrepancy (4.1) ...................................................................... 59CS3 Users Upgrading from 3.0 SP1 ................................................................ 59Lowercase Letters in Variable Names ............................................................. 59Uninitialized Variables.................................................................................. 59Page Numbering after Page Breaking Section Break ........................................ 60Out of Bounds Text in Table Cells .................................................................. 60Corda Charts................................................................................................ 60Table Borders and Adjacent Tables................................................................. 61Non-Breaking Spaces .................................................................................... 61Non-Breaking Hyphens ................................................................................ 61Y-Position Variance....................................................................................... 61Non-Breaking Spaces and Hyphens in Combination ....................................... 62Paragraph Spacing........................................................................................ 62

5

Table of Contents

Exact Row Height......................................................................................... 62Justification and Space Characters ................................................................. 62Table Cell Alignment in Web Service Output .................................................. 62Output Style in Web Service Output .............................................................. 63Current Date in Barcodes .............................................................................. 63Placeholder Table Cells ................................................................................. 63Paragraph Appears Higher on Page ............................................................... 63Tables with Blank Lines................................................................................. 63Overall Table Height..................................................................................... 64“Different First Page” Footers........................................................................ 64Undefined Variables ..................................................................................... 64Spaces in Optional Content ........................................................................... 64Improvement in Y-position ........................................................................... 64Non-Breaking Spaces .................................................................................... 65OMR Barcode Output ................................................................................... 65Page Numbering Logic ................................................................................. 65

6

Table of Contents

List of Tables

Table 1. xPression Home Files and Folders Not Applicable in xPression DE.......................... 38

7

Table of Contents

8

Preface

This guide provides steps for upgrading the xPression database, the xPression Server, xDesign, andxPresso client applications.

Intended AudienceThe guide is for document designers and system administrators who will upgrade xPression clientapplications and xPression Server.

ConventionsThe following conventions are used in this document:

Font Type Meaning

boldface Graphical user interface elements associated with an action

italic Book titles, emphasis, or placeholder variables for which you supply particularvalues

monospace Commands within a paragraph, URLs, code in examples, text that appears on thescreen, or text that you enter

xPressionHome

The term “xPressionHome” refers to the location where xPression is installed on your server. OnWindows servers, the default location is C:\xPression

Revision HistoryThe following changes have been made to this document.

9

Preface

Revision Date Description

November 2016 Initial publication

10

Chapter 1Before You Begin

The term upgrade refers to the process of moving from one version of the software to another version.Typically this process includes removing and replacing xPression components. This process may alsorequire customized steps if you are starting from certain versions. Some additional configurationsteps may be necessary to ensure document fidelity. Review for a list of issues that may affect yourdocuments.

Before you begin, review the following sections:• Moving xPresso Documents to the Server, page 11

• Back Up Database and Server Files, page 12

• Remove Font and Cache Agent Services, page 12

Moving xPresso Documents to the ServerxPresso documents use numeric versioning. Documents created in xPresso prior to xPression 4.5do not contain a version number; therefore, you must make sure that you use proper upgradeprocedures to move your documents to the upgraded server.

To move your xPression 4.2 to the current version of xPression Server, use one of the followingprocedures:• For xPresso for Adobe InDesign and xPresso for Dreamweaver documents, you can open pre-4.5documents from your current client applications. Once they are open, you can check them intothe server where they will be given a version number. Pre-4.5 xPresso for Word documentscannot be opened in the current version.

• For xPresso for Word documents, you can export your pre-4.5 documents in a PDPX file, thenimport it into your new environment through xAdmin. When the document is imported into theserver, you must ensure that a document with the same name does not already exist. Pre-version4.5 documents can be published on the server. If you need to change the document again, thereare two options, if you want to use new xPresso for Word format, you can check it out fromxPresso for Word client (4.5SP1 and later), the document will be upgraded automatically. Youcan check it into the server where they will be given a version number. If you want to keep thexPresso for Word as the pre-4.5 format, you must delete it completely from the server, update it in

11

Before You Begin

the pre-4.5 environment, and then import it again. Besides, you cannot import another copy orrevision of the same pre-4.5 document unless you first delete the previous document.

• For all xPresso documents, upgrade the 4.2 documents by upgrading the 4.2 server. The upgradeprocess automatically assigns version numbers to all documents in the xPression database.

Back Up Database and Server FilesTo back up your database and server files, complete the following steps:

1. To make a backup copy of all of your xPression properties files, use the xAdmin CheckVersionutility to create a .zip file package of all properties files. Use the utility to create the zip file backupand save it to a network location. See the xAdmin User Guide for instructions.

2. Stop the xPression Server.

3. Create a copy of your xPressionHome directory in a temporary location.

4. To create a backup of your xPression database, use the facilities of your database system.

Remove Font and Cache Agent ServicesThis step applies only to users who are upgrading from xPression 4.0 and lower versions. The Fontand Cache handling has been upgraded. The Font Agent and Cache Agent custom services that youadded to your application server are no longer needed. Though they are not likely to adverselyaffect your server performance, EMC Document Sciences recommended removing the unneededcomponents.

To Remove the Custom Services on WebSphere1. Log in to the WebSphere administrative console.

2. Expand Servers in the left pane, expand Server Type, clickWebSphere Application Servers,and click the server name.

3. In the Server Infrastructure section, expand Administration and click Custom Services.

4. Delete the Font and Cache agent custom services.

5. Save the changes to your master configuration.

To Remove the Custom Services on WebLogic1. Locate the Domain Structure section and expand the Environment item.

2. Click Startup & Shutdown Classes.

3. Select the Font Agent and the Cache Agent and click Delete.

4. Save your changes.

12

Before You Begin

Exporting xPression 2.5 Output ProfilesDue to significant structure changes in output processing, the upgrade process will not upgradeyour xPression 2.5 output profiles. You must export your 2.5 output profiles from your version 2.5environment before upgrading. After you upgrade your environment, you can then import the 2.5output profiles to the new environment.

Start the server and log on to xAdmin. Access Migration Utilities and export all needed outputprofiles to PDPX files. The only way to preserve your output profiles is to export them from your 2.5server, upgrade the server, and import the output profiles into your upgraded server.

EMC Document Sciences recommends that you remove any existing xPression (workgroup edition)Server that resides on the application server where you will install xPression.

13

Before You Begin

14

Chapter 2Step One: Upgrade xPression Database

The database scripts vary depending on the version you are upgrading from. The scripts can beprovided by your EMC Document Sciences representative or in the installation package.

Note:• This section contains general instructions for upgrading your xPression database to version4.6SP1. To upgrade to a patch version, refer to the corresponding xPression Patch Release Notes.

• xPression does not support upgrading your database from 4.6 P10 or higher versions to 4.6SP1General availability (GA) version.

To upgrade your xPression database, see the following topics:• Upgrading From 4.1 SP1 and Higher Versions, page 15

• Upgrading From a Version Lower than 4.1 SP1, page 16

• Upgrading xPressForms Database, page 17

Upgrading From 4.1 SP1 and Higher VersionsIf the dbtype_4.2to4.5_additional_tables.sql script exists in your CRUpgrade directory,verify if the XPF_FORMDATA table exists in the xPression database, and then perform one of thefollowing steps. Where dbtype is SQL, Ora, or DB2 depending on the type of database you are using(SQL Server, Oracle, or DB2).• If XPF_FORMDATA exists, do NOT run dbtype_4.2to4.5_additional_tables.sql.Proceed to upgrade the xPression Server.

• If XPF_FORMDATA does not exist, and your company is NOT running xPressForms or xPressionCatalog, run dbtype_4.2to4.5_additional_tables.sql.

• If XPF_FORMDATA does not exist, and your company is running xPressForms or xPressionCatalog, contact EMC Technical Support for additional information and assistance or refer tothe Upgrading xPressForms Database section.

To upgrade your database from any patch of xPression 4.1 SP1, xPression 4.2, xPression 4.5, xPression4.5 SP1 and xPression 4.6 to xPression 4.6 Sevice Pack, use the procedure below:

1. Locate the CRScriptGenerator tool in your installation package.Provide the xPressionHome directory when prompted.

15

Step One: Upgrade xPression Database

2. Upgrade your xPression database by using the following procedure:a. Extract the contents of CRScriptGenerator to a local directory. For UNIX and Linux platforms,

grant execution permission to the files in the local directory.

b. Open the CRupgrade directory, and run the patch-level upgrade scripts in asequence. For example, to upgrade Oracle database from xPression 4.1 SP1 P01, runOra_4.1sp1_Patch02.sql, Ora_4.1sp1_Patch03.sql, ..., and so on.

c. Run the version-level upgrade scripts in a sequence. For example, to upgrade Oracledatabase from xPression 4.1 SP1 P01, run Ora_4.1sp1to4.2.sql, Ora_4.2to4.5.sql,Ora_4.5to4.5sp1.sql, and Ora_4.5SP1to4.6.sql.

Note: You may encounter an error when running SQL_4.5to4.5SP1, Ora_4.5to4.5SP1,or DB2_4.5to4.5SP1. You can safely ignore the error.

Upgrading From a Version Lower than 4.1 SP1To upgrade your xPression database from a version lower than 4.1 SP1, contact your EMC DocumentSciences representative to get the upgrade scripts and instructions.

Upgrading From xPression 2.x

Ensure that the t_mailinfo, t_archiveinfo, and t_printinfo database tables are empty before runningthe upgrade scripts. A new column, “SERVERNAME”, will be added to each of these tables. Thevalue of this column will be null if the table is not emptied prior to upgrading.

If records are found with null SERVERNAME values after upgrading, contact EMC DocumentSciences Support for help in updating the SERVERNAME. If these tables are not empty, any recordswill not be picked up without manual intervention and this intervention will require assistancefrom Solution Support.

Upgrading From Pre–3.0 SP1 Versions for DB2 Users

If you are using DB2 and upgrading from 3.0 SP1 or earlier versions, you must check the size of theUSERSPACE tablespace. You will experience errors while running the database upgrade scripts ifyour xPression database was created with an insufficient USERSPACE tablespace allocation. Aminimum allocation of 8 k USERSPACE is recommended. If your USERSPACE tablespace is less than8 k, perform the following steps before running any upgrade scripts.

1. Export the data from the T_DATASOURCEGROUP and T_BUSINESSCATEGORY tables.

2. Drop these two tables.

3. Re-create the same tables with USERSPACE8K.

4. Import the data back into the tables.

5. Run your xPression database upgrade scripts.

16


Upgrading xPressForms DatabaseWith xPression 3.0 SP1, users have the option of deploying the xPressForms tables to either thexPression database or a separate database. For 4.0 and higher versions, the xPressForms tablesmust reside in the xPression database. Users with two databases (one xPressForms database andone xPression database) must move the xPressForms tables to the xPression database. This chaptercontains upgrading steps for users with two databases (xPressForms and xPression in separatedatabases) and users with one database (xPressForms and xPression share one database).

If you use the default UID prefix (DSC) in xPression 3.0 SP1, the UID prefix will be automaticallychanged to the new default prefix with the version 4.0 upgrade script. The new default UID prefix isXPF.

To Upgrade Your xPressForms Database1. Back up the existing database.

2. Determine where your xPressForms tables reside. If your xPressForms tables reside in a separatedatabase, do the steps in Moving the Database, page 17.

3. Follow the instructions in Upgrading From 4.1 SP1 and Higher Versions, page 15 or UpgradingFrom a Version Lower than 4.1 SP1, page 16 to run correct database scripts.

Determining the Database In-Use

To determine if your xPressForms tables reside in their own database or in the xPression database,open the database management console to browse the tables in the xPression database. ThexPressForms tables begin with the following prefix: XPF. If any of the tables starts with XPF, yourxPressForms tables reside in the xPression database, and you do not need to move the tables. Runthe upgrade scripts to upgrade your database.

If your xPression database does not contain those tables, the tables reside in a separate database,and you must move the tables before upgrading. See Moving the Database, page 17 for detailedinstructions.

Moving the Database

xPression 4.0 and higher versions require that the xPressForms database tables reside in the xPressiondatabase. If you have installed the xPressForms tables to a separate database, you must move thetables to the xPression database. The exact steps for this procedure differ for each database type.The following procedure shows general steps:

1. Export the data from the old xPressForms database.

2. Run revised xPressForms installation scripts that create the xPressForms tables on the xPressiondatabase, but do not define an identity for these tables.

3. Import the data to the xPression database.

17


4. Add foreign key, constraints, and triggers.

5. Restore the identity or sequence.To move the xPressforms database for each database type, see the following topics:• Moving the Database for SQL Server, page 18

• Moving the Database for DB2, page 20

• Moving the Database for Oracle, page 22

Moving the Database for SQL Server

Complete the following steps to move the xPressForms tables from an xPressForms database to thexPression database on SQL Server:

1. Run the DTSWizard.

2. Run the primary key scripts.

3. Reset the Identity.

Run the DTSWizard

To start the DTSWizard, type dtswizard from the command line. Follow the DTSWizard to copy thetables and data from the existing xPressForms database. Make the following selections in the wizard:• On the Choose a Data Source page, select the source (xPressForms) database.

In the Authentication section, define your authentication settings. These settings should enableyou to access the xPressForms database.

Select your xPressForms database from the drop-down list.

• On the Choose a Destination page, select the destination (xPression) database.

In the Authentication section, define your authentication settings. These settings should enableyou to access the xPressForms database.

Select your xPression database from the drop-down list.

• On the Specify Table Copy or Query page, select Copy data from one or more tables or views.

• On the Select Source Tables and Views page, select the xPressForms tables that need to be copiedto the xPression database. Select all tables in the Source column and click Next. The DTSWizardwill export the data from the xPressForms database and import it into the xPression database.

The DTSWizard does not define primary keys for the data it migrates. Proceed to Run the PrimaryKey Scripts, page 18 to create the primary keys.

Run the Primary Key Scripts

The imported tables do not contain a primary key. Run the following scripts to add a primary key.You can copy the text for the script directly from this document.

18


ALTER TABLE XPF_FORMDATA ADD CONSTRAINT FORMDATA_UI PRIMARY KEY CLUSTERED(UNIQUE_ID ASC);

ALTER TABLE XPF_PERSPECTIVE ADD CONSTRAINT PK_PERSPECTIVE PRIMARY KEY CLUSTERED(NAME ASC, PALETTE ASC);

ALTER TABLE XPF_PERSPECTIVE_FIELDS ADD CONSTRAINT PK_PERSPECTIVE_FIELDS PRIMARYKEY CLUSTERED (PERSPECTIVE_TABLES_ID ASC, FIELD_NAME ASC);

ALTER TABLE XPF_PERSPECTIVE_TABLES ADD CONSTRAINT PK_PERSPECTIVE_TABLES PRIMARYKEY CLUSTERED (PERSPECTIVE_ID ASC, NAME ASC);

ALTER TABLE XPF_PERSPECTIVE_FORM ADD CONSTRAINT PK_PERSPECTIVE_FORM PRIMARY KEYCLUSTERED (PERSPECTIVE_ID ASC, UNIQUE_ID ASC);

ALTER TABLE XPF_TAG_FORMS ADD CONSTRAINT PK_TAG_FORMS PRIMARY KEY CLUSTERED(UNIQUE_ID ASC, TAG_ID ASC);

ALTER TABLE XPF_TAG_PERSPECTIVE ADD CONSTRAINT PK_TAG_PERSPECTIVE PRIMARY KEYCLUSTERED (TAG_ID ASC);

ALTER TABLE XPF_TAG_PERSPECTIVE_TABLES ADD CONSTRAINT PK_TAG_PERSPECTIVE_TABLESPRIMARY KEY CLUSTERED (PERSPECTIVE_ID ASC, NAME ASC);

ALTER TABLE XPF_TAG_PERSPECTIVE_FIELDS ADD CONSTRAINT PK_TAG_PERSPECTIVE_FIELDSPRIMARY KEY CLUSTERED (PERSPECTIVE_TABLES_ID ASC, FIELD_NAME ASC);

ALTER TABLE XPF_TAGS ADD CONSTRAINT DF__XPF_TAGS__TAGOWNER__ DEFAULT 'System'FOR TAGOWNER;

ALTER TABLE XPF_TAGS ADD CONSTRAINT DF__XPF_TAGS__ISREQUIRED__ DEFAULT 'false'FOR ISREQUIRED;

ALTER TABLE XPF_TAGS ADD CONSTRAINT DF__XPF_TAGS__ISDEFAULT__ DEFAULT 'false'FOR ISDEFAULT;

Reset Identity

Some of the table columns need to be set as Identity. Use the SQL Server Management Studio tolocate the following table columns.• XPF_PERSPECTIVE_FIELDS.PERSPECTIVE_FIELDS_ID

• XPF_PERSPECTIVE_TABLES.PERSPECTIVE_TABLES_ID

• XPF_TAGS.TAG_ID

• XPF_TAG_PERSPECTIVE.PERSPECTIVE_ID

• XPF_TAG_PERSPECTIVE_FIELDS.PERSPECTIVE_FIELDS_ID

• XPF_TAG_PERSPECTIVE_TABLES.PERSPECTIVE_TABLES_ID

For each table column, view the Column Properties in the right pane and set (Is Identity) to Yes.

19


Moving the Database for DB2

Complete the following steps to move the xPressForms table from an xPressForms database to thexPression database on DB2:

1. Export data.

2. Create tables.

3. Import data.

4. Reset Identity.

Export Data

To export all the xPressForms tables to a temporary location, complete the following steps:

1. Create a work folder to temporarily contain the exported data. This example usesC:\db2upgrade.

2. After creating the work folder, open a command window and navigate to the work folder. Forexample:cd db2upgrade

3. Initialize the Command Line Environment. In the command window, type:db2cmd

This will open the db2 command window, indicating that the initialization was successful.

4. Export the data from the xPressForms database. Connect to the xPressForms database using thefollowing command:connect to database_name user username using password

where database_name is the name of the xPressForms database, username is the username underwhich the tables were created, and password is the password for the user.If successful, you should see database connection information showing the server, SQLauthorization ID, and local database alias.

5. Type Quit and press Enter.

6. Export the data by using the following command:db2move database_name export -tc username -tn xpf_*

where database_name is the name of the xPressForms database, username is that created the tables.This command will move all tables that start with xpf_ and were created by the defined user.

7. The export data will now reside in the temporary folder created in step one. In this folder will bea db2move.lst and EXPORT.out file, along with many .ixf and .msg files.Db2move.lst lists all exported files. The .ixf files are the xPressForms tables, and the .msg files aremessage files for each table. Export.out contains all messages created while exporting the data.

20


Create Tables

Connect to the xPression database and run the REVISED_DB2_xPressForms_3.0SP1.ddl script.

Import Data

For each .ixf file in the export directory, type the following command in the DB2 command windowto restore the database with the imported data:import from path_and_IXF_file of ixf insert into XPF_CONFIG

where path_and_IXF_file is the path and filename for the .ixf file that you want to import. Forexample:import from C:\db2upgrade\tab1.ixf of ixf insert into XPF_CONFIG

Reset Identity

Run the following scripts to reset the identity for the following tables from TABLE.IDENTITY_ID:• XPF_PERSPECTIVE_FIELDS.PERSPECTIVE_FIELDS_ID

• XPF_PERSPECTIVE_TABLES.PERSPECTIVE_TABLES_ID

• XPF_TAGS.TAG_ID

• XPF_TAG_PERSPECTIVE.PERSPECTIVE_ID

• XPF_TAG_PERSPECTIVE_FIELDS.PERSPECTIVE_FIELDS_ID

• XPF_TAG_PERSPECTIVE_TABLES.PERSPECTIVE_TABLES_ID

For each of these tables, you must run the following scripts to reset the identity, select the max valueof the identity column, and restart with a new value for the identity column.• This script sets the specified column {IDENTITY_ID} as an identity.

alter table {TABLE} alter column {IDENTITY _ID} set generated alwaysas identity (start with 1, increment by 1, no cache)

• This script works in conjunction with the next script. This script finds the max value of an identitycolumn. Identity will automatically generate an unique number. Each time you insert a newrecord, the identity column value has to increment by 1. We don’t know the current latest identityvalue for your database, so this script queries the database for the highest identity value.select max( {IDENTITY _ID} ) from {TABLE}

• This script uses the identity value from the last script and sets the restart number to a value that isone number higher than the current max value.alter table {TABLE} alter column {IDENTITY_ID} restart with max_value+1

For {TABLE} and {IDENTITY_ID}, use the table name and identity column name for each table.

For example:alter table XPF_PERSPECTIVE_FIELDS alter column PERSPECTIVE_FIELDS_ID setgenerated always as identity (start with 1, increment by 1, no cache)

select max(perspective_fields_id) from xpf_perspective_fields

21


alter table XPF_PERSPECTIVE_FIELDS alter column PERSPECTIVE_FIELDS_IDrestart with max_value+1

Moving the Database for Oracle

Complete the following steps to move the xPressForms table from an xPressForms database tothe xPression database on Oracle 9. For an explanation of all of the command parameters, see theOracle documentation.

1. Create a temporary folder. For this example, we will use c:\xPressFormsUpgrade\

2. Open a command window and navigate to the temporary folder.

3. Export all of the xPressForms tables to the temporary folder. Type the following command toconnect to the database and export all of the data, triggers, sequences, and indexes to the filenamed “xPressFormsUpgrade.dmp”:exp username/password rows=y indexes=y buffer=65536 feedback=10000owner=username file=C:\xPressFormsUpgrade\xPressFormsUpgrade.dmplog=C:\xPressFormsUpgrade\exp.log

4. Import the exported data by using the following command:imp username/password fromuser=username to user=username rows=ycommitt=y buffer=65536 feedback=10000 ignore=n file=C:\xPressFormsUpgrade.dmp log=C:\imp.log

22

Chapter 3Step Two: Uninstall the xPressionServer

To upgrade your xPression server, you must uninstall any existing version. See the xPressionInstallation Guide for detailed instructions on uninstalling xPression server.

23

Step Two: Uninstall the xPression Server

24

Chapter 4Step Three: Install xPression Server

You can then deploy the new enterprise archive (EAR) file, and install the latest version of xPressionserver.

1. Deploy the xPression EAR file using the correct procedure for your application server. See thexPression Installation Guide for detailed steps for each application server.

2. Install the xPression Server, page 25

3. Compare Directories, page 26

4. Delay the xRevise Upgrade, page 26

Install the xPression ServerInstall the xPression Server using the installation program. You can find detailed instructions in thexPression Installation Guide.

Before Upgrading the Server

Before installing the server, review the following issues:• AIX users must run the slibclean command before installing xPression. This command removesany currently unused modules in kernel and library memory. It unloads all object files with loadand use counts of 0. It can also be used to remove object files that are no longer used from both theshared library region and in the shared library and kernel text regions by removing object filesthat are no longer required. The command must be run from a root shell. Ensure that all of yourapplication servers have been shut down before running this command.

• From xPression 4.5, xPression began to support LDAPS and the Start TLS extension in LDAPV3. See the xPression Installation Guide for configuration information if you want to changeyour configuration.

• xPression supports Active Directory through the LDAPUser interface. If you were previouslyusing ADUser authentication, switch to use LDAPUser authentication. ADUser authentication isno longer supported.

25

Step Three: Install xPression Server

Compare DirectoriesCompare the new xPressionHome directory to the backup directory you created in Back Up Databaseand Server Files, page 12. Look for any custom settings made to the old server and transfer them overto the new directory. Do not simply copy the old files into the new directory because the new filescould contain new settings.

For each properties file that contains customized configurations, duplicate the configurations in thenew properties file. Copy your fonts from your old xPressionHome directory to your new directory.The fonts are located in the \Publish\FontCache subdirectory.

Delay the xRevise UpgradeYou can delay the upgrade of xRevise records until the server is started. This enables you to continueworking and using xPression while the xRevise records are being upgraded. While the upgradeprocess is operating, do not attempt to use xRevise.

To Delay the xRevise Upgrade Process1. Upgrade the xPression database and software using the upgrade instructions that came with

your upgrade package, but do not start the server. If you start the server after upgrading thesoftware, the automated upgrade process will begin and you will not be able to use xPressionuntil it completes.

2. In your xPressionHome directory on your server, open revise.properties for editing.

3. Add the following property to the end of the document:skipReviseUpgrade=true

4. Save and close the file.

5. Start the server. You will see a log message indicating that the xRevise upgrade process wasskipped.

6. Start Internet Explorer and use the URL:http://yourserver:port/xAdmin/html/utl_upgrade_revise_to_v4.jsp

where yourserver:port is the name or IP address of your server and your port number.

7. Log in to xAdmin. You will see a message that states that the upgrade process has begun. Closethe browser window.

8. The upgrade will run in a separate thread, and write INFOmessages to the xpression.log file every100 records. Individual work items are not listed unless you set logging to DEBUG mode. Whenthe upgrade completes, you will see a final log message stating that xRevise upgrade is complete.

26

Chapter 5Step Five: Post-Installation Tasks

After installing the xPression server, do the following tasks:• Enabling Additional Batchrunner Parameters, page 27

• Updating Your Documentum Configuration, page 28

• Upgrading a JBoss Environment, page 28

• Upgrading xRevise, page 29

• Removing Old Classpath Settings on WebSphere, page 29

•

Enabling Additional Batchrunner ParametersWhen upgrading it is necessary to manually update the batchrunner.sh (UNIX) or batchrunner.bat(Windows) file to enable support for 10 or more Batchrunner input parameters.

For batchrunner.sh (UNIX), add the following to the end of the Java command line:${10} ${11} ${12} ${13} ${14} ${15} ${16} ${17} ${18} ${19} ${20} ${21} ${22} ${23} ${24}

The line should resemble this:$JAVA_HOME/bin/java … com.dsc.uniarch.batchrunner.BatchRunner $1 $2 $3 $4 $5 $6 $7 $8 $9${10} ${11} ${12} ${13} ${14} ${15} ${16} ${17} ${18} ${19} ${20} ${21} ${22} ${23} ${24}

The portion represented by ..., between java and com, should not be changed.

For batchrunner.bat (Windows), add the following before the Java command line:SET VAR1=%1SET VAR2=%2SET VAR3=%3SET VAR4=%4SET VAR5=%5SET VAR6=%6SET VAR7=%7SET VAR8=%8SET VAR9=%9SHIFTSHIFTSHIFTSHIFTSHIFTSHIFT

27

Step Five: Post-Installation Tasks

SHIFTSHIFTSHIFTSET VAR10=%1SET VAR11=%2SET VAR12=%3SET VAR13=%4SET VAR14=%5SET VAR15=%6SET VAR16=%7SET VAR17=%8SET VAR18=%9SHIFTSHIFTSHIFTSHIFTSHIFTSHIFTSHIFTSHIFTSHIFTSET VAR19=%1SET VAR20=%2SET VAR21=%3SET VAR22=%4SET VAR23=%5SET VAR24=%6SET PARA=%VAR1% %VAR2% %VAR3% %VAR4% %VAR5% %VAR6% %VAR7% %VAR8% %VAR9% %VAR10%%VAR11% %VAR12% %VAR13% %VAR14% %VAR15% %VAR16% %VAR17% %VAR18% %VAR19% %VAR20%%VAR21% %VAR22% %VAR23 % %VAR24%

Then, change the Java command line to resemble the following:"%JAVA_HOME%\bin\java" … com.dsc.uniarch.batchrunner.BatchRunner2 %PARA%

The portion represented by ..., between java and com, should not be changed.

Updating Your Documentum ConfigurationThis step is required for Documentum users. Previously, encrypted passwords were not supported inthe xAdmin interface. Now, encrypted password are supported. If you have an existing DocumentumConfiguration, you must update the login account as described in the following steps:

1. Open the Documentum configuration.

2. Click Change Login Account.

3. Type and re-type the password in the indicated fields.

4. Click Save.

Upgrading a JBoss EnvironmentTo resolve a problem with the way xPression handled certain characters on the xAdminAccess Rights tab, the URIEncoding="UTF-8" attribute/value pair has been removed from

28


JBOSS_HOME\server\default\deploy\jbossweb-tomcat55.sar\server.xml. Whenupgrading your JBoss environment, ensure this attribute is removed.

Upgrading xReviseIf you are upgrading from xPression 3.0 SP1 or lower versions and are using FastPath with xRevise,you must regenerate your encrypted user/password string.

Removing Old Classpath Settings onWebSphereFrom xPression 4.5, you are no longer required to include xPression_Cache.jar and log4j.jar in theapplication server classpath. You must remove these settings if your new xPression Server installationdirectory is installed to a location different from the existing location. If you are installing thexPression Server to the same location, this step is optional, but recommended.

Complete the following steps:

1. The classpath settings are located in the WebSphere admin console. Start the admin console.

2. In the left pane, select Servers > Server Type > WebSphere Application Servers > server1 > Javaand Process Management > Process Definition > Java Virtual Machine.

3. For the Classpath setting, remove the following lines:• ${XPRESSION_EAR}\log4j.jar

• ${XPRESSIONHOME}\Drivers\xPression_Cache.jar

4. Click OK and save your changes to the master configuration.

29


30

Chapter 6Upgrading xPression ClientApplications

To upgrade the xPression client applications, locate your product in the following list and followthe instructions:• Upgrading xDesign, page 31

• Upgrading xPresso for Word, page 32

• Upgrading xPresso for Adobe InDesign, page 33

• Upgrading xPresso for Dreamweaver, page 33

• About Upgrading xEditor, page 34

Upgrading xDesignxPression only provides the .NET version of xDesign. See the xPression Release Notes for a full listof new features.

Templates created in xDesign .NET cannot be used with the legacy version of xDesign, and vice versa.

Upgrading xDesign

Before upgrading xDesign, ensure that you have backed up any critical files in the xDesign installationdirectory. The installation process removes many of these files.

To Upgrade xDesign1. Open your xDesign installation directory, and back up the following directory:

xDesign_install_dir\Template

2. Start the removal program from Windows Control Panel to remove xDesign.

3. When the removal is completed, the Installshield Wizard displays all files that were not removed.Click Remove Files, and complete the uninstallation.

4. Copy the new xDesign installer to the local machine and run the installation program accordingto the instructions in the xPression Installation Guide.

31

Upgrading xPression Client Applications

Upgrading Word Templates for xDesign

The xDesign Installshield Wizard deploys two new Microsoft Word templates to the \Templatedirectory. If you want to use your old templates with custom or modified styles, you must upgradethe xPression Word templates with the using the Word Template Tool provided with xDesign ifyou want to do the following:

• Edit the existing xDesign document which was created based on the old xPression MicrosoftWord templates.

• Apply styles in existing Microsoft Word templates to the xDesign documents.

To Upgrade Word Templates1. From your Windows Start menu, open All Programs > EMC Document Sciences > xPression >

Word Template Tool. The xDesignWord Template Tool dialog appears. You can also findthe tool at the following location:xDesign_Home\bin\xDesignTemplateTool.exe

where xDesign_Home is the directory that you installed your xDesign.

2. In the Old or Existing Customized Template field, supply the full path of your old template.

3. In the New Default Template (Supplied with New xDesign) field, browseto your \Template folder and select a template. xPression provides youwith two templates: LetterSamplesWordTemplate_V46SP1.dotm andxPressionWordTemplate_V46SP1.dotm. Select the one that has the same name with whichyour old template is based on.

4. In the New Customized Template (Target) field, supply the name and full path of the targettemplate. If the target template does not exist, xPression creates it for you.

5. Click Run. A message pops out to indicate that the upgrade is successful.

6. In Microsoft Word, access the templates by selecting Developer tab > Templates group >Document Template > Organizer from the Word ribbon. Ensure that all your customized stylesare in the template, and the xPression tab appears in the Word Ribbon.

InstallShield Error When Upgrading xDesign

If you are not logging in Windows using the same user ID that is used when the original installationof xDesign was done, you may encounter an InstallShield error when upgrading xDesign.

This error can also occur when using the Administrator login. To solve this issue, either log inWindows using the original user ID and then upgrade xDesign.

Upgrading xPresso for WordxPresso for Word 4.6SP1 and 4.2 can be installed on the same workstation. If you have installedxPresso for Word 4.2, and want to work with both 4.2 and 4.6SP1 on your computer, you do not need

32


to uninstall xPresso for Word 4.2. For any other versions, you must uninstall xPresso for Wordbefore upgrading.

To upgrade xPresso for Word, use the Windows Add/Remove Programs utility to uninstall yourexisting version of xPresso for Word, and then install xPresso for Word using the new installer inyour installation package. See the xPression Installation Guide for detailed instructions.

Upgrading xPresso for Adobe InDesignUninstall your xPresso for Adobe InDesign, and then install xPresso for Adobe InDesign using thenew installer in your installation package. For detailed steps of uninstallation and installation, seexPression Installation Guide.

Displaying Turkish Characters

If you are upgrading from version 4.5, to display the Turkish characters, Ğ, ğ, Ş, ş, İ, and I in Cordacharts, copy and paste the TrueType fonts for Arial and the .fsd fonts to the following directories:• xPression plug-in directory on 32-bit systems: Your_drive\Program Files\Common

Files\xPresso\version\Corda\Resources\lib\fsfiles

• xPression plug-in directory on 64-bit systems: Your_drive\Program Files (x86)\CommonFiles\xPresso\version\Corda\Resources\lib\fsfiles

• Corda chart directory: Corda_directory\Resources\lib\fsfiles (where Corda_directoryis the folder where you installed Corda Builder.)

Upgrading xPresso for DreamweaverYou must remove your current version prior to upgrading to the new version.

To Upgrade xPresso for Dreamweaver1. Uninstall xPresso for Dreamweaver. To do so, you must remove the xPresso for Dreamweaver

extension through the Extension Manager. See the detailed steps in the xPression Installation Guide.

2. Reinstall xPresso for Dreamweaver. See the xPression Installation Guide for detailed steps.

Disabling the xPresso for Dreamweaver Extension

If you want to disable the xPresso for Dreamweaver extension in the Extension Manager withoutremoving it, follow the procedure in this section. When an extension is disabled, it still exists onthe system, but you cannot use it in Dreamweaver. If you try to install a new version of xPressofor Dreamweaver when the existing version is disabled, you may encounter errors. To install a

33


new version, ensure that the existing version is enabled (on), or remove the existing version, andthen install the new version.

To Disable xPresso for Dreamweaver on Windows1. Stop Adobe Dreamweaver.

2. Launch cmd.exe with Administrator privileges.

3. Navigate to the Extension Manager command-line tool folder.

4. Enter ExManCmd /list all, you can see xPresso if it is installed already.

5. To disable xPresso, enter ExManCmd /disable xPresso; to enable it again, enter ExManCmd/enable xPresso.

6. Restart Adobe Dreamweaver.xPresso disappears from toolbar.

Uninstalling xPresso for DreamweaverTo uninstall xPresso for Dreamweaver on your system,Remove the xPresso for Dreamweaver extension through the uninstaller. Use the following options:

• On Windows, navigate to Control Panel > Programs and Features and click xPresso forDreamweaver

• On Macintosh, go toMacintosh HD > Applications > Adobe Dreamweaver CC 2015 > xPresso> UinstallerData, click Uninstall_xPresso_for_Dreamweaver.

See the detailed steps in the xPression Installation Guide.

About Upgrading xEditorxPression uses automatic installation and upgrade for xEditor. To upgrade xEditor, ensure youhave upgraded the xPression Server. After you have upgraded the xPression Server, xPressionruns the automatic installer for xEditor when you try to open xEditor for the first time. For moreinformation, see the xPression Installation Guide.

Currently, xEditor version is changed in every build, and xEditor startup application pushes thedeployed xEditor to the client side based on the value of the Assembly Version parameter value.This value is updated based on the code changes (compared to a daily build number). As a result,xEditor is installed only if the code base is different from the one already installed on the client side.

34


The Assembly Version property of the xEditor binaries, intended to identify the code changesmade to xEditor, is updated following these rules:

• It is initialized with a particular version number.

• In case of the code change in any xEditor component, the version is updated to the latest formalbuild number (meaning the file version number).

• xEditor startup application compares the assembly version of xEditor on xPression server with theassembly version of the locally installed xEditor to determine whether the upgrade or downgradeoperation is required.

The assembly version information is saved to the xEditor startup log when you access a work item.You can access and verify the xEditor startup log at the following location:"C:\Users\<user login name>\AppData\Roaming\EMC Document Sciences\EditorStartup.log"

For example:04:28:40:440 INFO The assembly version of the xEditor on xPression server is [4.6.1.2]

35


36

Chapter 7Changes for Upgrade Users

After upgrading, the output appearance of your existing documents or settings may be affected.Review the following sections:• 4.6 SP1 Changes, page 37

• 4.6 Changes, page 41

• 4.5 SP1 Changes, page 42



• 4.1 SP1 Changes, page 51


4.6 SP1 ChangesIf you are upgrading from a version lower than xPression 4.6 SP1, note the issues described in thissection:• xPression Documentum Edition (DE) and xPression Enterprise Edition (EE), page 37

• SSH and TLS Certificates Support, page 39

• Changes to Document Naming Conventions, page 39

• Output of the Documents with Hidden End Mark Property, page 39

• Keep with Next, page 40Changes in Default “Normal” Style, page 40

• Number Rounding in JDK, page 40

xPression Documentum Edition (DE) and xPressionEnterprise Edition (EE)

xPression Documentum Edition (DE) has been merged into the xPression Enterprise Edition (EE)platform in this release.

37

Changes for Upgrade Users

In previous versions, xPression DE had a separate Enterprise Archive (EAR) resource. Now there isnow a single EAR for both xPression DE and xPression EE.

During the server installation, it is no longer required to specify the deployment type of xPression DEversus xPression EE. See xPression Installation Guide for details.

xPression DE users will see some changes in xPression Admin, however, all the previous functionalityavailable under prior versions of xPression DE is still available under this new deployment model.See xAdmin User Guide for more details.

xPression DE upgrade user will also see more files and folders under xPressionHome which are forxPression EE. xPression DE users can ignore them. See the list of these components in table below.

Table 1. xPression Home Files and Folders Not Applicable in xPression DE

Component name Files and folders which are not applicable forxPression DE users

xPressionHome xPressForms.properties

reviseStyles.properties

revise.properties

ofp.properties

log4j.isc.config.xml

eCor.properties

<DIR>bin

<DIR>Compuset

<DIR>xEditor

xPressionHome > PdpUploadFolder CsetBridgeOP_PDP.zip

CsetBridgeDoc_PDP.zip

xPressionHome > Drivers ccam32.dll

CMPCAL32.DLL

cmpcalwrapper.dll

Compubld.ini crlink.dll

gendll.dll h2csc.dll

h2cscwrapper.dll

JavaWrapper.dll

MPS.dll OP.dll SK32W.DLL

38


Users upgrading xPression DE you can also find additional war files after deploying thexPression.ear file. These files are not relevant to xPression DE and can be ignored. Refer to thelist below for details:

• xCatalog.war

• xDevKit.war

• xPressForms.war

• xPression_Response.war

• xPression_Revise.war

• xPressionAdapter.war

Note: To avoid a security issue, a defaultDatasourceSampleDataPath parameter is addedinto systemconfig.properties in to configure where the customer data file can be placed. Ifthe defined customer data location is not a child or grandchild directory, an error message appearsprompting the data into the required folder. The defaultDatasourceSampleDataPath parameter caninclude multiple folders separated by a semicolon.

SSH and TLS Certificates Support

All Document Sciences xPression applications have been upgraded to support .NET 4.5 framework.So we recommend you to update the .NET version to 4.5 for xPression Design, xPresso for Word, andxEditor following the procedures in corresponding User Guides.

Changes to Document Naming Conventions

In 4.6 SP1, xDesign, xPresso for Word, xPresso for Adobe InDesign and xPresso for Dreamweaverhave a new document naming convention. We do not recommend to use the following characters: $ :@ / \ ! ? * # { } ( ) & < > " ’ | and unit separator.

You do not need to modify the existing documents names though as these rules apply to the newlycreated documents only.

Output of the Documents with Hidden End MarkProperty

If a paragraph has a variable, and the paragraph marker is hidden, the hidden property of theparagraph marker is not applied in the final DOCX output. The paragraph marker is not hiddenin the DOCX output.

39


Keep with Next

In previous versions, if a continuous section exceeded the current page, and all paragraphs in thecurrent page were set to keep with next, the keep with next option did not work. This problem hasbeen fixed. Beginning paragraphs that exceed the current page are moved to the next page.

Changes in Default “Normal” Style

To align the definition of “Normal” style in xDesign, Microsoft Word templates to definitionin xDesign 4.5SP1 and earlier versions, font and paragraph space of “Normal” style in the twodefault word templates is changed. They are LetterSamplesWordTemplate_V46SP1.dotmand xPressionWordTemplate_V46SP1.dotm under <xDesign install root>\Design\Template directory.

Changes from xDesign version 4.6:• Font: (Default) Arial, Left

• Line spacing: Multiple 1.15 li, SpaceAfter: 10 pt

• Widow/Orphan control, Style: Quick Style

Changes to xDesign version 4.6SP1:• Font: (Default) Times New Roman, 12 pt, Left

• Line spacing: single, Widow/Orphan control, Style: Quick Style

Instead of applying those two new templates to xDesign document based on default Microsoft Wordtemplates (provided in xDesign 4.6), we recommend you one of the following:• Upgrade xDesign 4.6 templates using Word template tool shipped with xDesign;

• Manually merge the styles changes from the old word templates (xDesign 4.6) to the newMicrosoft Word templates (xDesign 4.6SP1).

Number Rounding in JDK

The JDK 1.8 treats floating point type calculations differently than previous versions of the JDK.Calculations that are performed in versions of xPression before version 4.6 SP1 will producedifferent results because of the way numbers are rounded within the JDK.

This issue is present after you upgrade from any prior version of xPression to version 4.6 SP1,because version 4.6 SP1 uses the JDK 1.8.

We recommend that you perform your floating point type calculations outside of xPression and thenuse xPression to display the calculation results.

40


4.6 ChangesIf you are upgrading from a previous version, note the following issues:• Table Row Height in xPresso for Word Documents, page 41

• Pie Chart in Content Loop, page 41

• Outputting Spot CMYK Colors, page 41

• Table Width in xDesign Online Editor, page 41

• Hyperlink Styles in xEditor, page 42

Table Row Height in xPresso for Word Documents

With this version, if you specified a value for the row height of a table containing only one cell, therow height will be outputted as you specified. However, this row height is changed to an at-leastheight with previous versions of xPresso for Word.

Pie Chart in Content Loop

If a package (.xindd) is created with xPresso for Adobe InDesign 4.2 or lower versions, the Pie typedynamic chart inside a content loop might be incorrect in the output. To solve this issue, recreate thepackage with the latest version of xPresso for Adobe InDesign.

Outputting Spot CMYK Colors

In previous versions, process CMYK colors are outputted as spot CMYK colors. Since xPression 4.6,process CMYK colors in InDesign will be outputted as they are by default.

To output all process CMYK colors as spot CMYK colors, set the OutputProcessCMYKAsSpotCMYKproperty in the xInDesign_Configure_directory\xPressoConfig.ini file to true, and thenrecreate the package. See xPresso for Adobe InDesign User Guide for more information.

Table Width in xDesign Online Editor

If the width of a table is not configured in Microsoft Word styles, the table width will be calculateddynamically by your browser when opened with xDesign Online Editor. Therefore, the table layoutmay be different from that in Microsoft Word; however, the publish result is identical with whatyou see in Word.

41


Hyperlink Styles in xEditor

If your document is created with Micorsoft Word 2007 or earlier versions, the custom color definitionon hyperlink text might be removed when you save changes with xEditor. To avoid this issue,you can update the xDesign document to Word 2010 or 2013, or reapply the custom color on thehyperlink text with xEditor.

4.5 SP1 ChangesIf you are upgrading from a version lower than xPression 4.5 SP1, note the following issues:• Unmapped Array Items, page 42

• List Indent, page 42

• Keep with Next, page 42

• ECM System Password, page 43

• Location of xPresso Schema files, page 43

• Category Names Ended with Spaces, page 43

• VBA Access Error, page 43

• Number Rounding in JDK, page 40

• Allowing Backwards Compatibility for Metadata Naming Convention, page 43

• Resample Images to Output Resolution, page 44

Unmapped Array Items

In an xPresso for Word document, if an array item is not mapped, an exception error will occur whenyou publish or preview the document. However, this error is ignored in previous versions.

List Indent

If you apply a named style on a list, the indent defined in the named style overrides the indentdefined by the list style. As a result, the list indent in the output might be changed, compared withthe output from an earlier version.

Keep with Next

In previous versions, when you set the keep with next setting to start from the current row, thestarting position was incorrectly calculated. This problem was fixed. As a result, some content in theoutput might move up when compared with output published by previous versions.

42


ECM System Password

After upgrade, if the xPression server runs on a non-Windows operating system, the passwordconfigured for the ECM system in ECM configuration might not work. To resolve the problem, resetyour password in xAdmin.

Location of xPresso Schema files

Prior to xPression 4.5 SP1, the values of xPresso schema sources were not stored in the contentrepository. As a result, for an xPresso data source group that was created with a pre-4.5 SP1 versionof xPression, the source of the schema file is considered as “From Server”.

Category Names Ended with Spaces

If a category is ended with spaces, the spaces are deleted automatically when you save the category;however, in pre-4.5 SP1 versions of xPression, those spaces are kept. Therefore, re-save a categorywhose name is ended with spaces after you import the category from previous versions.

VBA Access Error

With xEditor, after you load a work item that contains pre-3.0 SP1 xDesign templates, theProgrammatic Access to Visual Basic Project is not trusted error may occur when you try to closexEditor. This is caused by the VBA script in xDesign template not applicable to xEditor.

To avoid this error, grant the access to the VBA project object model by doing the following steps:1. In Microsoft Office Word 2010, click Developer > Macro Security from the Word Ribbon. The

Trust Center window appears.

2. On theMacro Settings tab, select Trust access to the VBA project object model, and click OK.

3. Load the work item again with xEditor.

Allowing Backwards Compatibility for Metadata NamingConvention

When you perform upgrade, metadata file naming changes can cause various back end businessapplications issues. To avoid this situation, specify the IsOverwriteMetadataFile=true inxPressionPublish.properties file.

If IsOverwriteMetadataFile=true, the metadata file name always remains the same with thenaming definition on Distribution Definition of xAdmin.

43


If IsOverwriteMetadataFile=false and duplicate metadata file exists in same folder accordingto the naming definition on Distribution Definition of xAdmin, the metadata file naming conventionis changed into the existing name based on the following pattern:"_"<publish Date>"_"<UID>

Resample Images to Output Resolution

In previous versions, the "Resample Images to Output Resolution" option in Output Definitions onlysupported documents containing images of a higher resolution than that of the printer. This featurehas been enhanced. The "Resample Images to Output Resolution" option resamples images to theresolution of the printer, regardless of whether image resolution is higher or lower than that ofthe printer.

4.5 ChangesIf you are upgrading from a version lower than xPression 4.5, note the following issues:• Text Frames, page 45

• LDAP Issues, page 45

• PPD Files for AFP Emitter, page 45

• New PDF Emitter, page 46

• PCL Emitter, page 46

• User Exits, page 46

• About AutoInc Fields, page 46

• Single Cell Tables, page 47

• Table Rows with Exact Height, page 47

• Paragraph Alignment in Tables, page 47

• Underline, page 48

• Empty Paragraphs at the End of Content Items, page 48

• Inserted Images, page 48

• Hidden Paragraph Marks, page 48

• Subdocument Page Breaks, page 48

• Table Continuation Text Improvement, page 48

• Handling of Variables, page 49

• Character Spacing, page 49

• Font Weight, page 49

• TIFF Color, page 49

44


• Paragraphs With Borders, page 49

• Datamail Documents (4.5), page 50

• Image Fit Options (4.5), page 50

• Line Styles, page 49

• Line Spacing Improvements (4.5), page 50

• Schematic Log (4.5), page 50

Text Frames

Text frames are not supported in xPresso for Word. Issues may occur with templates that areconverted from previous versions. EMC Document Sciences recommends not including dynamiccontent in text frames.

LDAP Issues

The following issues should be taken into consideration when upgrading:• LDAP user authentication is no longer case-sensitive. This may cause problems if you previouslyconfigured authentication using "common name” (cn) for the LDAP_NAME_ATTRIBUTE.All common names must be unique. If your common names are no longer unique becausecase sensitivity was removed, you should make one of the following changes to your LDAPconfiguration:— Reconfigure your common names to make them unique.

— Change the LDAP_NAME_ATTRIBUTE in the ldapcfg.properties file to use UserID(UID) instead of common name (cn).

• ADUser authentication is no longer supported. See for instructions on updating yourconfiguration.

• In xPression pre-4.5 versions, the LDAP configuration file was named ldapcfg.txt. Thisconfiguration file has been renamed to ldapcfg.properties.

PPD Files for AFP Emitter

A new AFP emitter has been added. You can select whether to use the new AFP emitter or the old4.2 AFP emitter. See xAdmin User Guide for detailed information.

The following PPD files in xPressionHome\Publish\PPD can be used with 4.2 AFP emitteronly: afpbwcs.ppd, afpbwrf.ppd, afpccs.ppd, and afpcrf.ppd. For the new AFP emitter,use afpgeneral.ppd.

45


New PDF Emitter

A new PDF emitter has been added. This emitter processes fonts better than the old emitter, resultingin output that more closely matches the fonts in Microsoft Word. However, this means the outputPDF will differ slightly from outputs of previous versions. Verify your output and make adjustmentsas necessary.

PCL Emitter

The PCL emitter underwent changes regarding image handling. In dcpi.properties, the default valuefor the ImagePreferenceForPCL property was changed.

In 4.2 and earlier versions, the default value is:ImagePreferenceForPCL=tif;tiff.

With this version, the default value is:ImagePreferenceForPCL=group4;tif;tiff.

User Exits

xPression has improved the way users can load their User Exits. Previously, you were required to addthe class path to the startup script for the xPression Server. With this version, you can simply placetheir JAR files in the xPression Plugins folder located in the xPressionHome directory. The user exitswill load when the server starts. You no longer need to configure the classpath in the startup script.

Note: Several third-party libraries have been upgraded. If you use User Exits to retrieve your data,after the upgrade, you need to re-import the jars used in the xPression.ear folder and rebuildyour User Exits with referenced Jars path. Otherwise, you would encounter ClassNotFound errors orClass Casting errors.

About AutoInc Fields

If your data source uses AutoInc fields, each time xPression evaluates this field for customer data,its value will increase by 1.

Older versions of xPression used only the field name to track when a field was evaluated. Now,xPression tracks the field with the following information: data source + table name + field name.

Different Results of Numeric Calculations for xPressoFunction Variables

For xPresso function variables, you can include calculations in the xPresso function expression.However, the calculation results in xPression 4.5 and later might be different from the results in

46


versions prior to xPression 4.5. When processing a calculation, prior versions determine the numerictype of intermediate results according to the type of numbers used in the calculation. For example, inversions prior to 4.5, for the integer calculation 62/30*30, xPression gets an integer intermediate resultof 2 for the subcalculation 62/30, next calculates 2*30, and then gets the final result 60.

However, xPression version 4.5 and later use the double type for all the intermediate results ofcalculations. Using the same example 62/30*30, xPression gets a double-type intermediate result of2.066666666666667, calculates 2.066666666666667*30, and then gets the final result 62. Because of thischange, the results of calculations with integer–type and float-type numbers in xPression 4.5 andlater might be different but more precise than before. Calculations of double-type numbers andxPression functions are not affected.

The following table shows examples of different results of the same calculation in pre-4.5 documentsand 4.5 and later documents.

Calculations Pre-4.5 Results 4.5 and later Results

4599f/0.15f 30659.998 30660.0

30*(62/30) 60 62

62/30*30 60 62

30*62/30 62 62

Single Cell Tables

xDesign improved the handling of single-row, single-cell tables without a specified column width. Ifyour documents contain this type of table, you may see small differences in layout. The new resultmore closely matches the appearance in Microsoft Word.

Table Rows with Exact Height

If you have table rows defined with “exact height”, text will not overrun the cell borders. Previously,the cell text overrun the cell border.

Paragraph Alignment in Tables

With xDesign, if the width of a table cell is smaller than the combined size of the cell margins,paragraph alignment will not work. Previously, the paragraph alignment would be honored. Thenew result matches the result in Microsoft Word.

47


Underline

In previous versions, when a word was underlined, the underline rendered by xPression extendedbeyond the end of the word. xPression has been improved to match Microsoft Word, eliminating thetrailing underline. Additionally, xPression does not support the “Draw Underline on Trailing Spaces”feature accessible at Microsoft Office Button > Word Options > Advanced > Layout Options.

Empty Paragraphs at the End of Content Items

During publishing, xPression removes empty paragraphs at the end of content items. If your existingdocuments use empty paragraphs at the end of content items to create space in your output, the spacewill be removed after upgrading to xPression 4.5.

Inserted Images

xDesign adds a space after an inserted image. Prior to xPression 4.5, the composition engine publishedthis space. To enable your output to match the document appearance in Microsoft Word, xPressionno longer publishes this space character. As a result, the spacing around your images may change.

Hidden Paragraph Marks

xPression 4.5 has improved the handling of paragraph marks applied in hidden text. Output willnow more closely match Microsoft Word.

Subdocument Page Breaks

The way xPression handles page breaks has improved, but the improvement can cause changes toyour page counts. If you have a continuous section break followed by a page break, xPression willprocess the page breaks differently than before. If you have this condition and notice changes toyour page numbers, you can configure the CountPageBreakBeginningContinuousSection propertyin Dcpi.properties. Set the value to “False” to enable xPression to procese page breaks as it didprior to version 4.5.

Table Continuation Text Improvement

Implementation of the table continuation text is improved. Previously, the continued table headingmight represent the wrong table heading.

48


Handling of Variables

After finishing assembly, xPression will remove variable elements from the document. This willprevent unpredictable results that can occur when your variable values are shared across multiplecustomer records.

Character Spacing

xPression now supports the following feature: Font > Character Spacing options: Scale, Spacing, andKerning. If you have specified values for those options in an existing document, the value had noeffect on your document’s formatting. Once you publish that document in xPression 4.5, the valueswill be honored.

When using character spacing on Justified text, xPression cannot guarantee exact fidelity withMicrosoft Word.

Font Weight

An update was made to the xPression composition engine to more closely match output font weightwith that shown in Microsoft Word. Font weight in your output file will now appear heavier thanprevious releases, and it will more closely match what you see when editing in Microsoft Word.

TIFF Color

Due to enhancements in xPression color processing, TIFF images appear slightly darker than inprevious xPression versions.

Paragraphs With Borders

Documents that contain paragraphs with borders that appear within tables will see better horizontalpositioning of the text located in the paragraph. The text may slightly shift to the left comparedto previous versions.

Line Styles

Support for Microsoft Word and Adobe InDesign line styles has been improved. As a result,documents containing lines will see better rendering of lines in the output, with the lines more closelyresembling Word or InDesign. Additionally, support for Microsoft Word’s “Double-line” is greatlyimproved. The output more closesly matches what you see in Microsoft Word.

49


Datamail Documents (4.5)

The package format and the internal process for publishing xPresso for Adobe InDesign documenthas changed. The change requires more memory to publish the document than was used in previousversions. If your output document is very large, the process will noticeably consume more memory.

Image Fit Options (4.5)

xPresso for Adobe InDesign’s processing of image fit options has been improved. Because of thischange, images may appear to be scaled differently in output produced with version 4.5 as comparedto previous versions. The output now matches InDesign.

Line Spacing Improvements (4.5)

xPresso for Word line spacing improved, and it now more closely matches Microsoft Word linespacing when compared to output from xPresso for Word 4.2.

Schematic Log (4.5)

xPresso for Word version 4.5 does not contain the Schematic Log feature that existed in previousversions.

4.2 ChangesIf you are upgrading from a version lower than xPression 4.2, note the following issues:• Syntax Error When Using a 3.0 SP1 Output Profile, page 50

• Using “Space Before” with Multiple Column, page 51

• Numbered Paragraphs Beginning with White Spaces, page 51

• Font Size of an Empty Paragraph (4.2), page 51

Syntax Error When Using a 3.0 SP1 Output Profile

After you upgrade from xPression 3.0 SP1, you may encounter a syntax error in the distributiondefinition expression when trying to use an 3.0 SP1 output profile with xPression Batch. To solve thisissue, save the distribution definition in the latest version of xPression.

50


Using “Space Before” with Multiple Column

If you use multiple columns with the “Space Before” value set on the paragraphs in the columns,xPression likely used the “Space Before” value and applied it to the top of the second column. Thiswould result in the text from the second column starting at a lower point than the text in the firstcolumn. xPression now processes this value correctly, resulting in the text starting at a higher pointthan before.

Numbered Paragraphs Beginning with White Spaces

If you have numbered paragraphs that contain white space at the beginning of the line, outputstarting with xPression 4.2 will match Microsoft Word output. In previous releases, the indentationwas not applied correctly and resulted in larger than expected indentation.

Font Size of an Empty Paragraph (4.2)

The font size of an empty paragraph is correctly set, and it now more closely matches Microsoft Wordcanvas output when compared to output from xPresso for Word 4.1 SP1.

4.1 SP1 ChangesIf you are upgrading a version lower than xPression 4.1 SP1, note the following issues:• UTF-8 Non-Compliant XML Causes Error (4.1 SP1), page 52

• Migrating Content From Pre–4.1 SP1 Versions, page 52

• Documents Causing Application Failure, page 52

• Line Break Differences in Documents Using Kerning (4.1 SP1), page 53

• Spacing Above Tables (4.1 SP1), page 53

• Length of Underline in Tables is Shorter, page 53

• Some Variables are Not Replaced, page 53

• Text Wrapping and Alignment Improvements, page 53

• New Feature: Remove Empty Paragraphs, page 54

• Odd/Even Page Header and Footer Improvements, page 54

• New Feature: Character Spacing, page 54

• Vertical Alignment Improvements, page 54

• Empty Table Rows, page 55

• Table Row Alignment, page 54

• Empty Table Row Spacing, page 55

51


• Y-Position Discrepancy When Using Line Height Exactly, page 55

• Justified Text with Leading Spaces, page 55

• Empty Table Cells, page 55

• Different Y Position Due to Empty Table Cells, page 56

• Different Y Position Due to Empty Table Rows, page 56

• Empty Table Rows with Spanning, page 56

• Leading White Space in Numbered Paragraphs, page 56

• Cell Margins Exceed Cell Width, page 56

UTF-8 Non-Compliant XML Causes Error (4.1 SP1)

If your schema XML is malformed for any reason (for example, if characters are not properlyencoded), xAdmin will now generate an error when you set the Schema data path. Older versions ofxPression did not generate an error because xPression did not read the XML data as it does now. Toresolve the error, please fix the XML.

Migrating Content From Pre–4.1 SP1 Versions

In older versions of xPression, xAdmin allowed you to create Output Variables with the same nameas built-in xPression system variables. xAdmin will no longer allow the creation of these OutputVariables. If you are importing Output Variables from previous xPression versions that use the samename as an xPression system variable, ensure that you rename the Output Variable after import.

Documents Causing Application Failure

Some changes were made in the xPresso clients that may cause the client to fail when openingdocuments created in earlier versions. The failure does not result in an error condition, but the designclient will halt when attempting to open the document. The first case involves unsupported symbolsin variable names. The following symbols are not supported:$:@/!?*#[](){}&<>\"'

It is necessary to manually change the variable names so that they do not contain any unsupportedcharacters.

The second case involves the use of the xPath function in variables. The xPath function is no longersupported. The procedure for updating variables to use the updated function is found in the UserGuide for each design client. There are slight differences in each procedure, so refer to the “Variablesin Pre-4.0 Documents” section in your design client’s User Guide.

52


Line Break Differences in Documents Using Kerning(4.1 SP1)

The process for handling kerning has improved so that xPresso for InDesign documents now matchthe Adobe InDesign output. The line breaks in documents created prior to xPression 4.1 SP1 maydiffer when published in xPression 4.1 SP1. This issue impacts documents both in preview and batchoutput. Removing kerning should produce the same output as in earlier versions.

Spacing Above Tables (4.1 SP1)

The spacing applied above tables in previous versions of xPresso for Adobe InDesign was greaterthan that in Adobe InDesign without xPresso. The effect was cumulative, so the difference grew withthe length of the document. This issue has been corrected, so documents created in version prior toxPression 4.1 Patch 5 may have different spacing and page breaks when published with xPression4.1 Patch 5 and later, including any xPression 4.1 SP1 patch level.

Length of Underline in Tables is Shorter

If you have table text that is underlined, the output will now more closely match what you see inMicrosoft Word. The underline may be shorter than output from previous versions.

Some Variables are Not Replaced

In xPression 4.1sp1, some variables are not replaced as they were in 3.0 SP1. This occurs whenvariables have not had the DLSVAR style applied. xPression uses the DLSVAR style to identifyvariables. When this style is not applied the variable will not be processed properly. EMC DocumentSciences can provide a utility that will identify variables lacking the DLSVAR style. Please contactSupport for more information. Please contact Support for more information.

Text Wrapping and Alignment Improvements

Improvements were made that enable text wrapping and vertical alignment formatting to matchthe base output of Microsoft Word.

53


New Feature: Remove Empty Paragraphs

A new feature was added that removes paragraphs when their only content is an unresolved variable.This means that xPression will remove the paragraph instead of publishing an empty paragraph. Theparagraph will be removed if all of the following conditions are met:• The paragraph contains a variable.

• The variable (and any variable formatting) is the only content in the paragraph.

• The variable is unresolved (empty), meaning that no value could be found for the currentcustomer record.

To make output conform to the 3.0SP1 baseline, simply add the paragraph through regular formatting.

Odd/Even Page Header and Footer Improvements

Improvements were made that enable odd/page header and footer formatting to match the baseoutput of Microsoft Word. In an odd page footer, the page number correctly appears on the right sideof the page. In an even page footer, the page number correctly appears on the left side of the page.

New Feature: Character Spacing

xPression 3.0SP1 and earlier did not support the ”Scale” option on the Microsoft Word FontProperties “Character Spacing” tab. Support for this option was added during a patch release forxPression 4.1SP1. If your documents inadvertently contain “Scale” values, those values will beapplied to your documents and will likely change the look of your documents. EMC DocumentSciences can provide a utility that will turn off the “Scale” feature in your content. Please contactSupport for more information.

Vertical Alignment Improvements

Improvements were made that enable the vertical alignment of text in xPression output to match thebase output of Microsoft Word. This change created a difference in vertical spacing when comparedagainst output from xPression 3.0SP1.

Table Row Alignment

Table rows can now be aligned correctly, even when span rows in the document are not defined well.The alignment of the table rows now matches Microsoft Word, so document fidelity in this regard hasimproved over previous versions. The output of documents created in earlier versions may not matchoutput of the same document with the current version.

54


Empty Table Rows

The Y-position of content may appear different in documents with empty table rows. This is a resultof a fix that enables the automatic removal of empty tables rows, therefore changing the locationof following content on the page. The current output matches Microsoft Word more closely, sodocument fidelity in this regard has improved over previous versions. The output of documentscreated in earlier versions may not match output of the same document with the current version. Ifnecessary, y-position can be adjusted with standard formatting tools to compensate for the difference.

Empty Table Row Spacing

The spacing allocated for empty rows in previous versions was greater than in Microsoft Word.A fix has been implemented, and the current output matches Microsoft Word. As a result of thisimprovement, there may be some differences in page layouts of documents created in earlier versionof xPression if they contain empty table rows.

Y-Position Discrepancy When Using Line HeightExactly

The method for determining line height with the EXACTLY option has improved. This may resultin a difference in the appearance of pages where this option is used in documents created prior toxPression 4.1 SP1. It may be possible to achieve the previous effect by using a different line heightin the current version.

Justified Text with Leading Spaces

In previous versions, reserved leading spaces in justified text were justified along with the text. Inthe current version, reserved leading spaces are not justified even if the text is justified. xPression’shandling of leading spaces in justified text now matches Microsoft Word. As a result of thisimprovement, the X-position of some justified text may differ between output created in previousversions, and output created in this version.

Empty Table Cells

In previous versions, xPression considered the content height of cells that contained no contentas zero. Microsoft Word assumes an empty paragraph of Normal style exists in empty cells, andcalculates the corresponding paragraph, cell, and row height accordingly. xPression now alsoassumes an empty paragraph exists in empty table cells; therefore, the xPression output now matchesWord. Because of this change, there may be a difference in spacing where empty table cells exist indocuments created in a previous version of xPression.

55


Different Y Position Due to Empty Table Cells

There will be a Y-position (vertical) difference in documents that include empty table rows thatcontain spanning cells. In previous versions these rows were removed, but are no longer removedto be consistent with Microsoft Word. To produce the same output as previous versions, manuallyremove the empty table rows.

Different Y Position Due to Empty Table Rows

There will be a Y-position (vertical) difference in documents that include empty table rows thatare spanned with other rows. In previous versions empty rows were removed, even if they werespanned with other rows. Rows are no longer removed in this case, so all rows are retained. Thisis consistent with Microsoft Word. To produce the same output as previous versions, manuallyremove the empty rows.

Empty Table Rows with Spanning

In previous versions, all empty table rows were automatically removed, even those that containedspanned cells. In xPression 4.1 SP1, if the empty row contains spanned cells, the empty rows are notremoved. This change may cause a difference in spacing in tables with spanned cells in documentscreated with a previous version, and published with 4.1 SP1.

Leading White Space in Numbered Paragraphs

In the current version of xPression, leading white space that occurs in numbered paragraphs is beingjustified. This may cause a difference in the appearance of documents created in previous versionsand published with xPression 4.1 SP1. This issue will be fixed in a subsequent release.

Cell Margins Exceed Cell Width

If the margins of a cell exceed the width of the cell, the alignment of the text in the cell will be ignored.Previously, the alignment was honored.

4.1 ChangesIf you are upgrading from a version lower than xPression 4.1, note the following issues:• Barcode Resolution (4.1), page 58

• Corda Charts (4.1), page 58

56


• Cell Width and Line Breaks (4.1), page 58

• Space Before (4.1), page 58

• Line Spacing Discrepancy (4.1), page 59

• CS3 Users Upgrading from 3.0 SP1, page 59

• Lowercase Letters in Variable Names, page 59

• Uninitialized Variables, page 59

• Page Numbering after Page Breaking Section Break, page 60

• Out of Bounds Text in Table Cells, page 60

• Corda Charts, page 60

• Table Borders and Adjacent Tables, page 61

• Non-Breaking Spaces, page 61

• Non-Breaking Hyphens, page 61

• Y-Position Variance, page 61

• Non-Breaking Spaces and Hyphens in Combination, page 62

• Paragraph Spacing, page 62

• Exact Row Height, page 62

• Justification and Space Characters, page 62

• Table Cell Alignment in Web Service Output, page 62

• Output Style in Web Service Output, page 63

• Current Date in Barcodes, page 63

• Placeholder Table Cells, page 63

• Paragraph Appears Higher on Page, page 63

• Tables with Blank Lines, page 63

• Overall Table Height, page 64

• “Different First Page” Footers, page 64

• Undefined Variables, page 64

• Spaces in Optional Content, page 64

• Improvement in Y-position, page 64

• Non-Breaking Spaces, page 65

• OMR Barcode Output, page 65

• Page Numbering Logic, page 65

57


Barcode Resolution (4.1)

Originally all barcode resolution was established either with the BarcodeResolution property inDCPI.properties or through xAdmin. xPression supports multiple bar code formats. When usingBarcodeResolution, the setting affected all barcode resolutions, regardless of format. In cases wheremultiple barcode formats were used in the same document, it may have been challenging to achievethe desired result with both formats, and the issue is complicated by the IMB standard that specifiesthe overall length of the bar code. To resolve this, a new property has been added to DCPI.properties:IMBBarcodeResolution. This property affects Intelligent Mail Barcodes only, and Intelligent MailBarcodes are not affected by BarcodeResolution. When upgrading from previous version it may bedesirable to adjust the barcode resolution properties as appropriate to optimize bar code size.

Corda Charts (4.1)

The label settings for bar graphs in Corda 7.3 has changed and as a result the way image labels arerendered may change when upgrading. The following procedure can be used to manually changecharts.

To change the label position:1. Open Corda Builder.

2. Open the bar graph.

3. Select the graph.

4. From Object Properties open the Data Label tree.

5. If the Position setting is set to outside-top, change it to outside.

6. Save and close as desired.

Cell Width and Line Breaks (4.1)

The method for determining cell width has improved when publishing xPresso for InDesigndocuments through xBatch. This improvement may result in differences in line breaks within tablecells. To achieve the same result as in previous patches, adjust the table cell width to compensate.

Space Before (4.1)

InDesign does not include empty space prior to the first paragraph in a frame. In previous versionsof xPression this spacing was applied even when the paragraph was the first content in the frame.xPression 4 properly ignores the space preceding the paragraph that is the first content in the frame.xPresso for InDesign output now matches InDesign output.

To achieve the same spacing in xPression 4 consider using other formatting options.

This issue is for xPresso for InDesign and refers to fidelity with InDesign output.

58


Line Spacing Discrepancy (4.1)

As a result of improvements in xPresso for InDesign and in the composition engine, vertical linespacing in documents created in earlier versions may be greater when the document is produced inxPression 4.0 or later if the package has not been recreated since upgrade. Recreating the package inxPression 4.0 or later should restore the previous spacing.

CS3 Users Upgrading from 3.0 SP1

This issue applies to customers upgrading from 3.0 SP1 CS3 to xPression 4.2. An issue was fixed thatcaused content to disappear and text to display out of place when compared to output from previousversions. To ensure your output remains consistent with output from the previous version, youmay need to make the following adjustments:• Repackage your document. Also, ensure you repackage the document after you make anyadjustments or changes to the document.

• xPression handles linked frame layout differently than before. If the appearance of content in yourlinked frames is inconsistent with previous versions of the document, ensure that the linked frameis large enough to accommodate the content within. You may need to adjust the size of your frame.

• If you are using a WebLogic application server, you may need to increase the maximum messagesize setting in BatchRunner.properties. This value controls the maximum message size limit forbatch jobs. If your document contains large images, you may need to increase this value. Thisvalue appears as a parameter in the Java_Option section of the BatchRunner.properties. Forexample:-Dweblogic.MasMessageSize=50000000

Lowercase Letters in Variable Names

EMC Document Sciences made a change in xPression v4 to make variable names case insensitive.If you have variable names that are identical except for their case, xPression will generate an errorwhen you attempt to publish the document containing the variables. If both versions are found in asingle assembly an error is generated to provide the user with the opportunity to determine if theintention was for the different cases to represent different variables or the same variable. xDesignforces new variable rules to upper case. If your document has many subdocuments, you mayhave large numbers of mixed case variables involved in an assembly. EMC Document Sciencescan provide a utility that will search all rules, BDTs, and output profile mappings in the xPressiondatabase for mixed case variable names and replace them with upper case names. Please contactSupport for more information.

Uninitialized Variables

In xPression 3.0 SP1, if you had Variable Rule criteria that was not met during assembly, xPressionwould display an empty space where the variable was supposed to appear. This would happen if

59


your variable was initialized or uninitialized. In xPression 4.1 and beyond, if you have Variable Rulecriteria that is not met and the variable is uninitialized, the “Replacement field” will be shown in theoutput. EMC Document Sciences can provide a utility that will initialize all uninitialized variables inan existing document. Please contact Support for more information.

Page Numbering after Page Breaking Section Break

In previous version of xPression, page breaking section breaks created new pages under mostcircumstances, but in Microsoft Word the cases are more limited. Specifically, Microsoft Word createsa new page when an odd page section break is followed by an odd page, or an even page sectionbreak is followed by an even page.

xPression now matches Microsoft Word output in this respect. As a result the page count for somedocuments will be less and page n of m values will reflect the difference. To restore the previous pagecount, use page breaks to force the new page rather than page breaking section breaks.

Out of Bounds Text in Table Cells

If a tab character precedes a printable character in a table cell, and the tab is sufficiently large topush the printable character out of the cell, the AFP output will differ from the PDF output. In PDFoutput the printable character will be discarded and so not included in the output, while in AFPoutput the printable character included and forced outside the cell by the tab. The PDF outputmatches Microsoft Word. To include the printable character in PDF output, or to prevent forcing theprintable character outside the cell in AFP output, delete the tab or adjust the tab settings to allowsufficient space to print the character or characters.

Corda Charts

The label settings for bar graphs in Corda 7.3 has changed and as a result the way image labels arerendered may change when upgrading. The following procedure can be used to manually changecharts.

To change the label position:1. Open Corda Builder.

2. Open the bar graph.

3. Select the graph.

4. From Object Properties open the Data Label tree.

5. If the Position setting is set to outside-top, change it to outside.

6. Save and close as desired.

60


Table Borders and Adjacent Tables

If consecutive tables with different column layouts have no space between, and the horizontal borderuses a different style than the vertical border in the adjacent table, it may appear that the horizontalborder overlaps the vertical border.

In the example above, the row containing the phrase “When and how much?” is a single-row tableimmediately followed by another table. Since the tables do not have the same column layout, thetables are not merged together in the output and so the dotted border appears to overlap the shadedborder.

One way to avoid the appearance of overlapping borders is to apply the same column layout to bothtables. When both tables have the same column layout the two tables will be merged in the outputand the apparent overlap will be avoided.

Non-Breaking Spaces

The method for handling non-breaking spaces has improved. In previous versions non-breakingspaces were not honored consistently. For example, dates in the format “11 January 2010” couldbreak across a line even though the spaces within the date were non-breaking. Non-breaking spacesare now honored. As a result the output of documents with non-breaking spaces created in earlierversion may not match output of the same documents in the current version.

Non-Breaking Hyphens

The method for handling non-breaking hyphens has improved. In previous versions non-breakinghyphens were not honored consistently. For example, if “non-breaking” appeared near the end ofa line, “non-” could appear at the end of a line and “breaking” could appear at the beginning ofthe next line. Non-breaking hyphens are now honored. As a result the output of documents withnon-breaking hyphens created in earlier version may not match output of the same documentsin the current version.

Y-Position Variance

The Y-position of text may appear measurably closer to the left margin in certain documents,especially where tables are used. The exact amount depends on the structure of the document inquestion. The current output matches Microsoft Word in any case, regardless of the specific variance,so document fidelity in this regard has improved over previous versions. The output of documentscreated in earlier versions may not match output of the same document with the current version. Ifnecessary, y-position can be adjusted with standard formatting tools to compensate for the difference.

61


Non-Breaking Spaces and Hyphens in Combination

In earlier versions of xPression line breaks in paragraphs that contained a combination ofnon-breaking spaces and hyphens did not match Microsoft Word. In xPression 4 the line breaksmatch Microsoft Word. As a result, the output of documents using these features will not matchthe baseline when produced with xPression 4. Modifying the use of non-breaking spaces andapplying layout options may result in output that matches previous versions more closely. Checkingthe Collapse multiple spaces to a single space option in the variable format will help preventunexpected line breaks.

Paragraph Spacing

Paragraph Spacing Before and Paragraph Spacing After for paragraphs with borders should becalculated as a gap between the text and the border. In previous versions of xPression the gap wasnot calculated in this manner, but it is in xPression 4. As a result the spacing between the text and theborder in paragraphs using before/after spacing and borders will not be the same when upgradingdocuments created in earlier versions. The spacing when published in the current version is the sameas Microsoft Word. To obtain the same result as in previous xPression versions, adjust the spacingbefore or after as required to reduce the space between the text and the border.

Exact Row Height

Prior to xPression 4.0 the cell bottom margin was not included in the row height calculation whenusing Exact Height. Microsoft Word includes the cell bottom margin, and xPression does as well,so the cell height of documents created in earlier versions will be greater when published with thecurrent version of xPression. The current output matches Microsoft Word. To replicate the previousversion, adjust the specified row height as required to reduce the height and match the baseline.

Justification and Space Characters

In previous versions of xPression spaces were included when the text was justified. This resulted ina space prior to the first character in a line of text in some cases. This was a defect in the softwareand has been corrected in xPression 4.1. If a space is desired before the opening character in ajustified paragraph, set the indent for the first line as desired using Microsoft Word’s Indents andSpacing options.

Table Cell Alignment in Web Service Output

The position of text within table cells in web service output may differ when produced in xPression4.1. In previous versions, the reference for positioning the text was not correct. It may be possible toapproximate the previous version output by changing Microsoft Word’s spacing settings.

62


Output Style in Web Service Output

In some cases the style applied to web service output in previous versions of xPression did not matchthe styles in the source document, resulting in differences in fonts, justification, and position. Thisissue has been corrected in xPression 4.1. As a result, documents created in earlier versions may notmatch the baseline. To recreate the earlier output it may be necessary to reformat the document.

Current Date in Barcodes

In previous versions it was possible to include the current date in barcodes using the functionnumericToString(CurrentDate+CurrentTimeMillis,10,0). However, this provided the desired outputonly because the function was not executed properly. The fault has been corrected, so to includecurrent date in barcodes please use left(CurrentDate+CurrentTimeMillis,10) to achieve the sameresult as with the previous function.

Placeholder Table Cells

In previous versions of xPression the content and borders of placeholder table cells, that is cellsthat were intentionally left empty to act as placeholders, were ignored. This has been corrected inxPresson 4.0, so these placeholders are no longer ignored. As a result content following placeholdercells may appear lower on the page when produced in xPression 4.0 and later when compared toearlier versions. Eliminate unneeded placeholder table cells to avoid changing the page layout.

Paragraph Appears Higher on Page

xPression uses a number of tagged elements in the document for internal processing, but removesthem when the output is produced. In earlier versions the <dsc_opdata> tag was not removed inall cases. This has been corrected in xPression 4, so when these documents are produced in thecurrent version, content following this tag appears one line higher on the page when compared tobaseline output.

To achieve the same page layout as the previous version, consider using Microsoft Word layoutoptions such as margins or paragraph spacing.

Tables with Blank Lines

In previous versions blank lines in tables would be removed. This is not consistent with MicrosoftWord and has been corrected. As a result, the text position in documents with tables that containblank lines may differ when produced with the current version. To produce the same result as inprevious versions, remove the blank line.

63


In addition, right-aligned text is now correctly aligned with the right side of the cell. This matchesMicrosoft Word output. To achieve the same result as previous versions it will be necessary to useMicrosoft Word’s formatting options to adjust the alignment.

Overall Table Height

Table rendering has been improved so that the overall height of tables matches Microsoft Word. Theposition of content in affected tables will be the same as previous versions, but the bottom margin ofthe table may be lower than in previous versions.

“Different First Page” Footers

When the “Different First Page” option is set for a footer, subsequent pages in the section use thedefault footer. In previous versions of xPression, the first page footer was used if no default footerwas defined. In Microsoft Word, no footer is used in this case if no default footer is defined.

xPression 4 handles this case in the same way as Microsoft Word, so documents created in earlierversions may appear to be missing footers in sections where the footer used the “Different First Page”option. A footer can be applied to these sections either by selecting another option for the footer,or defining a default footer.

Undefined Variables

When xPression encounters an undefined variable it cannot assign a value. In earlier versions, if anundefined variable was the sole content of a line, the line would render as blank. This has beenimproved so that the blank line generated as a result of the presence of an undefined variable will beremoved.

To maintain the same spacing, use one of Microsoft Word’s formatting options.

Spaces in Optional Content

When optional content, that is content that is included or not included based on customer data,included a series of line breaks one of the line breaks may have been omitted in previous versions ofxPression. xPression 4 does not omit the blank lines as was the case, so there may be more space in theoutput where these spaces occur. To achieve the same spacing as before, delete the extra line break.

Improvement in Y-position

In certain cases documents that use a subdocument there will be an upward shift in Y-positionof some content. The current output is closer to output directly from Microsoft Word, so this is

64


an improvement in performance. This issue will only be noticed in documents created prior toxPression 3SP1 Build 73.

Non-Breaking Spaces

In earlier versions of xPression non-breaking spaces were not handled correctly. When published theoutput is now correct when compared to Microsoft Word. This improvement may cause documentscreated in earlier versions to appear different when published in xPression 4. To preserve theprevious effect in cases where output has changed it will be necessary to modify the document byusing hard breaks or other text devices.

OMR Barcode Output

In earlier versions the BarcodeResolution value in DCPI.properties was not honored for OMRbarcodes. As a result, OP created in earlier versions may render OMR bar codes differently if theBarcodeResolution value is different when produced in xPression 4.0. The setting is honored forother types of barcodes.

Page Numbering Logic

In previous versions it was possible for pages to be included in sub-document page counts thatshould not have been included. For example, if a sub-document ended with a next page sectionbreak and it was followed by a section starting with a next page section break, the end of the firstsub-document would not be honored and a blank page would be added, resulting in the page countincluding the improper blank page. The logic has been improved and the extra blank page in this casewould not be included in the sub-document’s page count. This may result in a difference between thetotal page value for page N of M page numbers when output is produced in xPression 4.0.

65