Prev
Next
Forums Infor / Lawson Platforms S3 Security

User not seeing jobs added or print manager

 4 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
rlong
New Member Send Private Message
Posts: 5
New Member
2/13/2020 3:54 PM

We have a user that I can not figure out what is going on. She can add a job in lawson (example PR260). When she adds the  job, it accepts, but it does not show up in her job list. She can not see the job list.

Also when she goes to print manager, nothing is showing up.

I have checked the users security, have deleted her user account and recreated, made sure there was no orphan user in DELUSERS etc.

I can not figure out why she can not see her print manager or jobs. Any idea what to look at?  I opened a ticket with lawson support, but not sure the person I got knows what they are doing.

Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
2/13/2020 4:02 PM
What platform (Windows, *nix, IBMi)? Sounds like Windows... How is the user adding the job (Portal, Ming.le, jobdef in LID)? After she adds the job, can you (as Lawson) see the job was actually added?
rlong
New Member Send Private Message
Posts: 5
New Member
2/13/2020 4:28 PM

we are windows based, and the job is added inside of portal.

I can see the job as lawson.

JimY
Veteran Member Send Private Message
Posts: 510
Veteran Member
2/13/2020 5:14 PM
What version of Lawson LSF are you on? Also when you say she can't see it in her list do you mean that when she goes to the form she can't select it or is it in the Job Schedule Active queue that she can't see it?
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
2/13/2020 6:40 PM
It could be a number of things. Make sure they have some form of batch access in security, something akin to the Batch role. Another possibility is make sure that the case of the username as entered on the form matches the way it was created initially. I had a client that created a job, but when they cleared the form to look up that job, the username was being returned in uppercase (and they had used lower when the account was created)