Recently I have been developing some applications and have noticed some strange bugs in Kinetic Application Studio.
If the widget you add automatically gets an arrow, you delete the arrow and add it to a new widget there is no arrow just a line between the two widgets not allowing you to save the application. You then have the delete all the widgets and not have the arrow automatically connect to save your work.
Sometimes my logic would not make any sense when previewing the application. Using the developer tools it just made no sense seeing it go through the logic. Example: a row would hit a condition statement and would be false. It would go through the false logic and then go through some of the true logic…Refreshing the page after saving would result in Application Studio reorganizing my widgets to look nicer. Great!..Oh wait they added an arrow to my widgets resulting in what I was seeing in the application preview. I have also had experiences with Application studio deleting my logic resulting to me losing hours of work. This was not a result in me not saving my work for the record.
My Logic:
Application Studios Revised Logic Upon Refresh:
Anyone else had any of these experiences? I am working in the browser on 2023.2.16. I reported this to Epicor but they do not have any answers for me yet.
I’ve seen this kind of garbage, too
What I’ve experienced usually involves trying to change branching logic (True/False or OnSuccess, etc.) - so I started putting a console write on all of those branches so that I can (more) freely edit the arrows.
Basically, if I do have to edit one of those branches, I delete, save, close Application Studio, re-open, and continue … tedious
It seems like it sometimes loses the session, but keeps “working” … so it looks like everything is going well, but all the saves are going nowhere. I always look for the blue “loading” line at the top of the page after I hit save. If it doesn’t show that line, it’s not saving - close and re-open to see what is actually saved. The longer I’m working/messing around with logic without running a preview, the higher the chance of this happening
Great! Hopefully this fixes the changing of logic/deleting logic bug as well. I will do some testing and see if it does or not.
Only took us 3-4 years to get this fixed? I am sure I was not the only one who had reported this issue but I did send support multiple videos and detailed instructions on replicating this bug.
I have same problem in 2023.2.17. Most programmers will always need to go back in and change logic flows. Lost a lot of time re-creating the event flows. Hoping in future versions that the product will be tested more before releasing for GA.
I can confirm this is still not fixed in the latest version, experiencing same buggy behaviour. Workflow completely changes and lives its own live after save. Generally, this seems to happen for bigger workflows with conditional nodes.
Workaround: Use event-next to chain condition events vs. building complicated condition trees in a single event. keep it to a minimum number of branches in a single event (i don’t go above 2)
Correct, thats what I do also. Not pretty though, ending up with dozens of different events which could easily be placed into one workflow. I miss old c# dev days with if/else conditions…
Sometimes I move my entire (or as much as I can) workflow to a function and do it in c# instead. Low code is nice as it makes complicated things easy but then it makes easy things time consuming. I have not had any recent issues relating to this problem but also my development has been not as intensive. I have tested 2025.2 and it is a bit more buggy as well as bugs out BPMs/BAQs development screens
I shove as much as possible into functions too. It saves my hair from greying by another day or two.
2025.2.10 (or .8 or .9, i dont remember which and it was not in the release notes, of course) came with a significant improvement to any code editors in kinetic that work with C# (like BPM editor attached to Method Directives and within BAQ Advanced BPM Editor) - I’ve been doing all my coding in one of my non prods that is on that version since it released due to that.
Most of the time its better to do it a server function anyway, but sometimes it makes it really chatty on the network do some some kind of formatting or processing that would be fine on the client if application studio wasn’t so prone to inducing spontaneous suffering
May have to do a later release as I think our minor is .6 or .7. I will open the C# screen and it is just completely white and I have to drag down the box, close the editor, then reopen it.
