11.04.2022
11:15
Dear Webcon Community!
Problem:
longer background processes has to be split to smaller parts to fit in transaction timeout limit. For example if you have to move 50-1000 instances each morning taking some minutes, we have to use "select top <n>" and run global action more often (eg. in every 10 minutes) Earlier (before BPS 2020), it was a once a day run.
Proposal:
have new GA setting to specify number of cycles it should perform after triggered by schedule. This way we can split big transactions, but still keep once a day schedule for global actions. (I know execution condition on action is a workaround, but still too many global action cycles)
What do you think?
Thank you!
BR,
Peter
