Home > Alerts > Users > User Log In

User Log In

The major change implemented in version 1.1 of the Alerts Engine was to add support for user log in and security levels. This includes the ability to assign specific portals to specific users and to restrict access to maintenance functions and so on within the Alerts Engine.

Database Changes

Two new tables were added to the Alerts Engine database:

A default user TOREXADMIN is added to the users table and the default security levels required for different maintenance functions.

Security Levels

There are 4 security levels supported by the Alerts Engine. These are:

The default user TOREXADMIN is added as an administrator and has access to all functions. This user account should be changed immediately upon installation – at least to change the password.

For each of 6 areas of maintenance in the Alerts Engine, you can specify a minimum security level a user must have to View, Edit and Delete the function. The default levels of security required are as indicated in the table below:

Function

View

Edit

Delete

Alerts

Portal Manager

Alert Manager

Administrator

Portals

Portal Manager

Portal Manager

Administrator

Users

Alert Manager

Administrator

Administrator

Security

Administrator

Administrator

Administrator

Passwords

Administrator

Administrator

Administrator

Portal (view a portal)

Viewer

N/A

N/A

The security levels can be managed by an authorised user with a new maintenance function – see Managing Security Levels.

Importing User Details

When you add the required licence information to a new Alerts Engine database, the code will import users from the reports database using the details specified in the properties file. [There is also an “import users” function supported in the user maintenance screens, which could be used if you have upgraded an earlier version of the Alerts Engine.]

These properties specify the table and records within the reports database to be used to set up user records in the alerts database. The sample entries included in the properties file will import entries in the MICROS BE USERCODE table.

These properties link fields in the BE table to the equivalent fields in the AEUSERS table.

importusers.table =usercode

importusers.key =strUserCode

importusers.type =intLevel

importusers.email =strEmail

importusers.phone =strPhone

importusers.firstName =strUserName

importusers.lastName =

Then there are properties to map a user type field in the imported table to the alerts security level. The BE USERCODE table has an INTLEVEL field which takes values from 1 to 9, and these properties map this integer value to the equivalent alerts security level.

importuserstype.1=1

importuserstype.2=1

importuserstype.3=2

importuserstype.4=2

importuserstype.5=3

importuserstype.6=3

importuserstype.7=3

importuserstype.8=4

importuserstype.9=4

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)