...
- When a Person Role is associated with a COU with any status other than Archived, the associated Person is added to the COU's All Members Group. If the Person Role is disassociated from the COU, or the Person Role status is Archived, the associated Person is removed from the COU's All Members Group.
- When a Person Role is in Active or Grace Period status and is associated with a COU, the associated Person is added to the COU's Active Members Group. If the Person Role is set to any other status or is disassociated from the COU, the associated Person is removed from the COU's Active Members Group.
- A Person Role is considered valid (and provisionable) if (1) the Person Role is in Active or Grace Period status, (2) the valid from date is unspecified or in the past, and (3) the valid through date is unspecified or in the future.
Plugin
- Plugins must be uniquely named.
- Plugins installed in the core directory cannot be disabled.
- Plugins installed in the available directory are optional, and must be enabled prior to use.
- Plugins installed in the local directory are deployment specific, and must be enabled prior to use.
- If Plugins with the same name are installed in multiple locations, the resolution precedence is (1) core, (2) available, (3) local.
- Plugin schemas, if defined, are applied to the database for active Plugins only.
- If a Plugin is suspended, its associated database schema is not removed automatically.
- A Plugin cannot be suspended or deleted if it is in use (referenced in a configuration object).
- When a Plugin is instantiated, a skeletal record of the Entry Point Model is created, holding only a foreign key to the parent Pluggable Model. Validation and Application Rules are not executed when this record is created.
- If a Pluggable Model is deleted, the Entry Point Model associated with the Pluggable Model is also deleted.
- The Plugin Registry is refreshed upon loading of the Plugin Configuration page by the Platform Administrator.
...