Whenever an action or trigger instance is initialized, the configuration data, serialized and encoded as a byte array, is deserialized into the JUI page used to store configuration options and presented to the user. When the configuration data is still in the legacy format, this will cause an exception during deserialization and the configuration will be defaulted to a blank JUI page. To modify this process so legacy data can be properly read from the data the ConvertLegacyData method needs to be overridden in your implementation of the AbstractActionType Class or AbstractTriggerType Class.
Override the ConvertLegacyData method
Override this method and include the necessary code to deserialize your custom legacy data. If you used the data serialization methods defined in the legacy API, you can take advantage of the TrigActInfo.DeserializeLegacyData(TOutObject) Method to deserialize your legacy data. For example: