The SaaS tab provides information about the program's configuration when it runs as 'Software as a Service.' None of the settings on this tab may be edited.
Field |
Function |
Software as a Service |
Indicates whether the program is being run as Software as a Service. This setting is based on the License Codes. When this setting is True, other settings are displayed below. |
The following settings appear only if the Software as a Service setting is marked True. Some of these settings are specific to this tab; others are transfered to this tab from other tabs.
Field |
Function |
Setting Moved From |
Comma Delimited List of servers running WebCitizen |
Should include the URL to the Citizen Portal application (e.g., http://127.0.0.1:2295/gbamswebcitizen). If there is more than one web server for Citizen Portal, enter each URL, separated by commas. |
Website |
Default Location for map exports |
The network path to the location in which Map images should be saved when creating a new Work Order, Request, etc., with an attached map. |
GIS Desktop |
Enable S3 integration for document storage |
Allows the Lucity Document Server to store documents to the Amazon Cloud. |
|
Favor configuration over performance for business rules |
When changes are made to field properties (such as mask, required, editable) in the Desktop, IIS must be reset in order for those changes to be pushed into Lucity Web. Enabling this rule allows these changes to be pushed into Lucity Web by clearing the web cache, despite the fact that this may cause a significant drop in performance (15-20%). |
Web Performance |
GIS/Lucity Edit Integration - Disable all updates to the geodatabase from Lucity |
Prevents the geodatabase from being updated with edits made in Lucity Desktop and Web. |
GIS Edit Integration |
Internal Website |
The path to Lucity Web. The paths for the internal web sites should almost never be changed. ONLY edit these fields if there are multiple web servers and one needs to be designated to support the Lucity Administration for Web Apps Previews. |
Website |
Name of Bucket where S3 documents are stored |
The name of the Amazon Cloud S3 bucket that the Lucity Document Server uses if it is storing documents. |
|
Path where uploaded documents are stored (Citizen) |
The network path for the location in which documents from Citizen Portal will be stored. (Applies to Citizen Portal.) |
Documents |
Path where uploaded documents are stored (Internal) |
The network path for the location in which documents from Lucity Web and Mobile will be stored. (Applies to Lucity Web.) |
Documents |
Region endpoint where S3 bucket resides |
The S3 endpoint that stores the bucket in which the Lucity Document Server will store documents. |
|
URL for Lucity Custom Web Integrations |
The URL for a custom integration purchased for customer lookups. This information is provided by Lucity during the implementation of the custom product. |
Website |
Url for the Lucity Mobile Server Virtual directory (Externally accessible version) |
The externally accessible URL for Lucity Mobile Server, which is used to connect to Lucity Mobile from outside the network firewall. |
Mobile |
Url for the Lucity Mobile Server Virtual Directory (Internally accessible version) |
The internally accessible URL for the Lucity Mobile Server, which is used to download data to users' tablets using local wifi before users go offline. |
Mobile |
Website Theme |
The look of the web page. "Default" is the standard Lucity setting. |
Website |
Windows Authentication Website |
A path to Lucity Web that first accesses a launcher page that will try to log the person currently logged into the computer into Lucity. The paths for the internal websites should almost never be changed. |
Website |