BPM Best Practice for Start Points - One complex, or multiple simple? What is your opinion?

Hello Bud,

Thank you for your question.

I would like to touch some theory - specifically, the generic meaning of the "starting point" of the business process; for doing that it is suggested to temporary put out of the equation the particular engine that implements BPM in the particular software

I ask myself, whether speaking of the "starting point" of the process we usually mean a) the object (or set of objects) involved and b) the set of conditions or criteria which are so important in some meaning, so that if those are met for the object(s) we treat the situation as fairly important - at least important enough for triggering the sequence of actions (process/procedure/workflow - whatever terminology is prefered)

If to agree with this general meaning, let us note that the "key fact" or, in other words, "logical key event" is identified in a very moment when logical criteria are met for the target object

That is a real trigger.

I have to admit, that sayin the "logical key event" in the meaning of a combination of logical criteria, I also do oppose it to the "physical event" - the primitive of the field value change logged or linkage logged.

So, the "logical event" is the starting point of the process run

Usually, the logical key event - as a conclusion about criteria met - is also a subject of interest for CRM users and a must-be subject for the reports - remember the statistics - about 48% or companies don't get important info from their CRMs - maybe they just cannot be aware on time about key events happened as well as key events expected, but NOT happened- because that is pretty the situation not to miss in CRM (otherwise why it deserves an automated workflow to run, isn't it?)

If to use the criteria of the logical key event happened for collecting events as the records of the Object's Timeline, then you won't need to bother about complex criteria for starting the BPM anymore - all you would need is to fire the workflow on "logical key event" of particular type is recorded on the timeline

Again, because the logical key event identified is the real trigger and starting point for all the workflows, also in the CRMs

The Timeline and Key events collection in Sugar is provided with TImeLine Viewer addon
The criteria for the logical key events collection could be configured with Logic Builder flowcharts.

I hope this could help to choose the approach

Hello Bud,

Thank you for your question.

I would like to touch some theory - specifically, the generic meaning of the "starting point" of the business process; for doing that it is suggested to temporary put out of the equation the particular engine that implements BPM in the particular software

I ask myself, whether speaking of the "starting point" of the process we usually mean a) the object (or set of objects) involved and b) the set of conditions or criteria which are so important in some meaning, so that if those are met for the object(s) we treat the situation as fairly important - at least important enough for triggering the sequence of actions (process/procedure/workflow - whatever terminology is prefered)

If to agree with this general meaning, let us note that the "key fact" or, in other words, "logical key event" is identified in a very moment when logical criteria are met for the target object

That is a real trigger.

I have to admit, that sayin the "logical key event" in the meaning of a combination of logical criteria, I also do oppose it to the "physical event" - the primitive of the field value change logged or linkage logged.

So, the "logical event" is the starting point of the process run

Usually, the logical key event - as a conclusion about criteria met - is also a subject of interest for CRM users and a must-be subject for the reports - remember the statistics - about 48% or companies don't get important info from their CRMs - maybe they just cannot be aware on time about key events happened as well as key events expected, but NOT happened- because that is pretty the situation not to miss in CRM (otherwise why it deserves an automated workflow to run, isn't it?)

If to use the criteria of the logical key event happened for collecting events as the records of the Object's Timeline, then you won't need to bother about complex criteria for starting the BPM anymore - all you would need is to fire the workflow on "logical key event" of particular type is recorded on the timeline

Again, because the logical key event identified is the real trigger and starting point for all the workflows, also in the CRMs

The Timeline and Key events collection in Sugar is provided with TImeLine Viewer addon
The criteria for the logical key events collection could be configured with Logic Builder flowcharts.

I hope this could help to choose the approach