As of 2024.1.5 You Can Add Components to an Existing Event Flow in App Studio!🎊

HUZZAH!!!

Happy Birthday Yes GIF

3 Likes

Base events are still locked…

What do you mean by “existing event flow”?

Gary Coleman GIFs | Tenor

8 Likes

Pretty sure you could do that before.

It’s letting me do it in my current Live 2023.2 environment.

1 Like

But it would not work.

When you do that in Prod, does the connector have an arrow at the end of it?

1 Like

So it LOOKED wired up, but wouldn’t function as a true/false?

1 Like

image

Yes, there are a few posts about it on here. It looked like you could do it, but it did not work. It just happened to me a week or two ago. Thought I would give it a whirl in the updated environment and…

surprise magic GIF by Paul McCartney

2 Likes

wow

Sweet! In either case… I didn’t KNOW you could change the properties of a connector… so, very much appreciate the tip! And also glad you went through the frustration of it not working before, and not me! :rofl:

2 Likes

I guess I can stop writing all my apps in raw json then.

5 Likes

I just tested a condition in 2023.2. Deleted the connectors, manually added them back in (no arrows this time, even though there was one last time)… but the logic still worked. Previewed and the event would fire up the true and/or false branch.

Now… in this case, I didn’t add a condition mid-stream. I just deleted and manually added the connectors back in. So, maybe the “logic” was kinda cached in the background?? :man_shrugging:

I refreshed my screen and reopened my event and the arrows were now there.

Not sure… I can’t recreate what the person in your above thread was experiencing. Odd.

1 Like

Just figured out there is a little hiccup with this though. I added in the condition and set false to event-complete and after saving and going back in, the system added a connection off of the event-complete.
image

If you just delete the connection, save, and close out, it will be back again the next time you open it. You need to delete and reconnect all up until, in my case, I came across another condition.

3 Likes

@klincecum , still better than having to RE-DO the whole event.

I’m also wondering if they snuck it in retroactively for SaaS customers. :thinking:

1 Like

OMG About time this has been so infuriating

3 Likes

half is better than nothing I guess

Less than half. You had to delete the whole event and start from scratch before this. I think @hmwillett came up with a work around, but it was only serviceable.

1 Like

It involved rubbing your belly and patting someone else’s head at the same-time.

4 Likes

I’m just bitter.

I have quite a bit of technical debt that will fall about 80% on me, and this stuff is very frustrating.

Thank god 90% or more of my work is in the backend.