You have already found a quick fix, but I can recommend two other options.
Have you seen Event enrichment option for message center?
This step is only available if you have purchased the enrichment option: please check your license agreement.
To do this:
2 Deploy it on each existing execution instance,
The file must contain the methods for which a signature is defined in the library. After execution, the
This additional data can be available in an external database. Make sure the execution instances can access it using SOAP calls.
Option 2: Raise a ticket with neolane support and ask them if you can have some custom platform options in execution instance and you can put your data in executions instance and get this data in delivery.
Option 3: create a custom web service in your control instance which will act as routing service and call message center with rteventData+Your additional data.
Use second Event collection method
Events generated by the information system can be collected by Neolane Message Center using two modes:
Default calls to SOAP methods let you push events in Neolane Message Center second mode creating a workflow lets you recover events by importing files or via an SQL gateway.
it depends on your business case, i.e., what kind of data you have.
Hi, thanks for your answers. I have used Option1 and it works great for us. The only problem that I have is that it looks like AC cache the custom js router, and when I do updates on it I need to wait some hours before it starts to work, do you know a workaround so AC uses the new version faster?