Appendix

Inheritance

PAM utilizes the concept of inheritance is several areas to make the management and configuration of objects more streamlined and easily organized. Inheritance defines the relationship between a parent and child object and specifically what is inherited down from the parent to the child which resides beneath it.

Inheritance in PAM can be found in the following areas:

  • Permissions

    • Permissions are inherited by default from parent folder to child objects (subfolders or records). If permissions are modified on the parent folder, then all child objects will reflect this change.

    • To make permissions unique means to stop this parent to child inheritance and instead have the child contain its own set of permissions which may in turn inherit down to its own children.

  • Formulas

    • Formulas are inherited by default from Record Types. If the formula on a parent record type is modified, then all child types will reflect this change.

    • To make formulas unique means to stop this parent to child type inheritance and instead have the child contain its own formula which may in turn inherit down to its own children.

  • Strategies

    • Strategies are inherited by default from Record Types. If the strategy on a parent record type is modified, then all child types will reflect this change.

    • To make strategies unique means to stop this parent to child type inheritance and instead have the child contain its own strategy which may in turn inherit down to its own children.

  • Policies

    • Policies are inherited by default from parent folder to child objects (subfolders or records). If a policy is modified on the parent folder, then all child objects will reflect this change.

    • To make policies unique means to stop this parent to child inheritance and instead have the child contain its own policy which may in turn inherit down to its own children.

The “pros” of inheritance is that it allows for ease of use and flexibility when configuring and using the system while the “cons” are that the more unique objects you create, the more difficult and cumbersome it becomes to understand and manage the structure of your system.