Field
|
Function
|
 Permissions
|
Allow All Users Access to All Views
|
Removes the requirement that users be in a group assigned to a view in order to access the view. This gives all users access to all views in any module they have security permission to.
|
App Admin
|
Comma delimited list of user names that should not be tracked in AuditLogons Table
|
Enter Lucity usernames here to bypass tracking the successful logon of those users in the AuditLogons table.
- Intended for applications developed by clients, particularly REST applications, that may log in frequently (several times per second).
|
IT Admin
|
Date format for Notifications
Default: Short
|
Indicates which date format should be used when creating web notifications.
Example
- Short = 01/01/2015
- Long = Monday, January 1st, 2015
|
App Admin
|
Days to keep data in login auditing table (0 to maintain all history)
|
Indicates the number of days of login history for the Desktop or Web application that the system should retain in the AUDITLOGONS table in the User database.
|
IT Admin
|
Days to keep data in the event track table (0 to maintain all history)
|
Controls how many days records are stored in the Event Track table. The Event Track table is used in third-party integrations to determine when records have been edited in specific Work modules.
|
App Admin
|
ELA email to send expiration warning emails
|
Specifies the email address that should receive warning emails when an ELA license is about to expire.
|
App Admin
|
ELA number of days before expiration when warnings begin
|
Indicates the number of days before an ELA license expires that the system should start sending out warning emails.
|
App Admin
|
Enable Lucity Spatial
|
When enabled, tells the Lucity Spatial Updater Service (part of the Lucity Services) to update the Work Order and Request tables with spatial information.
|
App Admin
|
Flags to Alter Application Behavior for Rare Cases. Lucity Support will let you know if any may apply for your installation
|
Custom flags which direct Lucity code to apply a special behavior. Do not change the value in this setting except under direction from Lucity support or implementation.
|
IT Admin
|
How Many Days of Records Should be Kept in Audit Log
Default: 365
|
Controls how many days of records are left in the audit log. The audit log contains events such as record deletes, feature splits and merges, and other limited functions.
|
App Admin
|
How Many Days of Records Should be Kept in the Activity Log Table
Default: 365
|
Controls how many days of records are left in the LACTIVITYLOG table. The log contains a record of activities that occurred in any Lucity application.
|
IT Admin
|
How Many Days of Records Should be Kept in the Error Log Table
Default: 90
|
Controls how many days of records are left in the LERRORLOG table. The error log contains a copy of all the records written to any rolling.log that had a severity level of ERROR.
|
IT Admin
|
Inactive User Licenses Expiration in Minutes (recommended value=60)
|
The Web application limits the number of active users to the number of product licenses. This setting releases a user's licenses if the product has been idle for the time indicated. 60 minutes is the recommended time frame.
|
IT Admin
|
Location of the Lucity Help files for this system
|
Identifies the URL where the Lucity help files are stored.
This option defaults to the Lucity help site but can be modified by agencies that cannot give users access to the Internet. These agencies can request a copy of the Lucity Web help files and host them over their local network. An administrator must then enter the location of the root folder storing the help files so that all of the help links continue to work.
|
IT Admin
|
Max amount of days to process spatial history
|
Tells the Lucity Spatial Updater Service how many days back from the current date that it should check for Work Orders and Requests that need spatial information.
Note: The service can only update data back to Lucity version 7.40.
|
App Admin
|
Maximum number of records which may be updated using global edit using the Business Rules option
|
The most records during a global update query that can be updated at 1 time using the Business Rules option. If a child record is being updated the parent record is counted against this maximum.
|
App Admin
|
Maximum number of records which may be updated using global edit using the Direct SQL option
|
The most records during a global update query that can be updated at 1 time using the Direct SQL option. If a child record is being updated the parent record is counted against this maximum.
|
App Admin
|
Send Data Statistics to Lucity
|
Allows the Lucity system to automatically send monthly data statistics to Lucity. This provides us with information about how the software is being used. The statistics are sent on the first of each month.
|
IT Admin
|
Send weekly emails of orphaned documents and report files
|
Sends an email once a week to the users listed in the List of email addresses for system health notifications setting on the Email tab.
|
App Admin
|
Should detailed audit logging write to the audit log table
|
Determines whether user-initiated actions such as global updates or record deletions are included in the Audit Log table.
Note: The Audit Log is not automatically truncated or cleaned up. While Audit Logging is not excessive when enabled, it can produce a large table that requires periodic management.
|
App Admin
|