Converting actions to run as asynchronous actions
1643
Views
3
Comments
New
Backend

Executing actions asynchronously.

Basically there should be an option for any action i.e. Client Action, Server Action to make it as asynchronous actions.

So whenever it is turned on as asynchronous action, defining the output parameters has to be restricted, similar to how the number of output parameter is restricted when we convert any action to a function.

Also, there should be an option to make "ForEach" action as asynchronous, which will invoke the multi-threading/parallel execution capability.

Hi Nicholas,
Thanks for the information. I agree these workarounds can help fulfill the requirements. 

But I think there are few drawbacks as well associated with these workarounds. The first one being, obviously the time consumption for this workaround, and second when we specify any timer associated with any action, yes we can wake the timer to run is asynchronously, however if I want to specify some input parameters based on which the actual functionality of the server action will depend, I can specify the input parameters while Waking the Timer action.

However, if the OutSystems team just provides an option to make any Server action/Client action asynchronous, it would solve many performance issues very easily.

Regards,
Aditya

Yes I think it could be made simpler and more low code. Try using Processes instead of Timers to solve the issues you mentioned.