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 6 Next »

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, these can be used for distribution.  An example follows using a specific field but any field from the user record can be selected (as long as it is read / configured in the Swift MEAP server).

For example, if you have "Role" stored in your user record, you can 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 and in your data source, it can contain three values:

  • Sales
  • Management
  • Other

All servers contain a Base Configuration, you can create additional configurations that match the values above.

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

 

 

 

 


  • No labels