Introduction

In FP5 and earlier versions, field personalizations cannot be fully exchanged between Worktop and Web UI. This issue is caused by a different storage format of the personalizations between Worktop and Web UI. From FP6 the field personalizations are stored equally.

In FP5 and earlier versions, the identification of a personalized field during the personalization process is based on the field name and the sequence number linked to this field. When the definition of the form is changed, the sequence of a field might be changed. When processing the personalization, the field can no longer be found and the personalization is lost. To solve these issues and make a field personalization identifiable, FP6 links a Universally Unique Identifier (UUID) to each form field.

From FP6, in combination with at least the 8.5.1 version of the Dynamic Form Editor (DFE), field personalizations are stored with a UUID.

A conversion is required for:

• Dynamic form fields (ttadv308.zb_uuid)
• Field personalizations (ttadv900.zb_uuid)

The FP6 release is delivered with all the converted forms. Based on the converted standard forms, customized forms must be converted too. In the Compare Package VRC’s (ttadv6450m000) session, an Ignore UUID of form field option is added to exclude form changes caused by the UUID conversion.

The Procedure section describes the steps to take for the customized forms and is applicable only for VRCs with customized components (sessions/forms).