Versions Compared

Key

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

...

Connector definitions contain the schema definitions for the objects and attributes implemented for the external system as well as the calling methods for the system they support.  Examples of method calls are:·       

  • Read Accounts

...

  • Read Groups

...

  • Create Account

...

  • Create Group

...

  • Update Account

...

  • Update Group Membership

...

  • Delete Account

...

  • Delete Group

For each of these method calls, the connector definition contains the actual technical implementation for the connection such as calling a REST API, executing a store procedure, reading a table or view, inserting a record, etc.

One of the benefits of this type of “disconnection” between the business processes and logic, and the connector is that common workflows can be used to support any connected system.  For example:  the , the create account workflow will take input from the user for any attributes required for an account.  The logic to determine what attributes are needed for a particular target system, or what mandatory fields need to be completed, are is contained within the workflow.  Once the workflow has completed its accumulation of data and processing of any business logic and rules, it simply executes the “Create Account” operation and passes the data to it.  The operation then reads the connector definition for the target resource system and executes the appropriate “Create Account” method defined in the connector.  This process separates and isolates the technical requirements for communicating with the target system from the workflow or business process.

...

About the EmpowerID Schema

Cloud Gateway Client for SaaS