Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. If a Pipeline creates a new Person, the first Name returned by the External Identity Source backend will be used as the initial Primary Name for the new Person.
  2. Pipeline Person Matching ignores the existing Person status.

Plugin

  1. Plugins must be uniquely named.
  2. Plugins installed in the core directory cannot be disabled.
  3. Plugins installed in the available directory are optional, and must be enabled prior to use.
  4. Plugins installed in the local directory are deployment specific, and must be enabled prior to use.
  5. If Plugins with the same name are installed in multiple locations, the resolution precedence is (1) core, (2) available, (3) local.
  6. Plugin schemas, if defined, are applied to the database for active Plugins only.
  7. If a Plugin is suspended, its associated database schema is not removed automatically.
  8. A Plugin cannot be suspended or deleted if it is in use (referenced in a configuration object).
  9. 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.
  10. If a Pluggable Model is deleted, the Entry Point Model associated with the Pluggable Model is also deleted.
  11. The Plugin Registry is refreshed upon loading of the Plugin Configuration page by the Platform Administrator.

...