[BUG] Mirth 4.5.0 - Transformer steps are overwriten (code is lost and overwritten by other step's code) when moved around

[ppazos]

Describe the bug

I have a source transformer with about 20 steps. I have mappers, JS, message builders and iterators, all mixed.

If I add a new step, move up or down another step and then save, some steps lose their original code and it's overwritten with other steps code. This is a major issue and it happens a couple of times now in production, and losing code is not cool.

IMO something in the save process is mixing the orders of the steps and not updating the code correctly.

To Reproduce

I don't have an exact way of reproducing, it just happen a couple of times, and it's when editing the transformer steps when some steps are moved up or down.

Expected behavior

It should save each step's code without overwriting other steps.

Actual behavior

Some steps are overwritten with other step's code.

Screenshots

I'll try to create a video locally, I can't share this because it's code for a client.

Environment (please complete the following information):

• Linux Ubuntu
• OpenJDK 11
• Connect Version 4.5.0

Workaround(s)

None, I need to redo my code.

[jonbartels]

Pablo and I talked in Slack. Notes:

When you try to reproduce this, can you please make sure to use “show Java Console” YES in the launcher and capture the console output please? - Pablo will capture this

Did you rule out things like other users modifying the same channel at the same time? - Pablo was the only user

What I’m guessing is that Mirth edits and manages things in memory in the admin client. It only talks to the server when you save (not exactly but close). So if the client UI and the in-memory data gets corrupted then the save is corrupted.

[ppazos]

Last week I got another issue in prod: the iterator variables emptied by themselves, and, in this case, without even moving transformer steps up or down, I we just updating one step then on save the administrator complained about the transformer not being valid, double checking all the steps, an iterator step was emptied and I needed to restore the values from a backup (luckily I had a backup). So there is something going on with the transformers in Mirth 4.5.0 when there are many of them (I might have 25 steps in the source connector).