Skip to main content

 

Eptura Knowledge Center

AMAG Symmetry - Notes

  1. Last updated
  2. Save as PDF

Timing of changes within AMAG

- adding/deleting/updating users and access rights

When making changes that would require write access (add/update/delete) via the AMAG API, they are added to an import process that will initially add them into the DataImportTable in the multiMAXImport database in the default SQL Server instance. This slows down the total time it takes for these changes to take effect.

We force any such updates to be immediate and the import process within AMAG then determines how long this will take.

The MultiMaxImport process has a 10 second default that can be overridden by updating the multimax.ini file in C:\\ProgramData\\Security Management System.

You can update the below setting - the minimum possible value is 3 seconds:

[Scheduler]
ImportMonitoringTimeFrame=3

 If you do not see the above entry in the multimax.ini file you may add it in

By updating the default ImportMonitoringTimeFrame value to 3, the process is still within our expected maximum of 20 seconds, but any additional delays local to the setup (network latency, etc.) could take this over our usual limits.

If unsure about this process we recommend you discuss this with AMAG Support.

Dummy card in Cardholder profile?

Cardholders cannot be created in AMAG without a card. We therefore add a dummy card when adding a user - this uses the Cardholder ID as the token number (7 digits). When Proxyclick generates a QR card number (8 digits) this will be seen in the user profile as a second card.

Users are not entered by Proxyclick as “Visitors”

Within AMAG the Visitors model only allows for a single credential. For this reason we enter each user as a Card Holder.

Data Connect Module and XML Open Integration Module

The Data Connect Module is the user import system. The XML Open Integration Module is the API (WCF Service). Both are required.

Access Codes - character limit

AMAG set an Access Code name limit of 40 characters.

If using our custom access level functionality (custom field or company specific permissions) this will need to be kept in mind as we would append the custom field and/or company info from Proxyclick to create a custom access code in AMAG: if the overall group name is then too long this will cause an error.

We have reduced the length of our default access code names to help accommodate this:

"Proxyclick - checked-in" is listed as "PXC checked-in", for example.