Is it possible to start a Job Queue entry with another user? (NAV 2017)

Jan87

We are quite new to NAV 2017. We are coming from 2009. The Job Queue is a cool feature, but one thing I don't understand.

We want to use the Job Queue to run Background-Jobs (formerly NAS-Jobs). We want them to be started with different technical Users with only the neccessary permissions.

The problem is that the user that runs the queue has to push the button "Ready" in the Job Queue Entry Page.

And this every time the queue stops or need to be restarted/rescheduled.

Is there any possibility to change it?

Sorry for my bad english

OfficeZier

Apparently not anymore. This is due to scheduling posting etc. from the user itself. If someone schedules a posting queue and the user can be edited, there is no secure way to tell, who started this in first place.

If a job has to be executed more often, you can check "run on monday" etc. and play with "No. of minutes between run"

Another option would be to enable this again by code.

robbonick

Hi, I ran into this problem after upgrading to 2017. We use Job Queue Entries heavily, and they run using specific Service Accounts for example "AD\SVCACCOUNT1". We found that if the Job Queue Entry fails, and is restarted by a user, the Job Queue Entry/Scheduled Task would then be updated to run as that user.

We tried to solve this using Events, but there is no Event in our version which would help. There is an Event on COD453 called "OnBeforeScheduleTask", it would be nice to have the event "OnAfterScheduleTask", which would allow us to update the User ID field to "USERID" without modifying the standard codeunits.

Alas, there is no event so we had to resort to modifying the codeunit to update the User ID fields after the task has been scheduled. Hope this helps.

OfficeZier

Apparently not anymore. This is due to scheduling posting etc. from the user itself. If someone schedules a posting queue and the user can be edited, there is no secure way to tell, who started this in first place.

If a job has to be executed more often, you can check "run on monday" etc. and play with "No. of minutes between run"

Another option would be to enable this again by code.

robbonick

Hi, I ran into this problem after upgrading to 2017. We use Job Queue Entries heavily, and they run using specific Service Accounts for example "AD\SVCACCOUNT1". We found that if the Job Queue Entry fails, and is restarted by a user, the Job Queue Entry/Scheduled Task would then be updated to run as that user.

We tried to solve this using Events, but there is no Event in our version which would help. There is an Event on COD453 called "OnBeforeScheduleTask", it would be nice to have the event "OnAfterScheduleTask", which would allow us to update the User ID field to "USERID" without modifying the standard codeunits.

Alas, there is no event so we had to resort to modifying the codeunit to update the User ID fields after the task has been scheduled. Hope this helps.

Juhl

Use OnAfterModify event of table Job Queue Entry

IF Rec."User ID" <> 'domain\user' THEN BEGIN
Rec."User ID" := 'domain\user';
Rec.MODIFY(FALSE);
END;

robbonick

Juhl wrote: »

Use OnAfterModify event of table Job Queue Entry

IF Rec."User ID" <> 'domain\user' THEN BEGIN
Rec."User ID" := 'domain\user';
Rec.MODIFY(FALSE);
END;

This will modify the Job Queue Entry, but the Scheduled Task will be left with an incorrect User ID.

Juhl

Yes, but the Task is created based on the Job.
It works for me.

xStepa

this must be done before the Job is scheduled with CreateTask, than it works ...