Question

Standard Permission Set has been changed in customer environments

  • 19 July 2021
  • 1 reply
  • 107 views
N
Rank
Userlevel 4
Badge +8

Hi,

If a standard permission set has been changed in all the customer environments including internal Dev and BnT environments, what are the possible reasons for that? How can we investigate what has happened or whether it has done as a customization?
eg: If we export BR_FULL_IS_VIEW_ACCESS permission set from a core and customer environment, set of Revoke_Method( ) statements are missing the file exported from customer environment

Best Regards,
Nisansala

This topic has been closed for comments

1 reply

NickPorter
Rank
Userlevel 6
Badge +18

If the permission set in the customer environment is different from the current CORE that you have then either:

(1) the customer (or a partner etc) has changed the permission set

(2) IFS delivered one or more later customization with new file(s) that recreated/modified it to be different

(3) IFS delivered one or more later delivery such as an Update with new file(s) that recreated/modified it to be different but the customer did not apply it properly 

I don’t really see any other possibilities.

If the customer changed it themselves then the only way to prove that would be to compare their exported version to the originally delivered version from IFS and any potential later delivered files that changed it, which should be in Harvest or whatever development repository is used currently.  You can’t just compare the customers version to an export from Core because that doesn’t reflect what was  sent to the customer e.g. for mods.

If IFS sent customized code for a modification that required a change to the permission set then either an adjusted script should be in the development repository or *possibly* there is a manual change that the customer was advised to do in the BOD that you would need to find.

If IFS has sent modified files that the customer has NOT applied (so their version has not been updated as it should have been) then that could be seen only by proving that the files that were sent (again, by checking in the dev repository)

Hopefully this helps.

Nick

Terms & ConditionsCookie settings