GeneXus BPM Suite course ENG

GeneXus objects are associated with the tasks in the process diagram, so that when the task is executed, the associated object is invoked exist.

Additional associations of GeneXus objects with the diagram and its first execution.

The Customer transaction is associated with the Record Customer task. Conditions are entered to modify the process execution flow. First execution of the process diagram, description of incoming tray of the Workflow client.

Procedure objects are associated with batch tasks, the process is executed in prototype mode and the tasks executed by the process are viewed in animation.

A procedure object is associated with a task of the batch type and the execution of the procedure by the workflow engine is viewed without viewing it in the incoming tray. The embedded subprocess symbol is replaced with a reusable. Definition of process instances and prototyping cycle. History of a process and animation with its execution.

Explanation on how to implement tasks with multiple instances and the various ways in which we can determine the number of instances that will be executed.

Determining in design time or in runtime the number of instances of a multi-instance task by means of a procedure, through the use of vector-type relevant data, by mapping between relevant data and variables included in parameters of procedures and web panels. How to implement error notice between a sub-process and its parent process.

The possibilities of the workflow engine for managing different types of documents, including repository administration and the operations necessary to modify documents, are explored.

Sometimes we need to handle files with user information such as documents, worksheets, text files, images, compressed files, and so on. The workflow engine provides the mechanism necessary to store them, in association with the diagram, and also to control them and have access security.

Relevant data is modified from a webpanel using the workflow API, different temporization patterns that can be implemented with the timer event are analyzed, and it is shown how to create a customized calendar to be associated with a process.

As opposed to the case of procedures, in webpanels, mapping values between relevant data and the variables present in the Parm rule is valid only for input variables. That makes it necessary to use the workflow API to modify relevant data. A study is made of the properties of the intermediate event of the timer type and of the various temporization patterns such as delays, warning or deadlines, which may be implemented by varying the properties. And it is shown how to create calendars, how to customize them, and how to associate them to a process.

Analysis of the pattern that enables repetitive notices to be sent to an individual responsible for a task, as reminder of the task that must be performed. Finalization of the automation of the subprocess corresponding to the reservation validation, with the result of the validation sent to the ticket reservation main process.

Using a pattern and defining deadlines but without interrupting the task, periodical reminders are sent until they cease when the individual responsible for the task completes it. This is implemented with the use of intermediate events of the timer type and throw and catch signals. Notices are monitored with the deadline scheduler applicative and an explanation is given on how to use the deadline checker.

To end, the reservation validation subprocess is finalized with different results that are informed to the main process.

This video shows how to initiate a workflow process from a GeneXus application using methods and properties of Workflow data types. The most frequently used elements of the Workflow API are presented.

New requirements are added to the initial process. In this case a customer of the agency is to be enabled to enter his own reservation through the website. Then upon confirmation of the entry, the air ticket reservation process is initiated and the first task in the reservation entry is marked as completed. An analysis is made of the Workflow data types most used and their main properties and methods.

The server and task properties are modified so that when it is instanced, automatic emails are sent to all users holding permits for the task. The initiation of a process is executed from a web application, programmed in the previous video.

This video shows how to modify the properties of an interactive task so that when it is initiated, automatic emails are sent to all users who hold permits to execute the task. Some of the properties of the workflow server are also modified. The initiation of a process is executed from a GeneXus object through the Workflow API, programmed in the previous video.

By associating interactive tasks from a business process diagram to GeneXus objects for Smart Devices, we can execute those tasks on a mobile device.

The ticket reservation process is simplified and user tasks are associated to Work with for smart devices objects of customer and reservation transactions. The application is generated in Android and executed on an emulator. The functioning of the client GXflow for Smart Devices is shown in runtime.

Dynamic forms enables us to create screens for data entry directly from the workflow client and associate them to interactive tasks, in runtime, without the need to write lines of code.

Instead of redesigning the application and creating new GeneXus objects to enter data, we may create dynamic forms and adapt them in runtime to store information, without the need to modify the application’s database. This is particularly useful when we must save data relative to a given process that was not provided for in the original workflow, where we must include information that is only related to each instance in the process. Dynamic forms enable us to store that information in workflow, making database structures for this type of information unnecessary.

By default, workflow tables are created in the same data store where the application’s tables are stored.

However, it is possible to store those tables in an independent DataStore. This enhances security for application data and workflow data, because it is possible to define access restrictions separately for each table type.

This topic does not include video.

GXflow Standard Client is an application that allows users to access GXFlow Inbox, Outbox, My Processes, My Performance and more applications called 'components'. These components allow users to interact with the workflow engine to create, run, and / or submit BPD tasks. However, sometimes it is necessary to access these components from another built application or a custom client is required.

This topic does not include video. See PDF.

It's shows how to define security for business processes, establishing users and roles.

This video shows how to define roles at the knowledge base level in order to assign them to tasks or processes. This video also shows how to create users in the Gxflow client to assign to defined roles. And a detail is given of the special roles of the Gxflow client that grant users different permits for the client’s activities.

The execution is done in production mode to initiate processes with users other than the administrator. The "out of office" possibility is shown, where a substitute user may inherit roles and permits of the user being substituted.

This video shows how to change the execution of workflow processes of the prototype mode used in development, to the standard client mode which enables us to log on with users different from the administrator user.

It also shows how a substitute user may substitute another user in executing the tasks of the other user during his absence from the company.

Upon the defined branches of a company, this video shows how to make processes and tasks corresponding to one branch unavailable to all other branches.

In this video you will be able to see how Organizational Units are created that allow defining groups within an organization, for example branches, departments, etc. Once these units are created, the users of the organization are assigned to them and each process will inherit the organizational unit of the user that starts it. In this way, an employee from one branch will not be able to execute a task from another branch.

GXflow uses certain default roles and permissions that must be available in the GAM repository for it to work correctly at runtime. For this there is an initialization utility that must be run. When making prototypes in GeneXus, the initialization process is executed automatically, but to take it to production it may be necessary to execute the manual process.

This topic does not include video. See PDF

The deployment of an application based on Workflow is done from the IDE, like any other GeneXus application. The complete process consists of 3 stages:

• Deployment of the binary files of the process diagrams and their dependencies.

• Deployment of the database files and process definitions metadata.

• Licensing

This topic does not include video. See PDF.

The features available of the Gxflow client are shown for the application in the statistics of processes, tasks and work teams.

Based on the information that is stored during the execution of processes, Gxflow client provides us with statistical reports and graphs relative to the analysis of processes and tasks, and reports on process performance, as well as tasks and work teams, all of which facilitate an adequate decision making in the administration of work processes.

Further exploring the main data types and functionalities of the Workflow programming interface.

GXflow Custom Client, a client of Gxflow tailored to your needs, with a look & feel and behavior that matches the rest of your application.

GXflow Custom Client, a client of Gxflow tailored to your needs, with a look & feel and behavior that matches the rest of your application.