10
If a user creates or restarts a job queue entry, the User ID is set to this user. And if this job queue entry makes any changes, the name of this user ends up in the change log. This creates the suggestion that the changes are made by a real user instead of a service account. And this leads to problems, it is a returning topic in audits but also leads to confusion and questions for other users (why has this person changed this record?).
The alternative is to only create / edit job queues when logged in as a system user, but that's easy to forget.
And within larger organizations there are more users with access to the job queue, but you cannot give all these users access to one service account because it can make their other changes untraceable to the real user.
Therefore, the idea is to set-up a service account for the job queue, and all changes made by the job queue will be logged with this user. So that it will be clear that these changes are made by the job queue.
To be short, go back to the situation before NAV 11 when this was introduced :).
The alternative is to only create / edit job queues when logged in as a system user, but that's easy to forget.
And within larger organizations there are more users with access to the job queue, but you cannot give all these users access to one service account because it can make their other changes untraceable to the real user.
Therefore, the idea is to set-up a service account for the job queue, and all changes made by the job queue will be logged with this user. So that it will be clear that these changes are made by the job queue.
To be short, go back to the situation before NAV 11 when this was introduced :).
STATUS DETAILS
Needs Votes
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team