Server side actions are used when you want to delegate the work to the server.

Reasons for delegating to server might be that you want a single performer - the server. This is the case when assigning numbers that must be unique for example.

On viewModel Root class choose action "Edit criterias for server side execute".

Then "Make available for Server side execute"

Now you can set:

Interval == how often is this checked by the server

Serialized Blocking == when true the job should be small and quick - it is done within the main loop of server actions. If the job is long running/slow it is better to leave as FALSE so that server responds to admin events faster (evolve, check checksum etc)

Max Answers == The PS Ocl expression will return this many at most - -1 is unlimited

Pre EAL == Action language that will be executed prior to PS-OCL. One example of usage is:

-- You do not need anthing here but a good example is if you want to limit on a Time:
vYesterday:=DateTime.Today.AddDays(-1)  -- vYesterday must be a ViewModel variable

PS Ocl == the expression the server will run every "Interval"-second, just after the Pre EAL has executed. The result from the expression should be a list of CLASS of the same CLASS that your viewModel root has. For each item in result list the ViewModel will be created. Its actions will be executed in order. Any changed state will be automatically saved to database.

Example: