We are having catastrophic issues of having Post Processing BPMs overriding Epicor defaults. We are using Field Security Maintenance to make a record as read only for all users (example Credit Limit), but overriding default of zero to 1. When we save as a non security maintenance the Epicor defaults take place. This was a change with the latest version.
This is causing data integrity issues.
Does anyone have suggestions?
Thank you,
Cyle
I’m not sure I follow what your issue is can you explain a little further.
A BPM doesn’t care about field security (it never has) what’s the difference you are seeing?
Prior to 2022.1, we had field security on a number of customer fields set to “Read” by default for all but select users and Security Managers. We also had an in-transaction method on the GetNewCustomer method to overwrite system defaults with our company-specific defaults. Upon saving these BPM set values would save into the database. However, after this update, those BPM set values are no longer being saved for users with “Read” security on those fields. We looked at changing these from a Method to a Data directive but seem to run across the same security access control issues.
We also looked at extended properties but it does not appear that we can override values there for standard fields. Is there a way to run a BPM with higher-level access than that of the user who triggered that BPM?