TOTVS Fluig English

Árvore de páginas

Index


Speaking of Converting Requests...

The purpose of that feature is to convert requests opened in older process versions to newer versions. This is done by mapping the older version process activities to the newer version activities. So the old process request receives all features and activities from the newer version with a simple conversion.

When continuous improvement is correctly applied to business processes, a workflow request should start and end in the same process version.

The main reason why process versioning is allowed lies in the fact that it simply offers the opportunity of improving processes, in order to optimize the time spent on their tasks or allow a better distribution of financial and human resources in an organization. Another reason why the platform offers workflow request conversion is that it would be the last resort for situations such as:

  • The user responsible for a task cannot move it to another activity.
  • The process manager user cannot move the workflow request.
  • From a business point of view, canceling the request and starting another one is not possible.

Noting that, when performing request conversion, some rules of the platform should be considered, as for example:

  • Process events that affect both the source and the target activities will be executed.
  • The user who receives the task should be a user included in the assignment mechanism defined for the target task.
  • The Admin user privilege does not exceed the limitations imposed by the target mechanism. It is not possible to convert process requests flows of which are pending in a Subprocess activity at the time of conversion.
  • The version of the request form will be kept after conversion.


Creating specific process versions for technical fixes and adjustments that allow the workflow request is not recommended and must be avoided to the fullest. Refer to FAQ BPM 097 to view a list with some actions that can be taken by the process developer in order to develop processes that require such constant maintenance procedures without versioning the process as often.

Converting Requests

01. From the main menu, click Processes.

02. Click Convert requests.

03. Select the process that contains the requests started in an old version, which you want to convert to a new one.

04. The window below displays Process data, allowing viewing the number of versions and open requests. Select the version of the process to convert its requests

You can only convert open requests, so the selected process version must contain open requests.

05. In the last window, you can check Process activities and view the number of current activities and the number of open tasks in each activity. Select the process activity to be converted

06. Select Next, located in the upper right corner of the window.

07. Select the target version, that is, the version to which the requests that are in the source version will be converted.

08. For each source version activity, select a target version activity.

For each old version process activity, a target version activity should be mapped. That mapping is required in order to associate the activities that are the same or similar between the two process versions.

09. Click Next, located in the upper right corner of the window.

10. From the displayed requests listing, select the ones to be converted.

11. Click Next, located in the upper right corner of the window.

12. Click Convert.

By converting the request, all pending tasks are finished and new tasks are created for the target activities.

Once the conversion is complete, you can view the log and check whether it was performed successfully.



Please note!

This documentation is valid as of the Lake (1.7.0) update. Previous updates may contain different information than what you see on your platform.