Ability to start a process flow from the moment of entering data on a field.

Related products: Software Factory Universal GUI Indicium Service Tier

Will it be possible to add a new process action that will trigger when a user entered data on a field? For example, after the user entered data in a field it will save automatically:

  • Without action from the user.
  • We can also consider keyboard actions like when user press [tab] after entering data in a field to start a process a process action.

What we currently have is 

  • Edit Row process action - User has to press save button to start the process action. 
  • Default Procedures - Can consider keystrokes but not possible to combine from process flows.

 

NewOpen
 
Having a process flow start during adding or editing a row would certainly be a great addition, esspecially nowadays with the Generative AI process actions.

OpenPlanned for the Universal GUI

PlannedWorking on it!

Working on it!Next release

Next releaseCompleted
 
Implemented in the 2024.1 platform version. Compatible with Universal GUI from 2024.1.11

@Mark Jongeling is the addition of the @auto_commit parameter in the Default logic the solution for this Idea? 
 

If so, does this mean that the Add row and Edit row process flow start actions are ‘triggered’ upon the auto_commit and the auto_commit can initiate a Process Flow?
 

If above is true, can this then also return Values to the Default logic to be applied to the same Form?

Example: add Postal code + house number —> Process Flow returns Street + City.


@Arie V, the Auto_commit is indeed the solution to this idea.

Add and Edit row process actions can start a process flow. Once the default logic is triggered, you can write logic and set @auto_commit to 1 when the action should be commited. This then can continue a process flow, even in a loop.

An example can be, Starting with an Edit row (auto edit also possible). Then after editing a specific column, set @auto_commit = 1. That will tell the Universal GUI to commit the action; which is savig the record in this case. Then the process flow continues and could call a HTTP connector, an Extract JSON data connector or even the Generative AI connectors. Once that is finished, you could return to the Add/Edit row process action and start the loop again.

Your example can be achieved if the record could be saved temporarily. The code would look a bit like this:

if @cursor_from_col_id in ('postal_code', 'house_number')
and @postal_code is not null
and @house_number is not null
/* and all other mandatory fields are filled */
and @street is null
and @city is null
begin
set @auto_commit = 1
end

This would commit the save when the postal code and house number are saved. That could continue the process flow and obtain the Street and City via a HTTP connector. Then the Edit row process action could be called (again) and continue editing the same row.

Starting process flows during editing is something that is not supported but we do want to offer that in the future.


Thanks for clarifying @Mark Jongeling!