Workflow Office
Job WF_PROCESS sometimes does not process the workflow queue. There is a problem when the background jobs run in several different clients - they only work properly in one client.
Background jobs are almost always client-specific. This does not apply, however, when the background job is started by an event (which is not the case here) or when the respective user has the administrator authorization S_BTCH_ADMA. In these two cases, the background jobs affect all clients.
SolutionBecause the workflow background jobs WF_PROCESS and WF_PROCESS_DAILY must run non-client-specific (so they do not delete each other!), the batch queue (transaction WF05) must always be started by a user who does not have administrator authorization.
No comments:
Post a Comment