What are User Tables and User Pages and how can they be used?
User Tables and User Pages give Equus Platform users a seemingly infinite number of ways to customize their Equus Platform systems to fit their own needs.
The User Table Configuration page allows advanced users to configure and add new tables to the database. User Tables can be used to store single or multiple rows of data in the Equus Platform which do not have a natural home. Users can create a new set of "fields" which can then either reside in the database just as a path to be imported into or can be made visible by adding them to a User Page.
User Tables and User Pages are useful for:
Importing and maintaining large amounts of data which is needed for downstream processes, e.g. calculations
Creating client specific pages at the assignment, company or system level
Adding additional information to Authorizations and Requests
User Tables and User Pages are configured at the system level, however they can be set to appear at the system, company or assignment level.
A user can also be matched to an authorization table - this means that if data is inputted at the authorization, it will push down to a matching assignment table - this is important in cases where additional information is being requested via the authorization.
High Level Summary of User Page Configuration
Configure Security for the User Page if necessary and/or
Configure for the Portal, if desired.
Things to Note
User Tables should always be configured prior to creating the corresponding User Page
The number of User Tables allowed in the Equus Platform is unlimited, however User Pages are limited to 40 user pages system-wide.
For fields indicating a status, use a Boolean type rather than a Classification Lookup type
Minimize the use of special characters when defining the User Table's Display Name
When creating SQL logic in a User Report and you encounter an error message "Could not be located in this report’s tables", this could be a result of having a special characters in the User Table Display Name i.e. "Assignment - Additional Inputs". When this happens, instead of using the Equus Platform Field Label try using the User Table Database Field Name (as shown in DDMO). Also, if you are using a User Table field in the filter section, add the User Table Database Field Name in the report by creating a Custom SQL Field. i.e
Equus Platform Field Label - [Assignment - Additional Inputs: Name]
User Table Database Field Name - [UT_ASSIGNMENT_ADDITIONTAL_INPUTS!NAME]
Making changes to the Display Name of any user tables referencing a Document field will result in the error "Too many records returned by single-record query" appears. A workaround will be made available in a future release.
To track changes when a User Page is locked, the following fields can be reported on from the corresponding User Table: LOCKED, LOCKED_BY, LOCKED_DATE, and LOCKED_SOURCE.
Things to note when using Generic Imports
Once a User Table is created, it can be imported into the Equus Platform at system/company level using a Generic Import.
Generic imports are processed at the system level. If importing into a company user table, then the company ID must be included in the import file
If importing into lookup field, then the lookup value must be matched using the caption header "|lookupvalue=true"
Country - imported data cannot use country names (France). The country's 3 letter ISO Code (FRA) must match the values in the Equus Platform. Codes can be validated by reviewing the Countries screen at the system level.
When importing into a User Table that already contains data, any field which is left blank in the data row will be ignored. Such fields will not be given blank values in the database (they will not be updated at all). If you need the field to be set to “null” in the database, then specify the literal text “<blank>” in the value of the field. In the case of inserts, blank fields and fields that contain the text “<blank>” will both result in null values in the database,