I'd love to be able to setup some BPT processes on Delete or Update actions, instead of just Create. (I could create a seperate entiy just for this BPT in which I only create something, but that means I have to edit all kinds of wrappers to include this extra create)

This way I can more easily create logs, or inform external systems about the removal of an entity without letting the user wait for it.

Hi Joey,

You can actually use Launch on Update in BPT: try the conditional start.

This is not possible in BPT Light (there is another discussion on that) and i don't think its possible on Delete either.

So i think its a good idea, but now you know you can already implement the Launch on Update ;)

There should be possibility to launch a process on entity update, not just on create as it is now.

What is actually the reason that this is not available? This uses database trigger, which supports both cases, isn't it?

Some can say that there are workarounds for this. To summarize advices which I read or found myself:

1. Launch a process on entity's OnCreate and have conditional start inside. This is not very good option for a table which can have millions of records - I wouldn't want to have millions of processes hanging infinitely. Sometimes it can be that there is clear condition to finish such process, but in my practice more often then not there is none, and such process will hang forever.

2. Very interesting solution in this video https://www.outsystems.com/nextstep/2019/?wchannelid=lxt52ix89e&wmediaid=zow8f0qc8q - unfortunately doesn't work because there is no way to get the ID of the updated record. Or am I missing something?

3. Launch a process from inside the Entity_Update custom action, which will be the only update entry point. This just goes against architectural best practices. A process is higher level then the entity update action, and often it is separate module.

4. Similar to previous, but Create another "event" entity and insert into it when update happens. And then consumers can use this as process launch event. And then ideally delete the records to keep it clean. This seems to be the best option, and which we are using, but it is still an extra workaround of what should not be an issue in the first place.

Hi Igor,

The solution in the video ("singleton" process) should work.

If you make the conditional start trigger on the update of "SomeBPTEntity" the conditional start node will have (as an output) the Id of the row in SomeBPTEntity that caused that launch. You can then use it in the subsequent logic (see below - I can do things inside that Automatic Activity below)

Cheers,

Miguel

Miguel,

Thanks a lot for this hint! I was able to make it work after some playing around.

The problem was I have set Id to Null() to get rid of the warning shown. In this case the output doesn't appear. It took me some time to understand this.

But if I leave it empty - it does appear, however the warning is annoying, and my natural behavior was to "fix" it.

Unfortunately I am not able to edit the idea to correct it in that part.

I have always been VERY afraid of conditional start over performance concerns.

J.Ja