Hi Ralph,
Yes, you are right at all! Thank you very much!!!

But please let me ask another question here because it concerns to the same subject area. I believe it could be useful for others find the answers in the same topic.

Yes, follow-up action is normally started in result of saving operation initiated by REST request. But is there any way to define in RTC plug-in how the follow-up action was initiated - by a user or a single REST API request?

But if you believe that this is a matter of another topic, I can create a new answer without a problem!

Dmitry,

you have no control about how an advisor or participant is called, at least I don't know how. It gets called by the server (or client) on the triggering event and runs. What you can do is e.g. with the Java API at least, is to provide additional parameter (see https://rsjazz.wordpress.com/2012/07/31/rtc-update-parent-duration-estimation-and-effort-participant/) that the participant can use to decide if it needs to run. This is also used internally to create CLM back links. I am not sure if you can add additional parameters when using the REST API.

Otherwise the operation has to decide on the other given data if it needs to run or not.