I did a BPM that was GetNewOper, and mandated ti to only manger groups. However, CSR’s are still able to add operation. Anyone know what I am missing?
Why don’t you do this on the Update method, and if you detect they are in the manager group, just hault the Update in a pre-process BPM. That would achieve the goal you are trying to reach.
So, Erp.ABCCode.Update, set a pre-processing restriction for the CSR’s? Ok, I will give that a shot as well. Wonder if that will restrict anything else…
If thats the correct process. You’ll wanna do a trace to make sure, and basically just do a check if there is a new operation being submitted and they aren’t a manager, throw an exception and stop the BPM and don’t allow the update.
Edit: Basically do a check that if the JobOper.RowMod = A, or U (if you wanna restrict Updates also to operations already inputed). and if those are there, then you can safely flag it and return an error if they aren’t a manager.
Figured it out. I was using the GetNewJobOper, when they were going a different way. Thought the business object JobEntry, and InsertNewJobOper. I noticed it due to the Update method also being triggered. So, once I realized it was a totally different method, I was able to restrict where it was needed and it all worked out. But I would not of easily thought of it without the push to check the JobOper.RowMod. @mathis1337 , thanks for the input and ideas!
Glad you got it figured out! Usually doing a trace solves the problem in these scenarios !
1 Like