.Pitney Bowes Business Insight is delighted to announce the release of these CCM products. A summary of new features in this release is provided below. If you want to find out more, please browse the release notes and user documentation available on this site. You can also find information about problem fixes in the release and up-to-date details of known restrictions on the Report Tracking pages.
To receive your copy of the new version, please contact DOC1 Customer Support or your account manager.
DOC1 v5.6 Enhancements White space management A new design object has been created to allow specific management of space remaining on the last page of a document section or where a page throw is specifically requested. This remaining space, or 'white space' can be used for optional content such as advertisements or promotional material. Content objects that form part of a remaining space group will be placed only where there is sufficient space left over in the main body of the relevant page. You can specify any amount of additional content in this way which DOC1 will add to the page in the sequence it is defined in the logic map. Batch publishing You can now create production resources for DOC1 Generate or EngageOne Interactive without the need to open DOC1 Designer by using a command line utility and associated script file. This may be useful if you have large amounts of production resources to update regularly and need to automate the publishing process. Custom bar chart labeling Custom bar labels can now be defined for both 2D and 3D bar charts. Barcode enhancements The GS1 Databar barcode that is commonly used for goods tracking and discount coupons is now supported in DOC1 using the font scaling method. The font scaling method itself has been extended to support AFP, IJPDS and PCL output Dynamic paragraph merging Text from two consecutive paragraph objects in the publication logic map can now be merged together to form a single paragraph on the page. This feature can be used in conjunction with condition objects or active content to build a single paragraph from multiple sources. Keep text together A new character property allows you to mark phrases that should always be kept together on the same line. The ‘keep together’ option works for both regular text and variable data added to a paragraph. Extended language support for the HTML driver The DOC1 HTML driver now supports the use of extended character sets required for Chinese, Japanese and Korean text. Changing the sample data when previewing Once you have previewed a publication, you can now use the preview window to specify a different sample data and run preview again. Structured XML Journals A new journal type provides a consistent and automated method of logging commonly required run-time data such as page count and offset information. Custom elements can also be added to the journal as required. A schema is provided to allow the Structured XML journal to be easily interpreted by non-DOC1 post-composition processes. Enhanced support for XML input data Support for XML as the DOC1 input source has been extended to include <xs:sequence> and <xsi:type> constructs. Referencing printer resident fonts in PostScript environments Fonts from the printer environment can be referenced Postscript, VIPP and VPS output datastreams. When referencing certain types of PostScript fonts you have the option to specify a mapping file. Optimizing fonts and images for AFP When fonts or images are embedded in AFP output datastreams they can now be optimized so that only those that are actually used in the publication are embedded. AFP outline (FOCA Type1) fonts in PCE The support for AFP outline (FOCA Type1) fonts that was added to DOC1 Generate in 5.5 and 5.5.1 has now been extended to PCE. Background images in eHTML output Images can now be used as background for pages produced by the eHTML driver when viewed in the browser. They can be either tiled as necessary to fit the window or placed just once. Beta level support for virtualization of DOC1 Designer Several changes have been made to the DOC1 Designer to allow it to be installed and run as a virtualized client/server application using server software such as Citrix XenApp or Microsoft RemoteApp. We have conducted initial testing of these changes but we are aware that customer configurations of these type of environments can vary significantly and may not be reflected in our local test facilities. For this reason we are launching support for such application virtualization as a Beta level feature in version 5.6 of DOC1. There are no extra software or license keys required to install DOC1 Designer for virtualization so customers are free to trial this support as required. However, we are naturally very keen to get your feedback about how well this support performs and any problems that might be encountered. You can send your comments directly to our User Acceptance team at AAP@pb.com. Alternatively please contact your regional Customer Support office. CCM Content Author v5.6 Enhancements Interaction between message placement and publication logic A 'message signal' attribute can now be assigned to messages in the Content Author that can allow DOC1 applications to respond to specific messages being placed in a publication. This can have many uses but is likely to be particularly useful where external post composition actions are required: for example a signal can be used to initiate a DOC1 journal entry and the resulting journal file can then be used to control the insertion of appropriate additional material in a mailing package. Filtering message objects in DOC1 Designer When setting up message boxes or message streams within DOC1 Designer you can now filter the available message areas or data fields by project. This improves navigation in a large messaging environment EngageOne Interactive v1.2 Enhancements Enhanced template version control There is now a built in support for a template’s effective and withdrawn date, which when applied allows only one version of the template to be selected by the correspondent. Retention policies You can now define a retention period for folders with templates and Active Content. Expired folders can be moved or deleted from the content repository, so that you can easily manage template usage and control your disk space. Support for EngageOne non-accumulated batch Non-accumulated batch is now supported, which allows any number of XML input files, containing any number of records. This means that you can produce output using many templates, but each record defines which template to use, its effective date and delivery option. You can create templates for a batch job and interactive, for example, to produce chain letters or mail-merge. Support for multiple documents in a template Templates can be edited interactively in a multi-document publication using thumbnails to navigate between documents. Group Data Prompting You can now logically group together interactive prompts in a single prompt dialog such as address box, as well as dropdown and open text group prompts to optimize input. Enhanced Web Services Web services have now been simplified using a top down design to satisfy basic use cases, further reducing integration efforts. New release also offers enriched Web services security. External key maps and keyed image support The new Image Management feature allows you to define key maps in EngageOne. To create a valid key map you must import the key map zip file created by the Key Map Generator tool. This is Windows utility, which allows you to select a target print stream and allocate the relevant image formats to convert source images into target image formats. The Configuration management feature allows you to move the content repository location and change database passwords and settings post installation. Oracle support Support for Oracle has now been added as the content repository. Support for structured journals Journal file enhancements allow for page level and document level information, as well as custom elements in the EngageOne report file. All information is pushed into EngageOne output variables. Incorporating resources from other repositories If a resource cannot be found during publishing, you are now given the opportunity to import any missing resources into your repository and continue publishing e2Vault Integration Enhancements Journal files (also known as DIJ files) generated by the EngageOne Server will now work without setting the vault option TolerateMissingSignature=1. The DIJ files have been added with DocInstanceId, DocMasterId, and ResourceGuid, which are all required by Vault for document loading. The templates and their associated device files only need to be republished in DOC1 Designer and be uploaded to the EngageOne Administration to leverage this feature.