dschlieder
Well Known Member
Did a quick search and couldn't find this discussed anywhere.
Has anyone implemented row security on the submitted job search screen to prevent users from deleting jobs that have not completed, i.e. job status of S, W or P? And maybe prevented them from terminating active jobs?
We have a group of users who no matter how many times we tell them not to delete incomplete jobs, they do it anyway. They simply select all of their jobs and delete them all regardless of the status - for some reason they can't seem to stand having anything there.
Of course this can lead to corrupt data if a job is deleted or terminated in the middle of a process that updates records as it processes. Or they delete a waiting job and don't know they did and expect it to have completed.
In some cases we have told them that if they know what they are doing they can terminate an active job. Not sure that that is a good idea either.
However we want the power users, i.e. the IT staff that know what the ramifications are to be able to do these actions.
Since our security is not environment specific and we only have the one logic server for all environments, I'm gun shy about making changes without some thoughts on this issue from someone who has already gone down this path.
We have never put in any row security before so this is all new ground to us. And JOBSTS is not set up for row security in the DD.
Any insight into securing this application would be appreciated.
Thanks,
Dave Schlieder
Has anyone implemented row security on the submitted job search screen to prevent users from deleting jobs that have not completed, i.e. job status of S, W or P? And maybe prevented them from terminating active jobs?
We have a group of users who no matter how many times we tell them not to delete incomplete jobs, they do it anyway. They simply select all of their jobs and delete them all regardless of the status - for some reason they can't seem to stand having anything there.
Of course this can lead to corrupt data if a job is deleted or terminated in the middle of a process that updates records as it processes. Or they delete a waiting job and don't know they did and expect it to have completed.
In some cases we have told them that if they know what they are doing they can terminate an active job. Not sure that that is a good idea either.
However we want the power users, i.e. the IT staff that know what the ramifications are to be able to do these actions.
Since our security is not environment specific and we only have the one logic server for all environments, I'm gun shy about making changes without some thoughts on this issue from someone who has already gone down this path.
We have never put in any row security before so this is all new ground to us. And JOBSTS is not set up for row security in the DD.
Any insight into securing this application would be appreciated.
Thanks,
Dave Schlieder