...
- 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.
Type
- When a new CO is created, the default Types will be instantiated into the CO. Afterwards, available Types are only updated by administrator action.
- A Type cannot be deleted once it has been used by at least one Registry object, even if that object is subsequently deleted.
- A Suspended Type can not be assigned to new Registry objects, but existing objects already referencing it will not be changed.