You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

 

 

Narrative:

  1. Record is created in institutional source system.
  2. Institutionally defined logic invokes the Person Registration and Update service
  3. Person Registration and Update service invokes search / match to determine if the record supplied matches an existing record
    1. If search / match returns a definite match, person registration invokes Identifier Assignment to generate any additional identifiers (if needed), registers new person, address and affiliation data to Person Data Store and puts a message on the Person Update queue
    2. If search / match returns a possible match (verification required), Person Registration puts a message in a Person Record Verification queue, where Orchestration Engine will see it and fire a workflow
    1. If search / match returns no possible match, person registration invokes Identifier Assignment to generate any needed identifiers,  registers record to Person Data Store , and puts a message on the Person Update queue.
  4. Orchestration engine triggers refresh of data-driven group information in the Groups Service based on message in Person Update queue
  5. Orchestration engine invokes rule-based provisioning in Provisioning Service
  6. Accounts and access are provisioned according to data-driven group membership

 

 

  • No labels