CR #417509
Description: When the name of an XSD file used in a transformation service is changed, the .map, .rules, .gem, and the svc_trans_rules.gem files fail to update and do not allow you to package the service.
Workaround: Open the transformation service, and make a minor change to the map, such as moving one of the content models on the Map page. Save the minor change to restore the transformation service to a consistent state.
CR #401702
Description: When you use the Dialog Service Test wizard to test a transformation service that calls the getTimeZoneID function, the Dialog Service Test wizard may send the incorrect time zone to the getTimeZoneID function, resulting in an incorrect value of “0000” every time you call the getTimeZoneID function.
Workaround: Instead of using the Dialog Service Test wizard to test a transformation service that calls the getTimeZoneID function, use the SOAP Request/Response Service Test wizard or the Create Web Service Client wizard.
CR #423065
Description: When defining a transformation rule in a Java Transformation Service using the expression editor, a problem arises when comparing hexBinary values.
Workaround: Convert each hexBinary value to a string.
Comparing hexBinary values in a Java transformation
service
Convert each hexBinary value to a string.
The result is a string of hexBinary characters (0-f).
Compare the results to another string.
CR #429723
Description: After rules are defined in a conditional logic function, error messages appear in the Problems View of the Service Development perspective, and the corresponding transformation service cannot be deployed.
Workaround: Delete all if-then links,
and then redraw the links.
CR #430935
Description: A Java Transformation does not compile if it contains a literal in the map.
Workaround: Use expression constants instead of map literals.
Using expression constants instead of map literals
Delete the literal, and map a source field to the target field.
In the transformation rule, delete the source field.
Add to the rule a constant with a type matching the datatype of the target field.
Set the value of the constant to the desired value.
Add a number or string function to the rule:
Use a string function for String, Binary, Custom Date & Time, Date & Time, Date, and Time data types.
Use a number function for all other data types.
Connect the constant to the string or number function.
Connect the string or number function to the target field.
