As the Sub-Process is multiple, the wait page of this task (feedback) cannot be displayed to the end users. When this property is activated, Bizagi will immediately execute the Activity through its Work Portal a wait page will be displayed while the request is processed, notifying the completion or failure of this execution. Hence, away from the userвЂ™s experience.Дisable show feedback when the first activity of a Multiple Sub-Process is an Automatic taskДЄutomatic tasks have a property called Show Feedback. If you know that an interface takes a long time to process (because of its nature and the amount of processing that must be done), design the automatic activity without feedback. Interfaces that take a long time to respond (like document management interfaces), feedback will make the application look slow and will cause imminent performance issues. When interfaces don't have feedback they are executed by the scheduler, allowing the case to move on without end users waiting for an answer. For the end user, the Work Portal will notify that this execution is scheduled. When this property is disabled, the Asynchronous Activity is executed by the Scheduler service later on. If not, convert your interfaces to asynchronous.Д®nable show feedback in interfaces that take NO MORE than 10 secondsДЄutomatic tasks have a property called Show Feedback.

Use synchronous interfaces only if you can absolutely guarantee that the external service will respond in maximum 3 seconds. In this way, you will have an Asynchronous Activity which will handle retries and other possibilities to manage transactions (for instance, delayed locks are avoided) in points of the Process where there is a significant service time (due to a possibly and presumed delay implied in a communication with external systems). When you have Activities which invoke external services (SOAP Web services or REST services), or which use an integration component (through the Component Library), use the Asynchronous property for that Activity.

When using synchronous interfaces if the interface fails the case will be blocked.ДЄsynchronous Activities have been designed especially to call external interfaces, which are mainly used for integration with existing services in other systems.

When using synchronous interfaces, if the answer takes too long the tables used may be blocked, affecting ALL end users.

Synchronous interfaces wait for a response from the external service before they allow the case to continue.

When using synchronous interfaces, as they are executed the tables that are involved are blocked until the transaction is finished.

When the time involved in an integration point's transaction is significantly extended you should use asynchronous tasks instead synchronous ones for the following reasons: This section provides some guidelines and practices to create and configure efficient interfaces that do not affect the user experience and the normal execution of Processes.

It is possible to invoke Web-based services (i.e., SOAP, REST) or APIs directly from within Bizagi Processes (i.e., dlls, jars).

In projects where there is the need to integrate the Processes with existing applications (e.g., ESB systems), Bizagi's Integration layer presents multiple integration options. Bizagi provides a powerful integration layer follows a service-oriented architecture that supports different integration possibilities for the entire corporate solution.

Bizagi modeler suspend event