Adobe LiveCycle ES3 Service Pack Installation Instructions

Adobe LiveCycle ES3 Service Pack Installation Instructions Service pack 2, Version 10.0.4 September 2012 Copyright 2012 Adobe Systems Incorporated and its licensors. All rights reserved. Contents Purpose of this service pack on page 1 Service pack overview on page 1 Known issues on page 2 Prepare to install the service pack on page 2 Install the service pack for Workbench and Designer on page 2 Install and configure the service pack for LiveCycle server on page 3 Install the service pack for LiveCycle server using GUI on page 3 Install the service pack for LiveCycle server using CLI on page 4 Install the service pack for Correspondence Management Solution on page 6 Run Configuration Manager on page 7 Upgrade to LiveCycle ES3 and install the service pack on page 9 Applying the service pack to an upgraded LiveCycle deployment on page 9 Issues addressed on page 10 Service pack 1 (10.0.3) on page 10 Service pack 2 (10.0.4) on page 14 Purpose of this service pack This service pack provides general fixes to Adobe LiveCycle Enterprise Suite 3 (ES3). Service pack overview To successfully install and deploy the service pack, you must complete the following steps: 1. Install the service pack. 2. Rebuild the EAR files using LiveCycle Configuration Manager. 3. Deploy the new EAR files using Configuration Manager or manually. 1

Service Pack Installation Instructions Known issues 2 4. Bootstrap the database. Note: This step does not affect the existing data. 5. Deploy the LiveCycle Components (DSC) using Configuration Manager. 6. Verify the service pack installation. Note: Click here for information about the supported platform combinations for LiveCycle ES3. Known issues For a complete list of the known issues in LiveCycle ES3, see the Release Notes document. Prepare to install the service pack Consider the following points before installing the service pack: Ensure that you have a fresh or an upgraded instance of LiveCycle ES3 running. For information on installing or upgrading to LiveCycle ES3, see the appropriate documentation at http://www.adobe.com/go/learn_lc_documentation_10. Use any MD5 encryption utility to verify that the service pack files are downloaded properly. The checksum number is posted on the Adobe download site. Ensure that your environment is backed up. To create a backup, follow the instructions at Backing up the LiveCycle data. Ensure that you have sufficient free disk space available to install the service packs. Service pack for LiveCycle server requires 6 GB of disk space. Service pack for Workbench requires 200 MB of disk space. Install the service pack for Workbench and Designer There are two methods used to incorporate Adobe LiveCycle Workbench 10 functionality into your LiveCycle environment: Default integrated development environment As a plug-in to an existing Eclipse 3.6.2 environment Perform the following procedure to install the service pack for Workbench: Note: There is no separate installer for Designer. The Designer files are updated automatically on installing the service pack for Workbench. 1. Ensure that Workbench is not running. 2. Install the service pack for Workbench by running adobelivecycle_workbench_patch\10.0\disk1\instdata\windows\vm\lcs3_sp_inst all.exe. This step opens a wizard that guides you through the installation. 3. On the Welcome screen, click Next.

Service Pack Installation Instructions Install and configure the service pack for LiveCycle server 3 4. On the Choose Install Folder screen, verify that the default location displayed is correct for your existing installation, or click Choose to select the alternate folder where Workbench is currently installed, and then click Next. 5. On the Service Pack Summary screen, review the information and, if it is correct, click Next. (Click Previous to correct any errors that occurred.) 6. On the Pre-Installation Summary screen, click Install. 7. On the Apply Patch screen, click Next to apply the updates. 8. When the Install Complete screen refreshes to indicate a successful installation, click Done. 9. Start Workbench. 10. Select Help > About Adobe LiveCycle Workbench ES3, and verify that Version 10.0.4.x is displayed on the startup screen. Install and configure the service pack for LiveCycle server Perform the following procedures to install the service pack: Install the service pack using the Graphical User Interface (GUI) (see Install the service pack for LiveCycle server using GUI on page 3). or Install the service pack using the Command-line interface (CLI) (see Install the service pack for LiveCycle server using CLI on page 4) (Optional) Install the patch for Correspondence Management Solution (see Install the service pack for Correspondence Management Solution on page 6) Configure and deploy LiveCycle for the service pack using LiveCycle Configuration manager (see Run Configuration Manager on page 7). Note: Ensure that Configuration Manager is not running before you start the service pack installation wizard. Caution: While running Configuration Manager, ensure that you perform the Initialize LiveCycle Database task to properly configure the service pack. This step does not affect the existing data. Install the service pack for LiveCycle server using GUI 1. Run the appropriate installer for your operating system: (32-bit Windows) 10.0.4-server\Disk1\InstData\Windows\VM\lces3_sp_install.exe (64-bit Windows) 10.0.4-server\Disk1\InstData\Windows_64bit\ VM/lces3_sp_install.exe (AIX) 10.0.4-server/Disk1/InstData/AIX/VM/lces3_sp_install.bin (Linux) 10.0.4-server/Disk1/InstData/Linux/NoVM/lces3_sp_install.bin (Solaris) 10.0.4-server/Disk1/InstData/Solaris/NoVM/lces3_sp_install.bin This step opens a wizard that guides you through the installation.

Service Pack Installation Instructions Install the service pack for LiveCycle server using CLI 4 Note: On a UNIX-like system, when you download files from the source, lces3_sp_install.bin might lose the executable permissions. Ensure that you restore the write-execute permissions after downloading the files. 2. When prompted, select the language to use for the installation and then click OK. 3. On the Introduction screen, click Next. 4. On the Choose Install Folder screen, verify that the default location displayed is correct for your existing installation, or click Browse to select the alternate folder where LiveCycle ES3 is currently installed, and click Next. 5. On the Service Pack Summary screen, review the information and, if it is correct, click Next. (Click Previous to go back to previous screens and correct errors, if any). 6. On the Pre-installation Summary screen, review the information and, if it is correct, click Install. (Click Previous to go back to previous screens and correct errors, if any.) Note: This step may take a few minutes to complete. 7. On the Apply Patch screen, click Next. Note: The typical time to apply patch updates is approximately 5 minutes. However, depending upon the resources available on your system, applying patches may take as many as 15 minutes. 8. When the Installation Complete screen refreshes to indicate a successful installation, ensure that Start Configuration Manager is selected and then click Done. Note: If you have Correspondence Management Solution running on LiveCycle ES3, it is recommended to install the service pack for Correspondence Management Solution, as described in Install the service pack for Correspondence Management Solution on page 6, before running the Configuration Manager. Note: On AIX, start Configuration Manager manually by running the ConfigurationManager.sh script from the [LiveCycle root]/configurationmanager/bin/ directory. Install the service pack for LiveCycle server using CLI 9. At the command line, navigate to the directory relevant for your operating system: (32-bit Windows) 10.0.4-server\Disk1\InstData\Windows\VM\ (64-bit Windows) 10.0.4-server\Disk1\InstData\Windows_64bit\VM\ (AIX) 10.0.4-server/Disk1/InstData/AIX/VM/ Note: AIX is supported only for WebSphere Application Server. (Linux) 10.0.4-server/Disk1/InstData/Linux/NoVM/ (Solaris) 10.0.4-server/Disk1/InstData/Solaris/NoVM/ 10. Execute the following command: (Windows) lces3_sp_install -i console (UNIX)./lces3_sp_install -i console 11. Follow the on-screen instructions. For more information, see the table below.

Service Pack Installation Instructions Install the service pack for LiveCycle server using CLI 5 Prompt Choose Locale Description Select the locale for the installation to use by entering a value from 1 through 3. Type 1 for German, 2 for English or 3 for French and then press Enter. You can also select the default language by pressing Enter. English is the default language. Note: If you are using Japanese language OS, you may see an option to select Japanese locale for the installation. Choose Install Folder On the Destination screen, press Enter to accept the default directory or select the location where LiveCycle ES3 in currently installed. Default install folders are: (Windows): C:\Adobe\Adobe LiveCycle ES3 (AIX, Linux, Solaris): /opt/adobe/adobe_livecycle_es3 Note: Do not use accented characters in the directory name. Otherwise, CLI will ignore the accents and create a directory after modifying the accented characters. Pre-Installation Summary Review the installation choices you have made and press Enter to continue installation with the choices you have made. Tip: Type back to go back to previous steps and change any of the settings. Ready To Install Installer displays the installation directory. Press Enter to start the installation process. During the installation process, the progress bar advances to indicate the progress of installation. Tip: Type back if you want to change the settings, or quit to close the installation. Installing Apply Patch The progress of the installation process is indicated. Press Enter to apply service pack and replace existing files with the updated ones.

Service Pack Installation Instructions Install the service pack for Correspondence Management Solution 6 Prompt LiveCycle Configuration Manager Installation Complete Description Press Enter to complete the installation. You can run the Configuration Manager by running the following script: (Windows): [LiveCycle_root]\configurationManager\bin\Config urationmanager.bat (AIX, Linux, Solaris): [LiveCycle_root]/configurationManager/bin/Config urationmanager.sh For more information, see Run Configuration Manager on page 7. For Configuration Manager steps relevant to clustered configurations, see the Configuring LiveCycle Application Server Clusters document that applies to your application server. The installation completion screen displays the status and the location of install. Press Enter to exit the installer. Note: To correctly uninstall LiveCycle, run the uninstaller from the command line, using the -i console flag. Install the service pack for Correspondence Management Solution 1. Stop the Application Server. 2. Run the Correspondence Management patch installer for your operating system: (32-bit Windows) 10.0.4-CMS\Disk1\InstData\Windows\VM\lces3_sp_install.exe (64-bit Windows) 10.0.4-CMS\Disk1\InstData\Windows_64bit\ VM/lces3_sp_install.exe (AIX) 10.0.4-CMS/Disk1/InstData/AIX/VM/lces3_sp_install.bin (Linux) 10.0.4-CMS/Disk1/InstData/Linux/NoVM/lces3_sp_install.bin (Solaris) 10.0.4-CMS/Disk1/InstData/Solaris/NoVM/lces3_sp_install.bin This step opens a wizard that guides you through the installation. 3. Select the language to use in the install wizard and click OK. 4. On the Introduction panel, click Next. 5. Either accept the default Adobe LiveCycle product directory or click Choose to select the location where LiveCycle ES3 and Correspondence Management Solution are installed, and then click Next. 6. Read the Patch Summary information and click Next. 7. Read the Pre-Installation Summary information and click Install. 8. When the installation is complete, click Next to apply the patch to your installed files.

Service Pack Installation Instructions Run Configuration Manager 7 9. When the Installation Complete screen refreshes to indicate a successful installation, ensure that Start Configuration Manager is selected and then click Done. You can now configure the service pack by running Configuration Manager. See Run Configuration Manager on page 7. Run Configuration Manager Note: If the Configuration Manager is running, Skip step 1 of the following procedure. 1. Start Configuration Manager manually by navigating to the [LiveCycle_root]/configurationManager/bin directory and entering the following command: (Windows) ConfigurationManager.bat (Linux, UNIX)./ConfigurationManager.sh 2. When prompted, select the language for the Configuration Manager and click OK. 3. On the Welcome screen, click Next. 4. On the Upgrade Task Selection screen, ensure that no options are selected, and then click Next. 5. On Correspondence Management Solution Selection screen, Correspondence Management Solution 10.0.2 option is selected by default. With this option selected, you will be presented with the configuration screens to configure Correspondence Management Solution. Click Next to continue. Note: This screen will appear only if Correspondence Management Solution is installed. 6. On the Modules screen, keep the defaults or select the components that you have licensed. Click Next. 7. Perform the tasks in the table below that apply to your configuration. For more information, see the Installing and Deploying LiveCycle ES3 document for your application server. The complete LiveCycle ES3 documentation is available at http://www.adobe.com/go/learn_lc_documentation_10.

Service Pack Installation Instructions Run Configuration Manager 8 Configuration Task JBoss Application Server (turnkey) JBoss Application Server (partial turnkey) WebLogic Application Server WebSphere Application Server On the Task Selection screen, select the following tasks and then click Next. Navigate through all the following screens and perform the tasks listed on the respective screens. Configure LiveCycle EARs (Only for turnkey) Configure turnkey JBoss SSL (Optional) Configure Correspondence Management Solution (Optional; applicable only for WebSphere and WebLogic) Configure application server (Optional; applicable only for WebSphere and WebLogic) Validate application server configuration Deploy LiveCycle EAR files Initialize LiveCycle database Deploy LiveCycle components Validate LiveCycle component deployment Configure LiveCycle components (Optional) Import LiveCycle Samples Note: Do not select the tasks to configure the application server or to validate the application server if LiveCycle has been configured earlier. Note: If the following error appears in the application server log file, ignore it: UMConstants.ErrorCodes.E_RESTYPE_PREEXISTS_ WITH_SAME_ATTRIBUTE JBoss Application Server (non-turnkey) On the Task Selection screen, select Configure LiveCycle EAR files and Configure Correspondence Management Solution (optional) and click Next. Navigate through all the following screens and perform the tasks listed on the respective screens. Exit Configuration Manager and then manually undeploy the existing LiveCycle EAR files. Manually deploy the new LiveCycle EAR files. Return to Configuration Manager and, on the Task Selection screen, select the following tasks: Initialize LiveCycle database Deploy LiveCycle components Validate LiveCycle component deployment Configure LiveCycle components (Optional) Import LiveCycle Samples 8. Restart the application server.

Service Pack Installation Instructions Upgrade to LiveCycle ES3 and install the service pack 9 Note: In a clustered configuration, restart each application server instance of the cluster. Note: If you do not restart the application server after installing service pack, you may encounter error "ALC-WKS-007-027" and PDF forms will fail to render. 9. Log in to Administration Console by typing the URL http://[host name]:[port]/adminui in a web browser. Tip: To verify the service pack installation, log in to the Administration Console and select About. Ensure that the service pack version indicates SP2. Also, ensure that all Installed Modules report SP2 under the Patch column. Upgrade to LiveCycle ES3 and install the service pack Perform the following procedure to upgrade from LiveCycle version ES Update 1 or ES2 to LiveCycle ES3 and apply the service pack. To upgrade to LiveCycle ES3: 1. Upgrade to LiveCycle ES3 by following the instructions in the Upgrading to LiveCycle ES3 document for your application server. (See the "Installing the product files" section.) Do not start Configuration Manager. 2. Apply the service pack to the installed files by following steps 1 through 8 of the Install the service pack for LiveCycle server using GUI on page 3 procedure. 3. Start Configuration Manager as instructed in steps 1 through 3 of the Run Configuration Manager on page 7 procedure. 4. Complete the configuration, upgrade, and deployment by following the instructions in the "Configuring LiveCycle for Deployment" chapter of the Upgrading to LiveCycle ES3 document for your application server. Applying the service pack to an upgraded LiveCycle deployment If you have upgraded from LiveCycle ES Update1 or ES2 to LiveCycle ES3, perform the following steps to apply the service pack: To apply the service pack to an upgraded LiveCycle Server: 1. Apply the service pack by following the steps 1 through 8 of the Install the service pack for LiveCycle server using GUI on page 3 procedure in this document. 2. Start Configuration Manager as instructed in steps 1 through 3 of the Run Configuration Manager on page 7 procedure. 3. On the Upgrade Task Selection screen, select one of the following, as required: Upgrade from LiveCycle ES Update 1 Upgrade from LiveCycle ES2 or LiveCycle ES 2.5 4. On the Task Selection screen, select the following task options: Configure EARs

Service Pack Installation Instructions Issues addressed 10 Deploy EARs (if you are deploying to JBoss Turnkey, WebSphere, or WebLogic; otherwise, you can manually redeploy the EAR files by following the instructions in the Installing and Deploying LiveCycle document for your application server.) Initialize database Deploy components Validate component deployment (Optional) Configure the connectors for ECM, Reader Extensions, and PDF Generator (Optional) Import Samples into LiveCycle Note: Do not select the tasks to configure the application server or validate the application server. 5. Complete the configuration, upgrade, and deployment of the patched EAR files by following the instructions in the Configuration Manager wizard and in the "Configuring LiveCycle for Deployment" section of the Upgrading to LiveCycle ES3 document for your application server. Note: If the LiveCycle 10.0.4 EAR files fail to deploy through Configuration Manager, manually undeploy the LiveCycle EAR files for the components you are updating according to the documentation. Restart the application server before you run Configuration Manager again. 6. Restart your application server. Tip: To verify the service pack installation, log in to the Administration Console and select About. Ensure that the service pack version indicates SP2. Also, ensure that all Installed Modules report SP2 under the Patch column. Issues addressed Service pack 1 (10.0.3) Assembler [Ref #3155930] DocConverter produces PDF/A document which fails preflight with Acrobat Professional, giving the error XMP property neither predefined nor defined in extension schema. [Ref #3153638] Validation for a PDF/A document using DocConverter validatepdfa and using Acrobat Professional returns conflicting results. [Ref #3152413] OutputIntent information is not displayed in the Acrobat Professional toolbar after Acrobat Professional loads a PDF/A document. [Ref #3142787, 3142784, 3142780, 3171115, 3171123] Assembler docconvertor service does not correctly validate a PDFA/1b document. [Ref #3128365] While using East Asian fonts, the error 'Cannot find or create the font JYXYFU+MS-PGothic. Some characters may not be displayed or print correctly' is reported. [Ref #3126138] A PDF encrypted with 256-bit AES encryption cannot be decrypted by DDX, and an error results. [Ref #3171157] Conversion of a PDF document to PDF/A fails on Linux OS, whereas, the document successfully converts on Windows OS.

Service Pack Installation Instructions Service pack 1 (10.0.3) 11 [Ref #3171118] Documents converted and validated successfully using Callas, fail PDF/A validation using docconvertor. [Ref #3171130] A PDF document converted to a erroneous PDF/A-1b document incorrectly passes the validation. [Ref #3171186] A PDF document fails conversion giving the error 'Annotation uses RGB GTS_PDFA1 color space, but not found in the destination output profiles'. [Ref #3171140] Conversion of a PDF document to PDF/A-1b and the validation fails giving the error 'ICC profile version is 4.0 or higher'. [Ref #3106472] Forms and Output cache grows endlessly, resulting in low disk space on the server. Core [Ref # 3151676] Stale sessions are created in the Oracle database when using certain LiveCycle SQL statements. [Ref # 3161085] The Automated Ordering process for a batch with multiple requests throws an OverlappingFileLockException exception. Core - Standard Services [Ref # 3158282] Mapping a blob object returned by JDBCService to a Document type variable fails with an InvalidCoercionException exception. [Ref # 3140796] The WriteString operation in Workbench fails to append to an existing file. [Ref # 3158278] An exception is thrown when trying to add the JDBCService component to a workflow. [Ref # 3139624] The FTP PUT service is not backward compatible. [Ref # 3158242] On a Unix-based NFS mount, the WriteFile service writes a 0-byte file to and fails with an exception. Core - User Manager [Ref # 3160029] Authentication using SAML fails with the "The assertion is not signed correctly" error. [Ref # 3161042] After being authenticated using SAML, the user get redirected to a page with the following error: You have reached this page because cookies might not be enabled on your browser. Please enable the cookies and then re access the LiveCycle application. Correspondence Management Solution [Ref # 3151033] On pressing Delete, two characters instead of one, get deleted in the Correspondence Management text editor. [Ref # 3150913] Difficult to remove the content highlighting. A new checkbox, Enable CCR PDF highlight, has been added to the Create Correspondence UI, which when deselected disables the highlighting. [Ref # 3150852] The Content View is not the default view in the letter preview mode. [Ref # 3150850] The description for a placeholder or variable is not saved. [Ref # 3150845] Issues with the display when sorting assets. [Ref # 3157275] Conditional expressions in a repeating element are not evaluated.

Service Pack Installation Instructions Service pack 1 (10.0.3) 12 [Ref # 3151021] Japanese, French, and German characters are not supported in Correspondence Management assets names. [Ref # 3151013] Cannot remove an assigned post-process. [Ref # 3157292] Special characters are not supported in Correspondence Management assets names. [Ref # 3157325] Letter references are not updated if the text with variables is added to a condition or list. [Ref # 3157269] Changes made to a data dictionary do not reflect on the publish instance and other cluster nodes. [Ref # 3157271] Importing a letter with fragments fails if it already exists in the system. [Ref # 3157309] Imported packages in CRX are not deleted after the import is complete. Also, the package manager doesn t open if you import more than 500 packages. [Ref # 3070539] Added accessibility shortcuts in the Correspondence Management tools. PDF Generator [Ref #3155117] Adobe LiveCycle PDF Generator fails to convert Microsoft Visio files to Adobe PDF documents. The PDF generator process results in a time out. [Ref #3175079] Image2pdf service fails to convert TIFF file to an Adobe PDF document and user encounters Java heap space error. This issue occurs when TIFF file is created from a PDF document. [Ref # 3167046] When the PaperCaptureService operation times out, a new process instance is initiated instead of resuming the process from the memory. EMC Connectors [Ref #2928413] LiveCycle ES3 Connector for Microsoft SharePoint does not support Kerberos authentication protocol. [Ref #3110162] LiveCycle ES3 Connector for Microsoft SharePoint does not support Just in time creation of the users. [Ref #3097249] LiveCycle ES3 Connector for EMC Documentum does not support multiple connection broker. [Ref #3158272] Workbench does not restrict developers from creating an updated version of pre-existing LiveCycle application. Forms [Ref #3070554] Performance of rendering interactive forms through Assembler Service calls (using DDX) is not as expected. [Ref #3138506] Image Field content is reduced in dimensions when rendered in to a static PDF, and is rendered as expected in to a dynamic PDF. [Ref #3114642] After applying a quick fix to prevent text overlapping problems, some PDF to PDF/A conversions are not as expected. Specifically page break is now allowed in forms, where it was not previously allowed. [Ref #3106465] Forms and Output cache grows endlessly, resulting in low disk space on the server. [Ref #3105357] LiveCycle Designer in German locale crashes when changing the Overflow Leader from Inherited to None or New. This does not happen with English locale designer.

Service Pack Installation Instructions Service pack 1 (10.0.3) 13 Output [Ref #3156447] When a PostScript file is rendered using generateprintedoutput, the landscape page gets printed as portrait, resulting in trimming of the page content. [Ref #3139689] generatepdfoutput orchestration generates an exception when Acrobat X or higher is selected as the pdfoption. Workbench [Ref #3158295] While searching a custom event in Workbench, user encounters an error could not find event properties and search for the custom event fails. [Ref #3158287] User encounters document passivate error and LCA files fail to export. Slow response of the LiveCycle servers causes this issue. [Ref #3158235] The visual representation of process routes appears faded or deleted, when a process includes a large number of activities. This is an issue only with visual representation and does not affect the actual process functionality. [Ref #3158288] Addresses the following issues: An asset can not be checked in if the name of the asset is more than 128 bytes long Performance issues when working with large applications. Improved performance is noticeable on: Check in/out Synchronize/Get application Create LCA (Export) Delete Remote view of applications It also provides three new options available in the workbench.ini: com.adobe.workbench.export.disableimprovedexport: Use to enable or disable the new exporting method. This new exporting method is to avoid potential out of memory errors and time out errors on the LiveCycle serve when exporting a large application. The new exporting method retrieves a specified count of assets for one time and then retrieve the next specified count of assets for next time to avoid the out of memory and time out errors. The default value for this option is "false". Note: Although this will avoid potential errors, performance will be slower since there is the need for more connections between Workbench and the LiveCycle server. com.adobe.workbench.export.batchsize: Use to set the 'specified count' described in specification of com.adobe.workbench.export.disableimprovedexport. For some cases, the size of one asset in a large application (greater than 1mg), the users should decrease this 'specified count' otherwise the out of memory or time out will occur. The valid value for this option is 1 to unlimited integer, the default value is 100. com.adobe.workbench.synchronization.retrieveonetime: This option is similar to the com.adobe.workbench.export.batchsize option, and is used for Synchronization action. The synchronization action retrieves a specified count of assets for one time, if the size of a single asset is big the users should consider to decrease this number also. The valid value for this option is 1 to unlimited integer, the default value is 100.

Service Pack Installation Instructions Service pack 2 (10.0.4) 14 [Ref #3158293] Workbench encounters an internal error and fails to create a new version of a Form application on the Document server. [Ref #3158237, #3158275] User encounters an error com.adobe.idp.dsc.dscruntimeexception: Internal error while checking out XDP files and while synchronizing LiveCycle applications from server, check-in and check-out operation for large XDP files is slow. [Ref #3158268] The process designer is unavailable and activities are not visible when you leave a process open and restart the workbench. [Ref #3158275] Workbench is very slow while synchronizing LiveCycle applications from a server. [Ref #3131935] User encounters an error Failed to load/render Property Editor in Workbench. This error occurs when user expands the Form Data Mapping section of an Assign Task. [Ref #3158275] Workbench is very slow while synchronizing LiveCycle applications from a server. [Ref #3167363] In LiveCycle designer, the size of forms database increases with every check-out and check-in of forms. Purge tool to remove non-required version of forms is not available. Service pack 2 (10.0.4) Assembler [Ref #3177037] Assembler creates bookmarks with changed characters when creating PDF documents with Cyrillic characters. [Ref #3210263] On using Header or Footer tag in a DDX document, the resultant PDF does not contain any content. [Ref #3211252] In the Workbench, the text for XDP Result is overlapping in Document Builder view. Correspondence Management [Ref #2878338] Correspondence Management logs, present across various log files, are consolidated into a single log file. [Ref #2888367] StackOverFlowError is generated for RevertToLastPublish operation, while viewing previous version, and while rendering letters using cmletterpublishdate. [Ref #2900655] Upon deleting an extended property from a Data Dictionary element it is not deleted. [Ref #2920343] When the data type of a variable is updated, it shows correctly, but there is no information message, 'i' message about the change. [Ref #2921153] Upon updating a data module of a letter in Correspondence Management, there is no notification to indicate that a newer version of the module exists. [Ref #2926835] In Correspondence Management, RevertToLastPublish does not work, even though the user interface shows the asset to be successfully reverted. [Ref #2936053] Unexpected Error is thrown, instead of an appropriate exception, when an invalid value is passed to getuseddatamodules and getdependentmodules APIs [Ref #2945516] In Correspondence Management user interface, users cannot input Japanese characters in the Name field. However, they can copy paste the unsupported characters in the field. [Ref #2963182] While creating or modifying a DD, the corresponding element cannot be selected using keyboard because of an accessibility issue in the DD Editor. [Ref #2966063] Correspondence Management login and help messages are not translated into Japanese.

Service Pack Installation Instructions Service pack 2 (10.0.4) 15 [Ref #2969619] In Correspondence Management if a Text module is part of a condition and a list, the Export dependency does not work for the Text module. [Ref #2970935] In Correspondence Management the Reset button in the Advanced Search panel is not translated into Japanese. [Ref #2982506] In Correspondence Management, a condition cannot be applied to its own copy, unless it is saved once after copying. [Ref #2986510] In Correspondence Management, RevertToLastPublish operation fails for new and pre-existing imported assets. The asset remains in same state with same content as that of the imported asset. [Ref #2987581] Time taken to publish a DD is about a minute. [Ref #3015928] An unexpected error is generated when an invalid FormID is passed to getlayoutservice().getformbyversion API. [Ref #3034152] An unexpected error is generated when an invalid Form ID is passed to getfragment- LayoutService().getDependentLetters API. [Ref #3042512] An unexpected error is generated when a NULL or an invalid ID is passed to getlayout- Service().deleteForm API. [Ref #3063289] When ignore list style option is enabled for a list or a condition, it is applicable to other modules also. [Ref #3064458] When a new user is provided with administration rights, the user is not able to install packages in CRX. [Ref #3081695] In Correspondence Management, When a Content Data module is updated with empty file, the preview of the content still shows the content from the previous file. [Ref #3081838] In Correspondence Management, it is not possible to revert a Content Data module which has an associated letter, if both the letter and the module are published at least once. [Ref #3082834] In Correspondence Management, in the audit screen in Audit tab, the Advanced Search does not work. [Ref #3083944] In Correspondence Management, users are not able to save a letter if its name contains only a single letter of alphabet. [Ref #3084171] In Correspondence Management, SaveAsPDF, EmailPDF, and Print operations are enabled for drafted letters. [Ref #3084225] In Correspondence Management, Advanced Search in Letter tab does not work. [Ref #3084256] In Correspondence Management, upon submitting a letter the audit logs are not generated. [Ref #3084792] In Correspondence Management, a user is allowed to run SavePDF, Email, and Print operations on a letter even when the mandatory field are not filled. [Ref #3084854] In Correspondence Management, the caption for a letter body field in the Email Letter Editor is missing. [Ref #3084944] In Correspondence Management, if a drafted letter is edited again and saved, it prompts for a new name of the letter instance, even if a name for the letter instance is already mentioned. [Ref #3086068] In Correspondence Management, deactivation of a letter works only for the Published letters and not for letters in Modified or ReadyToPublish state, even if such letters are published once. [Ref #3086076] Multiple email addresses in the To field in email editor are not allowed.

Service Pack Installation Instructions Service pack 2 (10.0.4) 16 [Ref #3086438] In Correspondence Management, text box with UseDefault selected for it, gets disabled in certain scenarios. [Ref #3087326] In Correspondence Management, upon saving a letter as draft, 'letter submitted successfully' message is displayed, instead of a 'letter saved successfully' message. [Ref #3087588] In Correspondence Management, for letter preview and letter instance view, both operations, the 'Save as draft' option is enabled. [Ref #3088650] In Correspondence Management, the agentsignatureimage DDE does not get populated when previewing a letter. [Ref #3088690] In Correspondence Management, a letter instance name allows spaces and special characters to be typed in and saves them, instead of allowing only alphanumeric characters and underscores in the letter instance name. [Ref #3088875] In Administration Console, in CorrespondenceManagement/processes/SendToPrinter : 1.0 service, no default value is set for defaultprinturl. [Ref #3089073] Data Dictionary gets saved in published state when imported using Asset Manager user interface. [Ref #3089873] Letter fails to preview when the cmletterpublishdate parameter is passed in the preview URL. [Ref #3090020] Letter fails to reload when there is no attachment. [Ref #3090210] Edits made in Document Composer are not persisted when the original text module is edited. [Ref #3090258] Custom attributes are truncated if they do not fit on the audit details page. Also, there is a colon missing after newly added attributes' names. [Ref #3091067] The Save as Draft button is either disabled or missing when the Race condition is applied. [Ref #3091551] Read audit logs are not generated for Data Dictionary and Category. [Ref #3092605] No error message is shown if server fails to start. Also, it doesn't allow to log in to Asset Manager. [Ref #3092646] The letter instance name is not shown in the audit logs. [Ref #3094956] The persona ""jrobinson"" cannot view the Manage Templates user interface. [Ref #3122882] Any user with basic Correspondence Management roles can use the assetexportservice.importasset() API. [Ref #3127252] The performance of Manage Assets user interface degrades when multiple users are logged in and concurrently fire lots of search queries. [Ref #3130241] When creating a letter, it is allowed to link a variable to its source. [Ref #3131226] The ""datamoduleservice.createtestdatamodule()"" and ""formservice.createtest- Form()"" functions return ""java.lang.classcastexception: java.lang"" exception. [Ref #3152943] The text is not visible while typing text in Document Composer fields. [Ref #3159241] Letter fails to preview when the cmletterpublishdate parameter is passed in the preview URL. [Ref #3161060, #3161059] Spnego feature is not available for Correspondence Management running with CQ. [Ref #3166808] Read audit logs are not generated for Data Dictionary and Category.

Service Pack Installation Instructions Service pack 2 (10.0.4) 17 [Ref #3173789] The default value for Numeric Place Holder and Numeric field is set to 0 in the PDF. Also, the DDE variable defaults to 0 when its value is removed. [Ref #3173790] All DDE types are set to String even if they are integer or Boolean. [Ref #3173838] Inline Expressions are not evaluated for Integer and Boolean DDEs through server-side rendition. [Ref #3174967] The Race condition is applied during initialization phase preventing Correspondence Management to start up properly. [Ref #3175681] Fragment data does not merge with letter when rendered from server-side API. [Ref #3175879] Viewing, printing, saving, or mailing a draft of a letterinstance fails if its corresponding letter is deactivated. [Ref #3176354] Letters diagnosed with error ""Variable Assignment has an ID that does not exist"" do not auto correct. [Ref #3177002] There Indentation in the PDF generated from server and the one submitted from Document Composer is different, [Ref #3181178] Reload fails when XML is extracted from a PDF that is rendered from the server. [Ref #3181928] PDFs generated for the PolicyJacket sample letter from ES2 and ES2 service pack builds are different. [Ref #3182192] If multiple letters with common dependent assets are imported and one of the letters is published, the list of dependent assets also includes others letters which share the common dependent assets. [Ref #3183867] In Correspondence Management, the time taken to publish the first letter is unacceptably large. [Ref #3183901] English strings appear in Correspondence Management user interface for Japanese. [Ref #3185972] A DDE that is used by another computed DDE and used in a data module can be deleted. [Ref #3192504] Extremely slow publish performance on a server with large number of assets. [Ref #3192712] Blank error dialog pops up when you update the layout XDP of a published letter and try to republish it with the earlier cmpublishdate. [Ref #3192716] Flash exception occurs when rendering a letter with cmletterpublishdate, which is a date earlier than the original publishing date. [Ref #3193649] The documentation for the customization story related to Splitting Logic of Assets has been enhanced. [Ref #3194524] When saving a letter, the default letter instance name is blank. [Ref #3194714] If you publish an imported asset, the list of dependencies includes additional assets that have not been published. [Ref #3196445] The success page after submitting a letter opens in a new window. [Ref #3196468] Documentation added for Attachment support. [Ref #3196477] Documentation added for Delivery Mechanism feature. [Ref #3196494] Documentation added for Auditing feature. [Ref #3196501] Documentation added for Managing Letter Instances feature. [Ref #3196512] Documentation added for Deactivation of Letter feature. [Ref #3196678] Multiple issues related to importing and exporting of letters and data dictionary.

Service Pack Installation Instructions Service pack 2 (10.0.4) 18 [Ref #3196792] In Preview mode, the display does not return on resizing the screen. [Ref #3196795] Cannot tab to the next field. [Ref #3196796] In Correspondence Management, a placeholder with drop-down list of values does not display the values in the order the values were typed in. [Ref #3196805] Cannot preview a letter. [Ref #3196808] The order of placeholder has changed in Data Editing view after applying the patch 1.3.8. [Ref #3196915] A class cast exception is thrown when trying to save a letter instance. [Ref #3197891] Cannot view a letter instance saved as draft. [Ref #3198456] Audit logs are generated even if CRUD operation fails. [Ref #3199793] Viewing a letter instance fails when a data module, which wasn't selected in the original letter, is selected before submitting the letter. [Ref #3199808] On updating a DDE that is used in a condition automatically changes to protected mode. [Ref #3199935] Rendering a letter with cmpublishdate prior to the current publish date of a text module, returns latest published state of the text module. [Ref #3200316] Redundant OK, Yes, No, and Cancel buttons appear on an error message dialog. [Ref #3201225] The Submit button is not enabled even if all mandatory fields are populated. [Ref #3201261] Opening a letter for editing takes long time in Windows Internet Explorer and sometimes crashes in Mozilla Firefox. [Ref #3201262] Drop-down list in the Data Elements view do not function properly with the mouse. [Ref #3201269] The scroll bar in the Data view does not function properly with the mouse wheel. [Ref #3201335] The sample packages are updated to enable OMR and Duplicate Print features. [Ref #3201339] To enable HRSDC features, an LCA is required to be installed on LiveCycle. This is available at: //livecycle/icc/branches/hrsdc/distribution/crx-package/src/main/resources/etc/aep/deploy/docservic es/correspondencemanagement/10.0.0.0/lca/correspondencemanagementprocesses.lca [Ref #3201438] If you copy an asset and save the newly created asset, an audit log is not generated for this action. [Ref #3201463] In the Manage Assets user interface, the sorting of the columns Asset type, Action Type, status, and version in the data grid is incorrect. The columns must sort alphabetically. [Ref #3201518] Documentation is required for the updates to the Import / Export asset feature in Correspondence Management [Ref #3201561] The new APIs related for Letter Instance, Content Data Module, and Audit do not have ACLs applied to them. As a result of which all the users can perform CRUD operations on these APIs. [Ref #3201761] If you use the APIs to programmatically create a ContentDataModule, the system throws the error ""Content is Missing!!. The current error message is misleading since this error occurs because the filename is not set. [Ref #3202364] Documentation for the Correspondence Management configurations: On all Author instances, the Publish URL to be set for: com.adobe.livecycle.content.activate.impl.activationmanagerimpl On all Publish instances, the Author URL to be set for: com.adobe.livecycle.content.activate.impl.versionrestoremanagerimpl

Service Pack Installation Instructions Service pack 2 (10.0.4) 19 [Ref #3202535] The Correspondence Management option 'reload without latest' loads the latest published text asset if the text has bulleted content. [Ref #3202623] Content Data modules show up in content library. Users able to assign them to target area [Ref #3202708] A user is allowed to enable/disable the lock order for content in view mode. The Done button is also enabled. However, clicking the Done button does not perform any action. [Ref #3203607] The letter reload fails and an error, Error in reloading Letter : {fault code: fault, errid: 0, info: failed to reload variable, occurs. This error occurs when type of a variable is changed and letter is loaded using reload with latest option. [Ref #3203760] If a data dictionary element contains two variables such that the name of one variable is contained within the name of the other variable, the evaluation of the expression is not always computed correctly. [Ref #3204547] The letter submission fails, if the content of the letter and the filename of the content contain special characters. [Ref #3204666] When a letter is going to be deactivated, then the user is not notified that the letter will no longer be available on the publish instance. When the letter has been deactivated, then the user is not notified that the letter has been deactivated successfully. [Ref #3204702] Email, printing, or custom delivery of a published letter fails if the corresponding letter on the Author instance is deactivated [Ref #3205441] Documentation required to describe that print delivery mechanism works fine for PDF attachments but office documents & image attachments would work only for PDFG customers. [Ref #3205635] Default Print Dispatcher wrapper process fails if the associated letter does not contain any attachment [Ref #3205816] During the import package process, the CM Asset Import group check should not be performed for the admin user. [Ref #3207742] Change default values of Author and Publish URL set in com.adobe.livecycle.content.activate.impl.versionrestoremanagerimpl and com.adobe.livecycle.content.activate.impl.activationmanagerimpl APIs. The default values of author and publish should be 8080 & 8180 and ADEP should be replaced with lc. [Ref #3207790] The user should not be allowed to the name of a letter instance if the letter is saved as a draft. [Ref #3207793] The tool tip and icon for View Letter Instance should be changed [Ref #3207984] On the Attachments tab, say the Max. Number of Attachments is set to zero. If you save and view the letter instance and then go to the Attachments tab, the Max. Number of Attachments field displays a blank value. [Ref #3208023] The module is not assigned to its container information message when same module is assigned to a text asset twice. [Ref #3208196] If the Manage Letter Instance configuration is disabled on the Publish instance, the Letters tab must not display. [Ref #3208266] The audit logs generated for any action on the Author i\nstances are replicated on the Publish instance. [Ref #3208903] On selecting Manage Letter Instance on Publish option for an author the renderletter API is called and it causes an error letter Instance Creation and Updation is only supported from Publish Server.

Service Pack Installation Instructions Service pack 2 (10.0.4) 20 [Ref #3209375] The replication queue on the Publish instance is blocked if two Audit logs with the same name are generated. [Ref #3210560] When custom function is used in a condition, the default data module is always rendered along with the resultant module. [Ref #3210664] The documentation for associating a letter to the postprocess is required. [Ref #3211319] User encounters an error, No function is mapped to the name ""REMOTE_test:contains"". javax.servlet.jsp.el.elexception: No function is mapped to the name ""REMOTE_test:contains"", and the custom functions fails to work with computed DDE. [Ref #3212756] On retrieving the version of a letter that has complex dependency, the user encounters an error ""javax.jcr.pathnotfoundexception: No such node /content/apps/.."" [Ref #3213173] If splitting is enabled on a system and a package is exported from the System, then importing the package on another system displays in a blank list of imported assets. However, all the assets in the package are correctly imported into the destination system. [Ref #3217847] On selecting the Asset Library, the debug console displays an error. [Ref #3217850] After customer submits a letter and views the letter in Adobe Reader, the escape sequence \u2028 appears in both the ServiceNumber and DecisionNumber assets. [Ref #3217855] The color of the drop-down placeholder is always gray even if the field is mandatory and is not filled-in. [Ref #3220042] The customization build fails due to missing third-party libraries. [Ref #3220051] In the Configuration manager, auditing and all audit operations should be deselected (not enabled), by default. [Ref #3230469] The browser hangs and users encounter a Flash error while scrolling in the Asset Manager user interface. [Ref #3230471] On adding assets to a letter, the submit button is unavailable. [Ref #3230541] The check box that makes an image module visible/not visible stops working. This happens only when an image module within a list is reordered. [Ref #3231108] If a condition contains multiple expressions, only the first expression is evaluated. [Ref #3231113] If a condition contains multiple expressions, if the ""Condition may evaluate to multiple results"" option is selected, the multiple true results display in a random order. [Ref #3231332] The activatedatamodule and publishdatamodule APIs return DataModule with category and subcategory set to null. [Ref #3231350] The activateform and publishform APIs return form object with fields set to null. [Ref #3270730] The welcome message drop-down box does not show tool-tip text for user name. [Ref #3270744] The Correspondence Management user interface displays the principalname and the usedid. The user interface should not contain the principalname. [Ref #3283388] Check with QA [Ref #3283426] In Correspondence Management, the DDI creation time of a correspondence, specially on AIX-WAS platform, is optimized for better performance. [Ref #3287042] On installing LiveCycle ES3 Service Pack 2 (10.0.4) on a LiveCycle ES3 System, the URL http://server:port/lc opens an older version of the CRX login page instead of Correspondence Management Asset Manager user interface. [Ref #3287088] Marking primitives as key elements allows Composites, Collections, and their child elements also to be marked as 'Key Elements'.