Web Settings migration issues and considerations

In WebFacing projects the input field .value is treated as initial value, and is not quoted. This is specified in config\conversion.rules:

<WebSetting>
<ValueMigration option="INITIALVALUE"></ValueMigration>
<INITIALVALUETransform type="unquoted"></INITIALVALUETransform>
</WebSetting>

Tweaking these settings and reconverting will lead to different results.

When a V5.1.2.2 project is migrated to V7.1, the following values will be specified in config\conversion.rules:

<WebSetting>
<ValueMigration option="CURRENTVALUE"></ValueMigration>
<INITIALVALUETransform type="quoted"></INITIALVALUETransform>
</WebSetting>

In the migrated V5.1.2.2 project, .value for input fields will be the current value, and initial value will be quoted, the same as the original V5.1.2.2 project.

Projects migrated from V5.1.2.1 will have the same settings as V7.1 projects. This means that .value for input fields will be initial value and will be unquoted, the same as the original V5.1.2.1 and earlier projects.

System Screen Migration from Versions before V6.0.1

All WebFacing projects migrated from versions before 6.0.1 will have the files added to support dynamic data stream transformation. This applies to projects created with either WebSphere® Development Studio Client Standard Edition or Advanced Edition.


Feedback