Hello Community,
we have several problems using the jobg object in Actions.
Our requirement
- Jobs are executed parallel within an action.
- The number of parallel jobs is determined dynamically at runtime.
- You can react to the end status of the jobs in the action.
We currently use job groups for this purpose.
Action examples in which we currently use job groups
- Stop/start of queues during maintenance of a target system
- The target system can be connected to several AE clients.
- The Job for stopping/starting the queue is started for each AE client.
- Jobs are executed simultaneously.
- Execute R3 report with several variants at the same time:
- R3-Job is started for each variant.
- R3-Jobs should be executed simultaneously.
Problem
We activate the same action multiple times in different processes, sometimes at the same time. A job group cannot be started more than once at the same time, therefore the workflow is canceled.
Our Workarounds
Variant 1:
- Workflow that contains a job group is set to "max. parallel 1".
Variant 2 (example is attached):
- The action-specific job group in workflow is replaced at runtime by process-specific job group.
- The action-specific job group in the workflow only serves as placeholders.
- The action workflow is modified at runtime: Action-specific job group is replaced by process-specific job group.
- This only works as long as the process in which the action is used is not started multiple times at the same time.
Is there another solution for our requirements or are job groups the right choice? How can we solve our problems with job groups?
Thank you !
Best Regards
Heiko Schmider
------------------------------
dmTECH GmbH
Team Business Automation
Phone +49 721 5592-2622
E-Mail:
heiko.schmider@dm.de------------------------------