Improving with kawak®

Today the Kflow steps work sequentially, it would be very good to execute two tasks in parallel because many processes work that way, and it is not possible to model them in the WF.

Allow WFs to be edited by moving a step from the WF to another part of the structure of the same WF (if only with their child steps). Because for productivity reasons, modifying or editing a workflow (even without publishing it) today is really inefficient and tortuous, because if you have to modify a small part of the WF that way, then you have to recreate all the activities from there on down, including approvals and forms from scratch. This should be graphic or at least with a relationship menu to be able to modify the relationships of a given WF. In this sense, Kflow has a great disadvantage because every process is subject to continuous improvement, and I reiterate that making a change today is totally surreal and highly inefficient.

Include logical functions in formula fields: IF, AND, OR, NOT, and operators of Greater than, Less than, Less or Equal and Greater than or Equal.

Just as today you can use the Formulas field type to import numeric fields from other forms or parts of the WF, it would be desirable to be able to import text fields from other sections of the WF. For example, let it be through the existing formula component, but with a new option in addition to existing wings (Normal, Date or Grid), which is called “Text”, whose reason is only to bring the value later without obviously being able to perform calculations (again I mention because it is text). It would be useful for the user to focus on information from another form such as product references, batches and others that are alphanumeric, without having to review the previous parts of WF forms.

In decision forks, the application allows you to select a field of an object, but it does not allow you to compare it with anything, which indicates that there is an error in that the application can select all the fields in a form, but is unable to compare the values of the field of an object. It would be interesting if the WF could make decisions based on the field value of an object as it seems that it has been designed but that does not currently work.

In the “response times by stage” section, it would be very good for management to be able to filter the stages by responsible person and thus better track them.