Triggers | Community Creatio

Question

17:15 Nov 11, 2024

Hi Community!

We are trying to find an elegant way of preventing the execution of business processes from create, update and delete elements within other business processes.

Think of it as Outlook's 'Stop processing more rules' flag.

We could set a certain flag and add it to the other processes' signal conditions, but this leads to a high coupling of business processes, more complexity, and over the lifetime of a Creatio instance inevitably to errors as everyone needs to know this 'magic' behavior.

Ideally, signals in Creatio would have the option to distinguish between different triggering options, like 'user', 'business process', 'import', 'odata', 'event handler', etc. but unfortunately, this is a missing feature.

Any thoughts would be more than welcome!

Thanks,

Robert

2 comments

Robert Pordes

12:20 Nov 13, 2024

Hi Community,
any ideas on this?

Thanks,

Robert

Serhii Parfentiev

17:51 Nov 14, 2024

Hello,

At the moment, such functionality is not available in Creatio's OOTB solution for triggering the addition/modification of records.
Indeed, a workaround in this situation can be to create additional columns at the level of the object model that will be filled in depending on which method the record was created/modified (for example, a special column for OData).
We will register this development idea with our R&D team so that they can consider implementing such functionality in future versions of the Creatio product.

Thank you.

Show all comments

Question

IIS Configuration for daily processes to work

Ghiu Diana Stefania

16:29 Apr 25, 2023

Hello!

I have a few processes that have a trigger to run daily at 2AM or 4AM. Unfortunately, on my local environment, they start running only after I open Creatio. Also, all processes that have triggers don't work on weekends.

Dows anybody know how I can set up my IIS in order for them to work?

Thank you!

2 comments

Bhoobalan Palanivelu

16:54 Apr 26, 2023

Ghiu Diana Stefania,

The BP will be executed only when the Creatio Application (i.e., the Creatio worker process is running) running. Unless there is no application pool/worker process of the Creatio instance running, any configuration like auto trigger event designed inside the application won't work.

The trigger should be all day, if the weekends are excluded the trigger wont be initiated.

BR,

Bhoobalan Palanivelu.

Kalymbet Anastasia

12:37 May 01, 2023

Hello,

To remedy this situation, we recommend setting up a ping that will send requests to the app at a specified frequency and prevent it from "falling asleep" in the absence of active users.

The following procedure describes the setup procedure:

Set Idle Timeout = 2 for the IIS application pool on which the application is running. Configure automatic monitoring of the Loader and the application.

Use the free monitoring service https://uptimerobot.com/ to set up automatic monitoring with a frequency of 5-10 minutes.

Show all comments

Question

Triggers

oData

Studio_Creatio_enterprise_edition

8.0

Does Odata return response before DB Triggers are fired?

Shivani Lakshman

13:27 Mar 02, 2023

Hello team,

I have written a script using SEQUENCE & TRIGGERS for PostGres to auto increment the record number. This was a decision taken to avoid writing multiple codes through JS and Server side because we get inputs from a lot of sources - 3rd party integration, manual entry & business process.

While our trigger works well, we noticed that using odata, the response returned does not have the auto numbered value, whereas the auto numbering is indeed getting stored in the data base.

The question is, does Odata response for POST requests get triggered after all DB triggers are completed or does it happen just before a record is inserted into the DB?

PS: I tried triggers using BEFORE update and it did not work

1 comments

Dmytro Vovchenko

16:59 Mar 08, 2023

Hello,

This question needs to be analyzed mo deeply, but, based on your information, the POST request isn't affected by all the DB triggers and therefore happens before the insert.

Also, a small note, if you have autonumbering both on the JS and Server side than a new number will be generated no matter what is the source of the object (data, business process, etc).

Show all comments

Subscribe to Triggers