PE_RN_Printable

XMPie® is pleased to announce the release of PersonalEffect version 6.5 build 6758.

The process of site creation and management from uCreate XM and Adobe Dreamweaver has been simplified to offer users a smooth and easy workflow.

uCreate XM becomes now your design center by offering you one point of control for all functions of site creation and design. You can now not only create your designs in Dreamweaver while enriching them with variable data tagging, email and page visit tracking functionality offered by uCreate XM, but also easily connect to RURL Wizard in order to create a new or import an existing site. There is no more need to separately create and transport .STE files from RURL Wizard.

When the user adds a new page in uCreate XM, the Page Settings window will have a default Port and its parameters selected. The default Port is the one that is used by other pages in the RURL site. This change will remove the need for repeated selections, thus improving usability and decreasing the possibility of errors. If needed, the user still has the option to override the default settings.

As part of PersonalEffect version 6.5, all types of email are created using a single interface of Email Activity. Emails that are prepared for distribution by an outside third-party can now be easily defined by selecting Prepare email for distribution as an email delivery provider and then using that provider when creating a new Email Activity. As a result, uProduce will generate all the files necessary for integration with the third-party delivery provider. This consistent approach to all email types promotes clarity and usability of the PersonalEffect system.

With PersonalEffect version 6.5, you can preview the email as it will be displayed for each individual recipient. The email preview functionality contributes to the uniform user experience in uProduce Online Email Editor and XMPie InDesign and Dreamweaver plug-ins.

In the previous versions, an Email Activity was used to define Mass Emails whereas the configuration of Triggered Emails was done separately in uCreate XM.

This version offers a single process to define both Mass and Triggered Emails. Both types of email are now based on the Email Activity definitions.

The Email Activity is created in uProduce. Defigning a Triggered Email in uCreate XM is done by simply selecting the required Email Activity in the relevant uCreate XM action (On page-load, Refer-a-friend or Self-registration ).

In PersonalEffect version 6.5, the configuration of Triggered Emails is based, similarly to Mass Emails, on the Email Activity. This uniform workflow for Mass and Triggered Emails, allows to track and analyze Triggered Emails with XMPie PersonalEffect Analytics.

Emails can contain links to websites. These links can lead either to personalized websites created with XMPie PersonalEffect, or to external websites, such as the brand's official website. With PersonalEffect version 6.5 you can track recipient clicks on any link in an email, whether internal or external. This feature is available with the ExactTarget Enhanced delivery provider and is integrated with PersonalEffect Analytics reporting.

Email Link Tracking requires Marketing Console version 2.2 or above to be installed. The new Email Clicks reports allow you to retrieve the email clicks tracking information. The following two reports are available:

• Email Clicks Population report - counts the number of recipients that clicked on a link in the email.

• Email Clicks Population List report - creates a list of all clicks, indicating the RecipientID, Touchpoint, Email Address, Link URL, and other user selected fields

The content of the HTML header in email messages affects different aspects of the email compatibility with various email clients. For example, the <meta name="viewport"> tag may improve email display on different mobile devices. PersonalEffect version 6.5 enables customers to take full advantage of these emails by sending not only the <body>, but also the <head> of the HTML to the email delivery provider.

In uCreate Print and uPlan, when using a text file Data Source (*.txt, *.csv) that contained missing values, the missing values were treated as empty strings. As a result, a QLingo condition comparing this value to an empty string returned a TRUE result. This behavior was inconsistent with uProduce Plan interpretation (Proofset and Job production) that treated missing values as NULL.

In version 6.5, empty strings in text file Data Sources are treated as NULL.
A QLingo condition comparing a missing value in the Data Source — that is now treated as NULL — to an empty string, will return a FALSE result.

The functionality of the following features has been modified in this release. The old functionality is still available until further notice, but is no longer developed or supported. In the future versions, these features will be discontinued.

If you send a Job with Tracking enabled but no Touchpoint defined, some Circle-related activities will not function.

The SendMail method of the InteractiveCampaign API class is now deprecated. Use the new SendMail method of the Email Marketing class to send a Triggered Email.

The old method of Web serving is now deprecated. Instead, use the ICP technology.

The mechanism for email preparation for distribution by proofing and processing TXT or HTML document is now deprecated. Instead, use the new "Prepare for Email Distribution" Delivery Provider in order to send an Email Activity to email distribution.

The new data type inference mechanism, introduced in version 6.0 (Data Handling Improvements), is now also available on Macintosh. The inference mechanism determines the data types for columns in data files that do not contain type information, such as Excel and TXT files. The new mechanism makes sure that determining the data type does not corrupt the actual data.

The new XMPBarcode function adds many new barcodes to the XMPie system. In addition to the existing barcodes, users of uCreate Print can now also add barcodes such as ISBN, GS1 barcodes including Data Bar, KIX and many more. The XMPBarcode function can also be used to create barcodes in color and to determine module width for one-dimensional barcodes.

XMPBarcode contains a correction to an old issue, allowing to use the CodePage parameter in a Macintosh environment

Creating bleed areas in print output is now possible through supporting the InDesign bleed feature. uProduce and uCreate Print now respect the bleed definitions used in InDesign and allow documents to be printed using these settings. In addition, elements in the bleed area will be actually displayed. In PDF workflows, bleed information is provided through the PDF Trim Box definition.

Previous versions of uProduce allowed only one imposition or copy operation at a time. The new version allows for better utilization of the system resources by allowing any number of imposition and copy operations to run in parallel.

The new "Monitor" screen in uProduce provides real-time information about the health of the uProduce servers cluster. The system is now monitored for available disk space, database size and running services, and the status information is displayed clearly in the specialized screen. In addition, a simple health icon is shown on the main uProduce menu, to quickly alert the user to severe issues. The system can also notify an administrator about errors and warnings through email.

uProduce can now accept Recipient Lists that do not conform to the defined Plan Schema. When adding a new Data Source to uProduce, you can determine which of its tables should be used as a Recipient List in the Campaign. If the table does not match the Plan Schema, you can map columns in the Data Source table to columns in the Plan schema, in order to allow using this table as a Recipient List.

It is now possible to safely introduce Facebook sharing into your web page. The new method of sharing is available via the Facebook Post to Wall snippet in uCreate XM.

The old Facebook Share feature has been deprecated and should no longer be used.

• Ability to send either fully composed emails or a template. Using an email template allows to considerably increase production speed.

For more details regarding the Email plug-in, see XMPie Email Plug-In SDK Sample Application.pdf.

The old interface for receiving and setting data through Plan named DBIF is now deprecated. Users of this protocol are encouraged to find suitable replacement in the API SDK.

The XMPie family of products supports the recent release of Adobe^® Creative Suite (CS) 6.0. XMPie customers can take full advantage of all the new CS6 features combined with the power of XMPie:

PersonalEffect 6.0.1 Product	Supported Adobe CS6 Product
uCreate™ Print	InDesign^® Desktop
uProduce	InDesign^® Server
uImage^®	Photoshop^® and Illustrator^®
uCreate™ XM	Dreamweaver^®

With the introduction of PersonalEffect 6.0.1, XMPie is simplifying product component names by aligning the names of the InDesign plug-ins for both the desktop and server solutions. Until now, the InDesign plug-ins included with uDirect configurations were either uDirect Standard or uDirect Professional. For PersonalEffect server configurations, the InDesign plug-ins included were either uCreate Print or uCreate Print Designer. Functionally, there were many overlapping capabilities between the uDirect and uCreate plug-ins for InDesign.

Starting from version 6.0.1, the name “uDirect” will refer only to the series of desktop configurations. For PersonalEffect server configurations, uCreate Print is provided as part of the desktop tools offering. Each package, will include one or more software components with the associated functionality as described below:

		Plug-in Capabilities
Product	InDesign Plug-in Name	Link to Data	Link to Plan	Export CPKG	VDP Output	XLIM	Includes
uDirect Designer	uCreate Print Trial	Yes	No	Yes	PDF (up to 5 records)	No
uDirect Classic	uCreate Print Standard	Yes	No	Yes	Yes	No
uDirect Studio	uCreate Print Standard	Yes	No	Yes	Yes	No	uImage, uChart
uDirect Premier	uCreate Print	Yes	Yes	Yes	Yes	Yes	uImage, uChart, uPlan
uCreate Print Designer	uCreate Print Designer	Yes	Yes	Yes	Yes, up to 5 records	Yes
uCreate Print Professional	uCreate Print	Yes	Tes	Yes	Yes	Yes

With PersonalEffect 6.0.1, uProduce, uCreate Print and uPlan include significant improvements to their data access mechanism, which allows the software to correctly identify data types in typeless Data Sources.

Prior to PersonalEffect 6.0.1, using Excel, CSV or TXT files as Data Sources could cause data corruption. Some examples are:

1. ZIP code values with leading zeros were treated as numbers instead of text. Consequently, the significant leading zeros were removed. As a result, barcodes were created incorrectly because they were not generated using the correct number of digits.

2. Columns that contained both numbers and text were treated as numbers. This caused the records containing non-number values to be evaluated as nulls. As a result, text was not written for these records.

3. In most cases, any data that is longer than 255 characters would be truncated.

These issues occurred because the Data Source file did not include a type definition (such as "number"," date", "Boolean" or just plain text). The data type inference mechanism in uCreate Print and uPlan made decisions about the column types in a manner that may have corrupted data.

Version 6.0.16.0 resolves this problem by significantly improving the data type inference mechanism for the Windows environment. As a result, data will no longer be corrupted due to wrong decisions when defining a column's data type. Non-text data types are determined using a safe method ensuring no data is mistakenly removed. For example, both scenarios shown below would result in the correct data type being set.

1. When using Excel files, the new mechanism will assign the same data types as those used by Excel. For example, a value that is considered to be a number in Excel will have the same data type in uCreate Print. The same is valid for dates and Boolean values.

1. Columns that only contain strings of numbers without leading zeros, will be considered as numbers. If some of the rows contain text or leading zeros, the data type would be string. If the data logic requires using such a column as number, use the Qlingo AsNumber function to convert the string to a number.

2. Columns that contain only "0"s and "1"s will be considered as Yes/No data types (Boolean values). If you want to consider them as strings, use the Qlingo function AsString. If you want to use other values for Yes/No types of decisions, use text comparison. For instance, if the Data Source contains "true" or "false" and you want to use them in an “If” statement, simply compare the value to the relevant Boolean string value, namely "true" or "false".

3. Dates are interpreted based on the system regional settings. This is true for separators’ format, the meaning of month and day names, and the order of day/month/year.

Improved uProduce MI Production Stability with Excel, MDB, CSV and TXT Data Files

Starting with uProduce 6.0.1, Excel, CSV and TXT data files are imported into the XMPie database when added to campaigns.

Importing the data files into the XMPie database improves stability when running production of print output or sending email batches in high performance multiple-instances environments.

Note that the new method imposes some limitations in the usage of Excel-specific operators in the plan queries. Essentially, when in uProduce, the Excel-specific operators may not function properly. To solve this issue, use Qlingo equivalents for these functions.

Adapting Plans Created prior to Version 6.0.1 to Match the New Data Handling Mechanism

Plans created in versions prior to 6.0.1 may need to be adapted to match the new data handling mechanism. For more information, refer to Technote 0048 “Porting Plans to PersonalEffect 6.0.1 or higher”:

Tracking performance was significantly improved for batch jobs. The improvements include:

PersonalEffect6.0.1 discontinues its support of Adobe® Creative Suite (CS) 3.0. The supported versions are: Adobe CS4, CS5, CS5.5 and CS6.

QLingo extensions implemented for the Windows platform can and must be compiled using Microsoft Visual Studio 2010.

Starting from version 6.0.1, uCreate Print generates VPS print output that conforms with the VPS 1.5 specifications. As result, uCreate Print is now compatible with all print controllers that support the VPS print format.

XLIM, the XMPie high-speed print production engine, provides several improvements around PDF production workflows, tables, character spacing, and text overflow handling.

PersonalEffect 6.0.1 includes a major change in the mode of production of PDF files using XLIM. PDF files are no longer generated via conversion of Postscript files, but are rather directly created in the PDF format. This technology significantly improves production speed and allows to support more PDF features.

• When working with PDF workflows (PDF or PDF/VT), images in PDF format can be used as Assets for dynamic images.

Note that configuring PDF output options through the Adobe PDF Settings file (*.joboptions) is no longer required and is not relevant for XLIM production. This is the result of the new implementation of XLIM PDF production that does not use a normalizer.

XLIM production now supports InDesign tables. Tables are added to a design either by drawing a table in InDesign or by including a Table ADOR into a page. Either of these options is supported by XLIM production. Most of the InDesign properties for tables, such as border color and alternating patterns are supported.

Kerning and Tracking enable the InDesign user to control spacing between characters.

Kerning is defined in the font file, which provides information about the distance between two particular characters. Tracking is an InDesign feature that enables you to override the default spacing determined by the font for a selected block of text.

Auto Flow allows you to control text overflow by automatically creating pages and text frames to satisfy the text length. As text length changes from one recipient to another, a different number of pages may be created.

In InDesign, the user designates a design page with a text frame as the page to be duplicated for including more text. Then, during print production this page is duplicated per text requirement.

uProduce 6.0.1 requires Windows Server 2008 R2 (64-bit) Standard Edition SP1 or later. It does not support Windows Server 2003.

Email Unsubscribe Enhancements for Exact Target and Exact Target Enhanced Delivery Providers

• A recipient who reports a spam complaint using an ISP that supports Feedback Loop (FBL) will automatically be unsubscribed and marked as an unsubscribed recipient.

• Exact Target unsubscribed recipients are automatically unsubscribed from the XMPie database.

• When using Exact Target Unsubscribe mechanism, unsubscribed recipients will also be registered to XMPie’s unsubscribe database.

• When exporting the Unsubscribe List using the Import/Export Unsubscribe List Utility, both the recipients who unsubscribed via Exact Target and recipients who were unsubscribed due to spam complaint are included in the exported list.

The following performance improvements have been introduced for the ExactTarget delivery provider:

• A new email delivery provider has been added to uProduce: ExactTarget Enhanced. This delivery providersoffers enhanced integration with ExactTarget and, therefore, is optmized to efficiently manage high email volumes. Please contact the email service administration (esjoin@xmpie.com), since a mandatory update of your ExactTarget account is also required in order to enable using these new delivery providers.

• To ensure fast email process time in uProduce and faster data streaming to ExactTarget, emails are sent to ExactTarget as templates whereas the actual composition is performed by ExactTarget. In order to benefit from the new template mechanism, your email batch must be based on a local document. Such document can be created either by the uProduce Email Editor, or by uploading an HTML file, Text file or an HTML Package. This option is only available for the Exact Target Enhanced delivery provider type.

The uProduce Email Editor is an easy way to create HTML and Plain Text documents. These documents are required in order to send uncomposed emails to ExactTarget, thus, ensure the fastest email batch sending time. Two major enhancements to the Email Editor in PersonalEffect 6.0.1 are easy insertion of the View In Browser link and easy upload of static images.

A link to an online version of the email content can be easily added to the email design using the new View In Browser ADOR Object which is accessible from the uProduce Email Editor via the Insert ADOR button.

Emails created with the uProduce HTML editor can contain both static and dynamic images. This version offers the new possibility to add plain, static images.

2. In the Browse window, locate the image that you want to insert. The supportable image file formats are: *.gif, *.jpeg, *.jpg, *.png.

HTML files can now be uploaded and downloaded from uProduce as a ZIP packages, thus, allowing you to easily import and export the email design. The ZIP file includes the HTML file and the images files stored in a separate folder.

When uploading a ZIP file that includes an HTML file and the images folder to uProduce, images that are referenced by the HTML file, will be automatically uploaded and will be available on the internet once the email is sent.

Downloading a ZIP file from uProduce will include the HTML file and a separate folder containing images that are referenced by the HTML file. This applies to images that were uploaded as part of a ZIP package import, or images that were uploaded via the uProduce Email Editor Insert Image function.

In cases when pre-processing of personalized images is not possible, the uImage On Demand snippet allows you to optimize the load time of web pages containing personalized images created on demand.

Typically, it is recommended to pre-process personalized images that are going to be embedded in a web page instead of generating them on demand. For more information on uImage pre-processing, see uImage User Guide.

However, in some cases, pre-processing of personalized images is not possible, as in the case of a Self-Registration procedure, during which you wish to display a personalized image of a newly registered user. In such cases, you want be able to generate a personalized image on the fly and load it to a web page without affecting the loading time of the web page.

Adding a Graphic ADOR Object in an On Demand workflow while using the regular ADOR tagging mechanism in uCreateXM might result in a slow loading time of personalized web pages, depending on the load of the site. Therefore, in order to dissociate the personalized image generation by uImage from the web page load, it is recommended to use the uImage On Demand snippet.

The uImage On Demand snippet operates differently in the following three scenarios:

A web page is loaded separately from the personalized images. The personalized images will be loaded asynchronously, and will be displayed after their generation is completed. Optimized web page loading is essential for keeping your visitors.

If a web page is displayed in JavaScript disabled browsers, the web page will not be completely loaded until a personalized image is generated. The uImage OnDemand optimization will not be applied in this case.

Personalized images embedded in an email are generated while the email is being sent. Once the email recipient opens the email, the image is already generated and ready to be opened.

Starting from PersonalEffect 6.0.1, all the new RURL sites are based on Microsoft .NET framework 4.0 and can include third party DLL files that require .NET 4.0.

RURL sites created prior to the upgrade to PersonalEffect 6.0.1 will continue to run under Microsoft .NET framework 2.0. In order to upgrade existing RURL sites to Microsoft .NET framework 4.0, please refer to AppNote-0041-PersonalEffect6.0_Upgrading RURL Sites to .NET 4.

Upgrading the RURL sites to .NET 4.0 will allow customers to benefit from the following PersonalEffect 6.0.1 functionality:

• Facebook Share (the feature was improved in PersonalEffect 6.0.1, especially around a limitation with MS Outlook 2007/2010).

Working with any external .NET 4.0 DLL files (or any .NET DLL files from versions higher than .NET 2.0)

For a detailed description of compatibility with third party software and hardware, see the “System Requirements” section in the Customer Expectations Document (CED).

Before you install the Adobe InDesign Server (AIS) software, obtain the AIS license key and then check the XMPie BOX site for the AIS CS6.0 installer and updates:

For detailed installation instructions, please refer to the uProduce Installation Guide.

If you are upgrading uProduce from an earlier software version, follow the instructions below.

1. Back up the entire XMPie folder using the Windows backup tool (or any other backup utility).

When upgrading uProduce in systems where uStore exist, follow this procedure to make sure uStore can continue to read assets from uProduce.

4. Go to Settings and set the URL Domain address (for example, pe.abcpriniting.com).

5. On the uStore machine, edit the host file of the machine to map the above address (for example, pe.abcprinting.com) to the internal network IP address.

If the upgrade is from an earlier version than 5.2, uProduce 6.5 requires a migration of the Tracking Database, in order to be compatible with reporting speed improvements introduced in Marketing Console 2.0.

The upgrade procedure is seamless and is performed by running the uProduce installer. If the previous version does not have a Tracking Database that holds data, the procedure is fully automatic and requires no user intervention. However, if the Tracking Database of the earlier version exists with data, an additional step is required. During this step, the Tracking Database will be migrated to a new form, in order to ensure compatibility with Marketing Console version 2.0.

It is highly recommended to create a backup copy of your Tracking Database. This might become useful in case a version downgrade is required in the future or if your migration process fails and needs to be repeated.

If the migration process failed, the Tracking Database may be corrupt and you will have to restore it from the backup using the SQL Server tools. When restoring, make sure that the backup database name is XMPDBTRACKING.

For detailed upgrade instructions, please refer to the uProduce Installation Guide.

Starting from version 6.0.1, XMPie provides the Adobe Photoshop and Illustrator installers for uImage Processing Unit and uImage Server. These installers include the English versions of these applications. If you are using a desktop version of uImage in languages other than English, it is highly recommended to install Adobe Photoshop or Illustrator CS5.1 or higher in order to avoid language compatibility issues between uImage desktop and the corresponding uImage servers.

When Photoshop CS5 or CS 5.1 is installed on the Mac, it can run in two modes: 64 bit (the default mode) and 32 bit. Before installing uImage functionality, you need to change Photoshop's default mode from 64 bit to 32 bit as follows:

The same installer is used to install two production licenses: one for uProduce and another for a uImage Processing Unit. These production licenses may be installed in two ways:

• Distributed configuration — one machine runs uProduce, and another machine performs uImage production.

• Use the uProduce license to install uProduce on a machine that does NOT have Photoshop installed.

n Use the "uImage Production" license to install the uImage Processing Unit (UPU) on another machine, which has Photoshop installed and is dedicated to uImage production.

• Combined configuration — the same machine runs uProduce and performs uImage production.

• Use the uProduce license to install uProduce on a machine that has Photoshop installed.

n Add the uImage Production license through the uProduce Dashboard's License Manager (available when logging in with the "admin" user, going to Settings and choosing License Manager).

1. The uProduce Online Email Editor did not support inserting the XMPieRURL ADOR Object (19827).

1. Date format in uCreate Print for Mac was not locale-sensitive. As a result, the default display of a field that was recognized as Date was not formatted according to the system locale settings (24589).

1. In version 6.0.2, dates were always displayed in DD/MM/YYYY format, independently of the regional settings. In version 6.2.1 for Windows, the date format is now according to the regional settings of the operation system. The date format in Mac is not locale-sensitive.

2. Some floating point values were incorrectly displayed when used as ADOR Object values (23497).

3. Data type inference mechanism was considering locale for dates but not for numbers. This created inconsistency and resulted in numbers being mistakenly identified as dates. This issue is now resolved by forcing the inference mechanism for numbers to take locale into consideration.

4. When using a text Data Source, floating point numbers were sometimes wrongly identified as “date” type, causing unexpected results (23499).

1. In uCreate Print for Mac, when linking a Document to a CSV Data Source, text columns were incorrectly treated as Dates (24387).

2. In uCreate Print for Mac, when linking a Document to a specific CSV Data Source, the following error message was displayed: “One or more Content Object expressions are not compatible with the Data Source. Modify these expressions (and then link to the Data Source) or link to a compatible Data Source” (24329).

3. In uCreate Print for Mac, the Dutch user interface displayed corrupted strings (24497).

1. When trying to generate a ProofSet, production failed with the following error message: “Data source name not found and no default driver specified”.

1. Users that purchased a Volume Pack license were charged for Proof production. In the current version, Proof production below 50 Proofs is free of charge. When more than 50 Proofs are generated, each Proof is charged as in the regular print production.

2. Exporting a Data Source from uProduce to Excel used to corrupt date fields (23498).

3. Upgrading uProduce to 6.0.1 on a system with a click license did not enable production. Even though production clicks were still available, the following error message was displayed: “Your click license has been depleted”(23374).

5. The Checkout/Checkin functionality for Data Sources in uProduce was faulty. As a result, modifying an existing Data Source was impossible (23301).

1. It is now possible to override uCreate XM caching mechanism. This is useful if you wish to retrieve the latest ADOR values when the recipient data was modified outside uCreate XM (for example, directly in the database).

2. In uCreate XM, you could not connect to a Port if the Port’s Account or Campaign name contained non-latin characters (20239).

1. Subscribers List Syncher utility did not work with ET Enhanced delivery provider (24275).

2. When an Email body was created in the uProduce Document Editor using the Text mode, double spaces and other special characters did not show up correctly when the email was sent (18426).

3. Clicking a link to an on-demand generation of a PDF file from an email could result in a failure to generate the PDF.

4. When sending an email batch, if the recipient’s email address was set to an ADOR Object and the value of this ADOR Object had trailing or leading spaces, then sending the email to this person failed (23330).

1. It was not possible to navigate to RURL sites if the Recipient Key contained non-URL conforming characters (23121).

1. When running large print jobs, tracking was sometimes stopped. As a result, any Marketing Console reports that were based on print tracking, such as "Print Population List", showed wrong values (23735).

2. Tracking print outputs through uCreate Print "Link to Port" functionality did not function when the port was set up on a uProduce e-Media configuration (23369).

1. Static resources were incorrectly loaded during XLIM production. This problem occurred in DF, PDF/VT, and Postscript output (24536).

2. XLIM tables implementation did not honor the "Row Height" functionality of cells (23105).

3. The “Once per Frame” feature was always applied to the tables "Repeat Header" and "Repeat Footer" regardless of the user’s choice (23086).

4. When using different line widths in a table, the lines had blanks around the edges (23162)

1. Print Production failed when using "Suppress trailing spaces" with an anchored text box (24302).

2. Proof output did not appear if the uProduce password contained special characters (24473).

4. PDF ouptut files did not contain bleed information in the form of a Trim Box.

5. Graphic ADORs were not populated properly in the following print production case:

n A Document has a text box containing an inline image box and a Text ADOR Object.

n The image box, if one of the images is missing for a certain recipient, was not be populated in any subsequent recipient documents (23106).

6. The PDF print output may have included PDF/VT metadata. This caused issues with several print vendors. This issue was eliminated by removing PDF/VT metadata from non-PDF/VT files.

7. It was not possible to create PDF files for proofing, if the template document was in XLIM format and its design contained a JPG image (23254).

1. The Horizontal Scaling overflow handling policy did not function correctly in Photoshop CS6 (23259).

2. When packing a uImage template in Photoshop, a non-functional default "uImage Optimize" option appeared in the Optimization Path list (23405).

1. There is no option to export a Local Data Source that was originally uploaded as FoxPro to FoxPro (24673).

1. When using uImage, production will fail if uImage horizontal scale is set. It is recommended to set the Optimize attribut to Automatic (24240).

2. uImage DPKG import fails if the file path includes Japanese characters. As a workaround, use Latin characters for file names and paths (24347).

3. When the uImage Server is running on Windows Server 2012, uImage ADOR objects that use an Adobe Illustrator template fail to run. As a workaround, it is possible to install the uImage Processing Unit (UPU) on another operating system (24919).

1. When using Japanese and Australian postal barcodes, the barcode is not sized by default according to the postal office requirements. It is necessary to adjust the size manually. For example, the Australian barcode needs to be stretched 170% horizontal and squeezed to 38% vertical to meet the requirements (24459).

2. When using the XMPbarcode function, human readable text does not appear in PDF\VT (24460).

3. When a XNIP file is imported to InDesign as inline image or table, the rest of the objects may not be positioned correctly (24487).

4. Production of PDF/VT format file with "Draw Page Information" enabled fails. As a workaround, use PostScript output (24586).

5. When using images with EXIF information (image orientation, for example, for images from iPhone), image rotation will not be honored during production even though InDesign will display them correctly). A possible workaround is to use the Require InDesign Rendering option for PDF and Post Scripts formats (24706).

6. When working on a Mac with an ANSI Data Source, accented characters are not display correctly. It is recommended to use a UTF-16 Data Source instead (24812).

1. When using "Merge Output" in production for designs with Graphic elements, production fails (24546).

1. Facebook Share in email does not work. As a workaround, you can place the Facebook Share button in a RURL site (24921).

1. When linking a Document to a Data Source containing a Time column (for example, “11:16:26”), the 31/12/1899 date is erroneously added to the time value (24514).

3. Excel 95 is not supported as a Data Source format for PersonalEffect. Users wishing to connect to Excel 95 data files, should convert them to Excel 1997-2003 XLS format or to later versions (22656).

1. The Bleed functionality does not work properly in an InDesign Document that uses Facing Pages if the "Inside" and "Outside" bleed values are different (23500).

2. Transparency features applied to groups are not maintained in print production.

4. uCreate Print Standard edition does not support the “Number of copies” feature for PDF. This feature allows you to create multiple copies of each record output. The number of copies can either be the same for all recipients, or vary between them per Content Object.

5. Converting a string to a number may fail to do so in a reliable manner if the string defines a number containing more than 15 digits. This behavior is tied to range limits of the underlying data type and to a double-precision floating-point number (20177).

6. In multiple-instance environments, where the data is stored in an Access (MDB) file, running production may fail. This failure occurs when the file is being accessed more times than the allowed number of connections (~20).

Use an alternative File Data Source type (such as CSV), or host the database on a server database (19172).

8. When a design contains an EPS that embeds a font, then the EPS appears distorted in the output - in some cases. This happens when the font embedded in the EPS is also stored in one of these paths:

a. %USERPROFILE%\Application Data\Adobe\InDesign\Version 5.0(or other version)\configuration_17001(or other instance)\CompositeFont

b. %USERPROFILE%\Application Data\Adobe\InDesign Server\Version 5.0(or other version)\configuration_17001
(or other instance)\CompositeFont

c. %ProgramFiles%\Adobe\Adobe InDesign CS3(or Adobe InDesign CS3 Server or other version)\Fonts

• %USERPROFILE% referenced above should be replaced with the root folder for the user that is running InDesign.

t In the case of desktop production (uCreate Print) — item 1 above— this is the root folder of the currently logged in user. A typical example is C:\Documents and Settings\John, where John is the currently logged in user.

t In the case of server production (uProduce) — item 2 above — this is the root folder of the uProduce service user. Use the Services list in Windows to find which user this is. A typical example is C:\Documents and Settings\operator, where operator is the uProduce service user.

n The Application Data folder referenced above is usually a hidden folder. To show it, take the following steps:

iii. Select the View tab, and under the “Hidden files and folders” folder, selected Show hidden files and folders.

Workaround: Check if the font embedded in the EPS is stored in one of these folders. If it is, move it to the Windows Fonts folder, or place it in Program Files\Common Files\Adobe\Fonts (12188).

9. When an InDesign document uses non-Latin characters, creating a print file without embedding fonts (that is, with "embed fonts" unchecked) causes the text to appear corrupted, although the fonts are available to the printer (or to Acrobat Distiller).

This issue has been reported to Adobe and is being investigated. Note that this problem does not occur in XLIM production (14969).

10. On uProduce systems that use InDesign Server CS5, Documents that contain transparency effects (including shadow, blur etc.) sometimes fail to produce Print Output files. This happens only at the early production stages. If you follow up with another production, the new production job does succeed.

If this is the case, the failure might be caused by InDesign CS5 startup issues.

As a workaround, you can use a registry key named InDesignRestartSleep to set uProduce to wait longer for InDesign CS5 to start up properly. This normally resolves all issues. A value of 3 seconds is a good default setting, which does not cause significant production delays (note that this "sleep time" is not applied to all production jobs, only to a very small amount).

b. In the Registry Editor window, under My Computer, go to one of the following folders:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\XMPie\XMPie uProduce Server Object\1.00.000

c. If the InDesignRestartSleep property is not listed, configure it now: Right-click the 1.00.000 folder, select New > String Value from the context menu and set the new property's name to InDesignRestartSleep.

d. Set the InDesignRestartSleep property to the desired sleep time in 1/1000 of a second. For example, to set the value to 3 seconds, double click it to display the Edit String window and set Value Data to 3000.

11. The XMPie Bleed feature creates corrupted output when used in combination with uProduce Global Caching feature (17647).

12. uProduce fails to produce uImage Document Packages (DPKGs) that reference a JavaScript file. This is because uProduce mistakenly searches for the JavaScript file in its location during packaging (the designer's machine), instead of its new location on the uProduce Server.

b. Edit the Plan file and modify the uImage function call, so that it references the uploaded JavaScript file.

1. uImage packaging mechanism does not support text tags that are located in the Smart Objects (24123).

2. After installing a uCreate Print license key that includes uImage, you need to restart InDesign. Until you restart InDesign, a watermark will appear on uImage output files (22318).

3. When exporting CPKGs from uCreate Print referenced uImage DPKGs will not be included (20608).

4. uImage packages that use JavaScript for implementing actions cause production to fail on uProduce. This failure is limited to the packages workflow of uImage. It is still possible to use JavaScript when using the direct templates (PSD files) workflow.

Unpack the uImage package and run production, using the templates directly. You will have to alter the plan definition as well (20251).

5. When creating personalized images from uImage templates that make use of dynamic images, the generated images do not show the dynamic images, even though production completes successfully. The same problem occurs in some XMPie Marketplace "image font" templates, where there is a dynamic image placeholder for each character. In these templates, the personalization (that is., the person's name) does not appear in the image created by uImage.

This problem happens because of a change in uImage behavior in version 4.6. Up to this release, when uImage created a personalized image for a given recipient, any invisible dynamic image layers in which images were placed by uImage, were automatically made visible. As of 4.6, hidden dynamic image layers remain hidden.

• If you are using a Marketplace template, try to download it again from Marketplace. It may have been updated since you last downloaded it. You can download the template again, and get the update for free.

n If you are using your own template, make sure all dynamic image layers (Smart Object layers) are visible in the template. Some of these layers may have content, in which case the content will have to be deleted, otherwise it will appear in all images generated by uImage. To delete the contents of dynamic image layers, follow the steps below to for each dynamic image layer:

i. Open the layer's Smart Object by double clicking the layer's thumbnail in the Layers palette.

v. Close the Smart Object (File -> Close). When prompted whether or not to save the file, save it.

After completing the steps above, save the template file, and try to generate the personalized images again (15394).

6. On some 2008 servers, uImage production may fail. The failure occurs when uImage activates the Photoshop registration dialog, which prevents uImage from operating.

As a workaround, disable the appearance of the Photoshop registration dialog. Proceed as follows:

t Be reminded later — the Photoshop registration dialog might appear again, causing uImage production to fail. In that case, repeat this procedure several times, until you are given the option to not be reminded again. Choose this option to prevent the appearance of the Registration dialog (14669).

7. Copy fitting is not supported for paragraph text (text boxes) in Photoshop. Use point text (text lines) instead (6242, 6260, 13977).

8. uImage does not generate new images that reflect the changes made in its definition.

This occurs in uCreate Print, when the definition of a uImage Content Object is changed in the Rule Editor, Skip Duplicates is checked, images have already been generated for some recipients and Dynamic Print is invoked, or the user browses through recipient records.

This also occurs in uPlan, when the uImage function call is changed, the OPT: parameter is used, images have already been generated for some recipients, and Generate Proof Set is invoked.

To work around this problem and cause uImage to generate new images, proceed as follows:

a. Browse to the uImage Output Folder — in uCreate Print this folder is defined by the Content Object Rule. In uPlan this folder is defined by the ADOR Object definition.

c. Generate new images — in uCreate Print, run Dynamic Print or browse through recipient records. In uPlan, invoke Generate Proof Set.

1. uProduce password may not contain the sequence $$. Otherwise, the RURL wizard will fail to load (23366).

2. To work with FoxPro databses on uProduce, you must install the FoxPro OLEDB driver manually (23905).

3. Exporting a Hosted Data Source to an Excel or Access file fails if the Data Source has more than 256 columns. The following error message is displayed: "Failed to fill exported table by data". To overcome this problem, export the Data Source to a CSV file (19227).

6. When working in uProduce with a Hosted Data Source that has one or more columns whose name contains a dot (.) character, the dot is replaced with a number (#) character. Later, exporting the Hosted Data Source will fail. The failure will also occur for any Data Source in which the number (#) character originally appears in a column name. To overcome this problem, avoid using either dot (.) or number (#) characters in a column name (19744, 19746).

7. Downloading a personalized PDF fails when clicking a link in an email created in uProduce Email Editor. The PDF is created on the server, but an error message appears to the end user, not allowing to download the file.

As a workaround, create the email in uCreate XM. Email documents created in uCreate XM work correctly with the PDF On Demand feature (20325).

For information about Production Units, login to uProduce as an administrator and select Balance from the Navigation Bar.

9. Non-English Data Sources of type CSV cannot use the “Adapt for the Web” feature.

10. When tracking a large amount of ADOR Objects (around 70 or more), then after reaching approximately 70000 events the events are no longer registered.

It is recommended to track a lower number of ADOR Objects. Note that in that case restarting the server will cause the unregistered events to be registered, due to the existence of a fallback mechanism (16125).

11. Uploading a large Campaign, to either a hosted or non-hosted environment, may sometimes fail. When a failure occurs, you will receive the following message:

../Telerik.RadUploadProgressHandler.ashx?RadUrid=c80c8ce6-c5b8-4f29-8525-bf8d297f348e

Please, see the help for more details: RadUpload for ASP.NET Ajax - Configuration - RadUploadProgressHandler."

n Create a new Campaign on uProduce and upload the material components separately (16140).

12. When creating a new Data Source by uploading large file databases (more than ~190MB) with the "Host Data Source" option enabled, the upload may fail. The following error message will appear: "RadUpload Ajax callback error".

n Upload the database file without the "Host Data source" option. After having completed the upload, use the "Host" functionality to complete the hosting of the database.

13. In uProduce, hosting a ZIP file containing an Excel file of a large size fails.
An operation time-out error message is received in the Process step.

14. Creating an Asset Source and adding Assets after a Port has been created does not affect the current RURL, leaving the image un-rendered. Be aware of the following:

a. The image will show correctly for all other recipients RURLs, that were not browsed before adding the ADOR Objects.

b. Even the RURL that causes the problem will work okay on other machines and browsers, who did not use this URL before the Assets have been added.

To view correctly the RURL that causes the problem on the same machine and browser, take the following steps:

b. Switch one of the characters of an existing recipient from uppercase to lowercase or vice versa (17277).

15. The HTML Editor used to create web pages and emails on uProduce does not show Graphic ADOR Object images when in preview mode.

Note that when the page is actually used, that is: viewed in the browser or accessed from a link in an email, the images appear correctly (17480).

16. It is not possible to change the format of XMPieRecipientKey when readapting a Campaign for the web (17938).

17. When installing uProduce, you may receive the following error during the installation process.

Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail (Exception from

Installation will be aborted. Please address this issue and run the installer again."

This issue is normally due to a corrupted version of the installed .NET environment.

18. When installing uProduce on a server where Microsoft Visual Studio 2005 is installed as well, the installation might fail. The following message will be displayed upon failure:

Check online to see if solutions are available from the Microsoft website. If solutions are found, Windows will automatically Display a website that lists steps you can take.

19. uProduce processing of HTML or Text Documents for Email Distribution (Proof or Process) does not work for a Document that was created using the Document Editor in the uProduce Dashboard. Once such Document is proofed or processed, the job will be completed successfully, but the output files will not be available.

This problem occurs since the Document Editor creates Documents with UTF-8 encoding, whereas Proof/Process does not support Unicode-based encoding.

As a workaround, HTML/TXT Documents can be uploaded rather than edited from the Dashboard.

For an "upload" document that does not use Unicode-based encoding (UTF-8 or UTF-16), Proof or Process are working correctly (18544).

20. In uProduce Document Editor, when copying a text block from Microsoft Word to a Plain Text Document (TXT), the formatting is not cleaned. As a result, the text in the Email message body appears with Microsoft Word tags.

As a workaround, when creating a Plain Text Document, copy the text, first, from Microsoft Word to Notepad, and then from Notepad to the uProduce Document Editor (18692).

21. Windows 2008: When uninstalling uProduce Server, the following message is shown: "An error occurred while trying to uninstall XMPie uProduce Server. It may have already been uninstalled. Would you like to remove XMPie uProduce Server from the Programs and Features list?". To uninstall uProduce Server, click the Yes button. Uninstallation will continue normally and should be completed successfully (14680).

22. uProduce version 4.6 provides a connection to the MySQL 5.0 database (through the uProduce Dashboard's Data Source drop-down list, which includes a MySQL 5.0 option). This connection is based on the ODBC provider of MySQL 5.0, which has been found to occasionally throw exceptions.

23. When using old HTML Production (XOD), the Document Edit feature does not work. Use upload instead (14156).

24. On Windows Server 2008 machines, a system error occurs when the system is not used for some time, and the following message is displayed:

"Error in '/XMPieDashboard' Application. Missing username\password in soap header."

If this happens, go to the XMPie Dashboard login page (replace <yourServerName> with the name of your server):

25. When installing uProduce on a Windows Server 2008 machine, the message "IIS component is not installed" appears during the installation.

For instructions on configuring the IIS component, see "Chapter 2: Preparing the uProduce Environment" of the uProduce installation Guide (14113).

26. When installing uProduce on a Windows Server 2008 machine, the installation sometimes fails and the following message is displayed:

"Failed on XMPieInstallerHelpersObject.DeleteVirtualDir: Unknown error (0x80005000)"

To correct this problem, your IIS installation should include the IIS 6 Management Compatibility tool. For instructions on configuring the IIS component, see "Chapter 2: Preparing the uProduce Environment" of the uProduce Installation Guide (14119).

27. When running the XMPie Legacy API setup, error messages are displayed. Clicking the error message's OK button continues the installation and it is completed successfully (14829).

1. In Email production, if the URL throws an exception even for a single recipient, the email production job fails.

To make sure this problem does not occur at production time, use the new Email Preflight feature (15381).

2. When the email content is a RURL web page, and it contains a link to another web page on the same RURL site, the link does not always work. Specifically, it fails when the link does not contain the current Recipient's unique identifier (Recipient Key), that is, the value of the Primary Field for the Recipient.

Include the Recipient Key in any link to the RURL site from the email content web page. For example, instead of linking to: linkedPage.aspx link to: linkedPage.aspx?XMPieRecipientKey=<%# /* Text ADOR */ AdorRec.FieldValue("RecipientID", Container)%>. Note that in this example, the Recipient Key ADOR Object is "RecipientID". You should replace it with the Recipient Key ADOR Object in your Campaign (15456).

3. The Email Preflight Delivery Provider does not provide any warnings if the message does not include ExactTarget fields, including those used to unsubscribe and the sender's physical address. Make sure you include these fields, such as %%member_addr%%, in your email message. For more information, see the uProduce Reference Manual (15703).

1. The “Text Rotation” feature for tables works correctly only for 0 or 180 degrees. For 90 and 270 degrees, the print output is corrupted (22909).

2. The "Repeat Header" and "Repeat Footer" features for tables will always be "Once per Frame" regardless of the user’s choice (23086).

3. When using different widths for lines in a table, the lines would have blanks around the edges (23162).

1. uCreate Print fails to connect to a CSV or TXT file Data Source whose name contains non-Latin characters. The following error message is displayed: “Failed to get table information from data source”.

To overcome this problem, rename the file, so that its name contains Latin characters only (19240).

2. When using a uImage package in a design on uCreate Print, and at the same time making changes to the uImage package (for instance, changing the design in Photoshop, and packing), the changes will not be reflected in the InDesign document.

Close InDesign, reopen it and either run production or browse to a different record. This will update the document to show the modified template (20188).

3. The Carriage Return ("\r") characters of the Text ADOR Objects are replaced with Newlines ("\n") when the Text ADOR Object values are delivered through a Port. InDesign treats Carriage Returns as paragraph ending marks as opposed to Newlines that are handled as simple line ending, with no paragraph ending. As a result, the text alignment and justification settings for the last line of a paragraph will be ignored.

4. Text that is tagged with a Style ADOR Object is lost when converting the Document's Rules to a Plan and later linking to this Plan.

When a "Text with Style" ADOR Object is used in uCreate Print, and later the Document Rules are converted to a Plan using the "Convert Rules to Plan" feature, two ADOR Objects are created:

• A Text ADOR Object — representing the text value of the "Text with Style" ADOR Object. This ADOR Object is named after the "Text with Style" ADOR Object.

n A Style ADOR Object — with the style value of the "Text with Style" ADOR Object. This ADOR Object is named after the "Text with Style" ADOR Object, with an additional, "corrupted" character ("?").

When viewing the Plan in uPlan, both the Text and the Style ADOR Objects appear (and the Style ADOR Object has the "corrupted" name).

However, when using the Plan in uCreate Print, only the Text ADOR Object is available, while the Style ADOR Object is unavailable.

As a result, the "Text with Style" feature is not usable in the workflow of converting the uCreate Print Rules to a Plan.

In uCreate Print, a Text with Style ADOR Object is defined with the name
"A Name". Converting the rules to a Plan results in a Text ADOR Object named "A Name", as well as a Style ADOR Object named "A Name?". Apart from the "corrupted" appearance, this Plan is unusable in uCreate Print, as it does not make the Style ADOR Object available.

• Avoid using Text with Style ADOR in uCreate Print. Instead use two separate ADORs - one Text ADOR and another Style ADOR.

n If Text with Style ADOR is used, then after converting the rules to a plan rename the Style ADOR in uPlan to a proper name. Now the Style ADOR can be used in uCreate Print.

5. When linking to a Data Source containing a field whose name ends with one or more spaces, the following message is displayed:

"One or more Content Object expressions are not compatible with the Data Source. Modify these expressions (and then link to the Data Source) or link to a compatible Data Source".

To avoid this error, remove all spaces from the end of column titles in your Data Source (7825).

6. If a Document created with InDesign CS3 uses a Text File ADOR Object to include Microsoft Word files, then when producing the Document with uCreate Print or uProduce, the text in the Text File ADOR Object is aligned to the right instead of the left.

As a workaround, edit the included Word files and change their "Normal" style to be left-aligned (14548).

7. When a bullet has color and "Suppress Trailing Spaces" is activated, the bullet color is determined by the suppressed line, as opposed to its own color setting (14774).

1. A Plan that does not define a Data Source, and, instead, provides data through a stored procedure using the EXECUTE command, fails to be validated in uPlan. This happens even though the Plan is valid and will be successful in production or generation of a Proof Set (17389).

2. When an ADOR Object named "XMPieRecipientKey" exists in a Plan file, the Plan cannot be viewed in uPlan and the following message is displayed:

"XMPieRecipientKey is a reserved word. Please choose a different name for this ADOR."

To prevent this issue, avoid using the reserved word "XMPieRecipientKey" as an ADOR Object name.

If you already have a Plan file with an ADOR Object named "XMPieRecipientKey", which cannot be edited as described above, recover it by taking the following steps:

b. Open one of the Plan file copies with a text editor (for example, Notepad in Windows).

c. Use the "Search and Replace" functionality to replace all occurrences of "XMPieRecipientKey" with another name, and save the updated Plan file.

3. On Windows Server 2008 and Windows Vista machines, in the Link to Data dialog, clicking Browse... to select an Asset Source using the Browse for Folder dialog allows selecting both folders and ZIP files. Selecting ZIP files causes the Proof Set generation to fail.

1. The ICP functionality is incompatible with the "skip" function in Qlingo (23502).

1. In uChart, text display in Advanced Options may sometimes be incorrect.
For example, writing the command "/LeftScaleFormat (£999,990)" will not display the Pound (£) symbol correctly.

1. uProduce installation fails with the following error message: "Failed on XMPieInstallerHelpersObject.CreateScheduleTask: ERROR: A specified logon session does not exist. It may already have been terminated." (19598).

This may happen if the Windows security option is set not to allow storage of credentials or .NET passports for network authentication.

a. Open the Start menu, type secpol.msc in the search line and press Enter. This will open the Local Security Settings Manager.

b. In the Security Settings tree, select Local Policies and then choose Security Options in the right pane.

c. Search for the Network Access: Do not allow storage of credentials or .NET passwords for network authentication option and double-click it. A Properties window will open allowing you to change the configuration.

2. New versions of Norton Antivirus may mistakenly identify uPlan and Proof Set Viewer as viruses and block these applications. When either finishing the uPlan installation or when trying to run the application, Norton Antivirus may notify you that a "Suspicious.Cloud" threat has been encountered and automatically quarantine the uPlan or Proof Set Viewer application.

Neither uPlan nor Proof Set Viewer are viruses, nor do they contain malicious code. The "Suspicious.Cloud" threat detection is known to falsely identify possible threats from safe applications.

To workaround this issue, you can take uPlan and/or Proof Set Viewer out of quarantine. Other possible workarounds are described in Symantec's web page, detailing issues concerning the "Suspicious.Cloud" threat detection:

n The public IP address of the RURL Wizard server (defined as uProduce External Address in the uProduce "Path Locator") is not accessible from the LAN.

a. If: the uProduce External Address in the Path Locator is configured with the RURL Wizard server's Public IP

b. If: the uProduce External Address in the Path Locator is configured with the uProduce internal LAN address

t An email with Assets, which uses a uProduce local Document (uProduce HTML/TXT Editor or uploaded Document) or a URL Document that points to an ICP page that is configured without a friendly URL, will fail to show the Assets.

t An email Unsubscribe link that uses the "generic Unsubscribe page" as the "Unsubscribe web address" will not function.

To resolve this issue, install uStore version 4.1 or higher, and verify that the uProduce External Path Locator Address is configured with the RURL Wizard server's Public IP.

1. On Demand emails that are triggered by the uCreate XM Self-Registration mechanism are not sent out when you use ExactTarget or ExactTarget Enhanced delivery providers (22312).

2. When you create or edit a Facebook Share button with Adobe Dreamweaver CS6 or uCreateXM, the button is not properly displayed on the RURL page (22968).

4. In uCreate XM it is not possible to have more than a single instance of a QR code snippet on a web page (18660).

5. When modifying a website that was created using the Email Template, and changing the Page Settings, the Document Name containing spaces will show a Parameter name containing invalid characters error.

6. When editing an Unsubscribe Email site created from the Unsubscribe Email Template, the preview will not work.

To preview the page, perform "test send" on the real email and click Unsubscribe from within the email. Remember to re-subscribe again, or you will no longer receive emails (18684).

7. When double-clicking the QR Code snippet in uCreate XM, the QR Code will not work in runtime (18628).

8. The Response.Redirect function will not work when using Proxy. Instead of using this method, use uCreateXMCtrls.uCreateXMCommonCSharp.XMP_Redirect (15229).

9. Emails that fail to be sent from a uCreate XM website are not reported by uProduce (13870).

10. On Windows, after installing uCreate XM on Adobe CS4, the Email, Tracking and Insert buttons do not respond to clicks.

To fix this problem, go to the Control Panel, double click Add or Remove Programs, select XMPie uCreate XM, click the Change button, select Repair and then click Next (13974).

11. When upgrading uCreate XM after upgrading Adobe Dreamweaver CS3 to CS4, the uCreate XM installation fails.

You can integrate 3rd party mapping services, such as Google Maps, with custom code (22278).

2. When you use the Email Unsubscribe RURL Template to create a RURL site for a Custom Unsubscribe page, the RURL site’s sample link does not work in the RURL Wizard.

To test the RURL site, you need to send an email that contains the Unsubscribe link and click the link from the received email.

3. When creating a personalized Custom Unsubscribe website using the Email Unsubscribe RURL Template, the Sample Link of this site in the RURL Wizard is not working.

In order to test such site, you need to send an email and click the Unsubscribe link from the received email (18595).

4. It may be impossible to navigate to RURL sites if the Recipient Key contains non-URL conforming characters (23121).

5. When upgrading the RURL Wizard from version 4.6.3 to version 5.0, the URL Domain setting is not saved. After the upgrade, go to the RURL Wizard Settings page and re-enter the value of the URL Domain in the URL Domain field (17606).

6. The RURL Wizard does not allow creating a website with the name of a deleted port.

7. In the URL step of the RURL Wizard, if the URL address is left with the default Friendly value, then the RURL Wizard crashes. Note that the Friendly value must be replaced with the real URL address (18672).

8. After upgrading from PersonalEffect 4.6.3 to PersonalEffect 5.0, the RURL Domain field in the RURL Wizard Settings is reset to None.

The administrator must login to the RURL Wizard and set the RURL Domain field to the value that was previously defined in version 4.6.3 (18005).

9. When a user's uProduce username and/or password are changed, the personalized websites created by this user stop working

As a workaround, update the site to work with the new user/password by connecting to the RURL Wizard with the new credentials and editing the site:

In the RURL Wizard's Sites page, go to the Actions section and click Edit. When editing the site, the wizard follows the same pages as when creating the site, except that your previous selections are already displayed as default settings. Click Next all the way through and finally click the Finish button (without making any changes).

10. RURL Wizard and RURL Websites can only exist on an IIS default website. The RURL Wizard installs the wizard on the IIS default website. All subsequent sites the Wizard creates are also created in the IIS default website (15460).

11. If the domain used to create the site is not registered on an Internet DNS, the last step of the RURL Wizard shows an error instead of a link.

To overcome this problem, purchase the domain and make sure that it is both accessible over the Internet and mapped to the external IP address of the RURL Wizard machine (14543).

12. In the URL page of the RURL Wizard, when configuring a friendly URL, the name of the Virtual Folder cannot begin with a number.

To continue, give the Virtual Folder a name that does not begin with a number (15244).

13. In GURL Templates, when using Graphic ADOR Objects as placeholders on the GURLSelfRegistration.aspx page, this page returns an error.

To avoid this problem, do not use Graphic ADOR Objects if you intend to use the GURLSelfRegistration.aspx page. Alternatively, edit this page in Dreamweaver and replace the dynamic content with static content (15250).

14. Some RURL Templates throw an exception instead of going to the specified template error page.

To fix this problem, define the required error page for the page using Dreamweaver (15269).

15. It is possible to create two sites with the same name: one using RURL Wizard and the other using uStore.

16. On Mac machines, the Site Definition File (STE) created by the RURL Wizard does not work as created. When trying to connect to uProduce, the error message "FTP error 0" is displayed.

To correct this error, edit the STE by going to Site > Manage Sites > Edit, and change all instances of the RURL Wizard's host name with its IP address (13911).

17. In the RURL Wizard's Settings page, when FTP is selected as the connection method, testing the connection by pressing the Test button sometimes fails, even when the connection is defined correctly.

To correctly test the FTP connection definitions, create a website with the RURL Wizard, and try to use its Site Definition File (STE) with Adobe Dreamweaver (13914).

18. On the Web Server machine, the user must manually install Helicon Tech's ISAPI_Rewrite 3.0. For details, see the uProduce Installation Guide (14111).

1. The “Email link tracking” functionality described in uProduce Reference Manual is currently not supported and will be implemented in the future.

2. When an email blast job contains recipients with non-unique email addresses, the tracking information for these recipients is not correct.

Make sure that each recipient has a unique email address before you send an email blast job (21824).

3. When you set up a uCreate XM Email page with content type Text, the resulting email body contains unnecessary HTML tags.

Instead of using uCreate XM, create the email body using uProduce HTML and Text Editor (18680).

4. When using XMPie Email Service or Exact Target Delivery provider for sending emails, it is not possible to define a From email address that contains "noreply@" or "no-replay@" (19147).

5. When an email based on an ASPX URL Email Document is viewed in an Internet browser, the ADOR Objects representing the Unsubscribe link and the Sender’s Business Details are not replaced by the real values. The ADOR Object names are displayed instead (19488).

6. Sending an Email Activity to multiple recipients with a constant email address results in tracking events associated with a single recipient.

In order to test emails and email tracking events correctly, send the Email Activity to recipients with a different email address (19918).

7. When clicking the Unsubscribe link from an email, it might take a long time for the Unsubscribe Confirmation page to load. This happens only when the Unsubscribe mechanism is starting its service after not being used for more than 720 minutes (usually it will happen only when the first recipient is trying to unsubscribe from an email blast job or when testing the Email Campaign)(19005).

8. Email Preflight fails for an HTML document that was created using the uProduce Document Editor in PersonalEffect version 4.6.3 or below.

As a workaround, check out the HTML Document and check it in using the Edit option in the Document Editor (20159).

9. When sending emails with an Unsubscribe link, make sure that the Unsubscribe link is not an IP address but rather a Domain Name. Otherwise, clients, such as Outlook, might show a phishing warning (18371).

10. The Unsubscribe Email Template cannot be used with Image ADOR Objects. Static images, such as logos and banners, will work (18674).

11. The Email Template does not create an Email Activity for uProduce Accounts that were created prior to PersonalEffect 5.0.

As a workaround, open uProduce Account Settings for editing, and click Save without modifying any field (17772).

1. In a website accessible via the HTTPS protocol, images that are used in the context of a Graphic ADOR and are hosted on a uProduce Asset Source will not appear. uProduce Asset resolving for web pages supports only HTTP protocol.

Instead of using the uProduce Asset resolving mechanism, you may choose to place the images in the website itself, thus, determining the image URL directly from the ADOR Object value (23860).

1. It is not possible to track the landing of the recipients' friends on the Shared Page (for example, a Self-registration page). As a result, the response of the recipients' friends from the social media cannot be analyzed.

2. In each web page or email, it is possible to add only a single Share button for each social network (19812).

3. A user clicking the Share button while not being logged into Facebook will be first prompted to log into Facebook. Logging in will open the expected Share page. In some cases, after submitting the login information, a Facebook Error page will be displayed instead of the Share page. This is due to a general problem with the Facebook Share button.

As a workaround, the user can close the Error window and press the Share button again. This time, the Share window will open while the user is already logged into Facebook and the user will be able to complete the share process (20291).

1. In a cluster configuration, when the SQL Server TCP/IP Port is defined as Static instead of Dynamic, the system encounters critical issues, such as tracking events are not written to the Tracking database.

1. Customers must refrain from tracking campaigns with non-unique recipient keys. Otherwise, the availability of data for reporting will be considerably delayed, and the respective data will be useless for reporting.