TOTVS Fluig English

Árvore de páginas

Common Activity

This is the common workflow activity on Fluig. It is the basic unit of separation of a workflow process in activities . It must be executed by a user so that the workflow request can be moved forward with the workflow request.

User activity

Very similar to the common activity, but more restrictive. This notation determines that it is mandatory for a user to execute this task and that it is controlled and registered by Fluig.

Service activity

This activity allows to check data from an external service and go to the data process originated from these external services. In the activity properties, it is possible to select a service registered in fluig and edit a javascript script that will access methods and data for that service . Using the hAPI and hFOrms apis, it is possible to send data obtained in the service consultation to fluig.

Example of a code generated to initiate the integration work with the service:

try {
	var Service = ServiceManager.getService('rm');
	var serviceHelper = Service.getBean();
	var serviceLocator = serviceHelper.instantiate('classe.locator');
} catch(error) { 
	log.error(error);
}

The code generated in this script is incorporated to the afterStateEntry event related to this process and it will be processed in the moment the request enters the service activity.

Message sending activity

This activity allows the sending of an e-mail message to an external address to the address on the fluig tool. It is possible to set up the type and e-mail (text or html), the subject and body of the e-mail in a modeling time. 

Manual activity

Manual activity represents an activity external to the system that does not necessarily need to be executed by a user using the process moving screen. A practical example would be the user seeking a document that has just been printed. This notation must be used in cases where these external activities need to be placed in the process diagram for process documentation purposes.

Business activity.

The Objective of this type of activity is to query business rules that are not internalized in Fluig. This query is made by a javascript script consulting a pre-registered service in fluig. The internal behavior of this activity shall be the same behavior of the service activity.

Script activity

This activity executes a script by being executed. In a modeling time, this script must be developed in javascript language and can use all infrastructure apis that fluig offers, such as hApi and hForm.

Subprocess

Business activity.

The Objective of this type of activity is to query business rules that are not internalized in Fluig. This query is made by a javascript script consulting a pre-registered service in fluig. The internal behavior of this activity shall be the same behavior of the service activity.

Subprocess

Allows to select another process previously exported to the fluig server as a subprocess.

 

  • Sem rótulos