Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 7 Current »

When a user activates, their credentials are passed to your data source and a user record is received.  We store the users details in the Swift MEAP™ server, and these can be used for distribution.  The example that follows uses a specific field, but any field from the user record may be selected (as long as it is already read / configured in the Swift MEAP server).

Example:

You have the field "Role" stored in your user record, you want to use the "Role" field to define which configuration users receive. 

User record fields

In some servers, the user record is mapped in the console and is available to view in the Map Settings screen (usually mapped to module id 333).  If you do not have a "user" module mapped in your configuration and therefore cannot check the fields available to you, these can be found in the HH_USERS table.  Access Utility->Show Db to view the database and select the HH_USERS table to view the fields stored.

Assuming that a user record has a "Role" field stored in your Data Source, and the field has a value already defined, it may contain three values:

  • Sales
  • Management
  • Other

 

Example flow

If a server contains a Base Configuration, "Role" is defined for multi configuration and a CAD has been created with the name "Management", the activation process is as follows:

  1. User enters their activation email address and data source login credentials
  2. The server reads the user record from the data source, checks if the "Role" field contains a value that matches our configuration names "Management"
    1. If the user record contains "Management", they receive the "Management" cad / configuration
    2. If the user record contains any other value or the value is blank, they will receive the Base Configuration

All servers contain a Base Configuration, and you can create additional configurations based on values in the "role" field not shown in the example above.

 

 

 


  • No labels