Workflow

Automate processes, Trigger and respond to events, Synchronize activities…

Workflow allows you to perform various processes, preferably without the need for user interaction. You can engage users only if approval is needed, input is provided, or to perform an action assigned to them.

You can model the course of the process (workflow) in the Workflow Designer. It is possible to control the flow by means of synchronization of activities, cyclic processing, waiting for events, setting deadlines and different ways of ending the entire workflow run or its individual branches.

You can maintain the workflow in versions, so that when a new, modified version of the workflow is deployed, the earlier execution of the workflow can be completed by the previously defined process, but the new execution already takes place according to the new version of the workflow.

You can monitor each workflow launch in a log that accurately captures progress of individual steps.

If the user is assigned any tasks during the workflow (e.g. approving a request), the task appears in the Task List and user receives a notification about it. Of course, you can also display the tasks generated from the workflow to the user in the task queues which you can define for the overall prioritization of activities, and you can remind the user of them (see time operations below).

You can also implement a simple state workflow that defines from which states you can transition to other states. Users are then provided with buttons with corresponding names, which they can use to transition to the subsequent enabled states.

Take a look at an example in documentation.

ObjectGears can automatically evaluate date values, compare them to the current time, and perform defined operations. All this without user interaction. As underlying data, you can use values ??stored in classes or queries that you define arbitrarily using ObjectGears queries (Transact SQL syntax). You always define intervals before or after a given date and what should be done, e.g.:

Jobs are used for scheduling operations such as import, export, workflow, scripts... Jobs allow detailed settings from a time point of view, where you can define different starting frequencies (e.g. daily, weekly...), define moments that are relevant (e.g. what day of the week, how many days of the month...), scope of the run (e.g. daily time from - to, every x hours and y minutes), job validity.

In connection with the workflow, which is initiated by events and the course of previous activities in individual branches of the workflow, you get a very powerful tool for solving a wide range of scenarios.