The restoring of a previous version (version management) of a CALL object of type EMAIL, introduces a corruption of the the field OH_SUBTYPE in the OH table.
Actually the correct value in OH_SUBTYPE is '3' for that kind of object. After the restoring the value is change to '3|E-mail' which is not correct.
If this object is then exported to XML and imported back into an AE system a warning will be issued and the action may be skipped
Starting import of object 'UC0.CALL.UC4OBP' Warning: The object type (CALL(3) of object (E-mail)) is not equal to the original object type (UC0.CALL.UC4OBP)! this object will be skipped.
Observed behavior :
This is where '3|E-mail' appears in the database under OH.OH_SUBTYPE.
If this object is exported to XML :
The XPATH CALL/ATTR_CALL/TYPE will be "3|E-mail|E-mail" instead of "3|E-mail"
The XPATH CALL/HEADER/OH_SUBTYPE will be "3|E-mail" instead of "3"
Release : 12.3.6 Component : AUTOMATION ENGINE
This is a bug of the Automation Engine component
Resolution: A problem has been fixed where restoring a CALL object from version management created an invalid sub type entry for this object in the database.
If the object is exported the sub type was "3|E-mail" instead of "3". This caused an error on import.
This bug is fixed in version 12.3.9 and in version 21.0.4 of the Automation Engine. Both releases are now available for download.