Global system settings for Unifi.
The Properties module is where you will find the global system settings for the Unifi application.
Control all integrations using this master switch.
Allow users with this role to read bond records for informational purposes. Intended for giving access using related bond lists on the process tables. It does not expose the application menu. For greater control use the x_snd_eb.user role**.**
Choose the required logging level for the application: 'debug' writes all logs to the database, 'info' writes informational, warning and error logs to the database.
Debug mode is extremely resource intensive. Only choose 'debug' for troubleshooting when session debugging is not adequate.
Use for general integration debugging to capture debug messages in the console in addition to info, warn and error.
Enable input/output trace logs for functions that have been wrapped for tracing.
Requires Debug mode to be enabled.
Enable input/output trace logs for core application methods. This produces extremely verbose logs from all core scripts which will help ShareLogic Ltd if you ever run into trouble with the app.
Not required for general integration debugging.
The choices are:
Off: No debug mode is active. Performance is not affected.
Silent: Enhanced exception handling and error logs. Performance is slightly affected.
Trace: Functional profiling in addition to enhanced exception handling and error logs. Peformance is affected. Requires Trace mode to be enabled.
Turns on Activity Logs for Service Portal interfaces.
How many days should Activity Logs be kept before being removed?
Default: 7.
Configure which columns are always shown on lists in the Unifi Integration Designer portal. Multiple columns should be separated by a comma.
How many days should orphaned transactions be kept before they are removed?
Default: 7.
What is the maximum number of orphaned transactions to remove at any one time?
Default: 1000.
How many hours should successful heartbeat transactions be kept for before they are removed?
Default: 24
How many days should failed heartbeat transactions be kept for before they are removed?
Default: 90
Enables logs and payloads generated by Unifi transaction processing to be attached to transactional records.
Logging attachments this way is now deprecated and has been replaced by the Unifi portal and Activity Log.
Control whether to allow files to be created in the Unifi scope on Unifi tables (prefix x_snd_eb_)
Default: false
The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day.
The link to the ServiceNow System Logs shows errors and warnings from the current day, and is the place to look in the case of something catastrophic happening outside of Unifi, or something that isn't captured in Activity Logs (effectively providing an additional back up).
Scheduled Scripts are automatically created by the system to perform tasks.
The Scheduled Scripts module displays the scripts which are automatically created by the system in order to perform tasks. These scripts generate log entries in the Activity Logs each time they run.
The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day.
Not to be confused with the System logs, the Activity Logs module displays all the entries to the Unifi Activity Log table from the current day. This reduces the clutter in the System logs table by bringing all the Unifi log entries together in one place, providing contextual links to the records.
Clicking into the records, you will very quickly discover that the level of detail and clarity provided in the Activity Logs makes them of even greater value. It is the place to look when debugging.
Below is an excerpt from one of the log entries in the Activity Logs:
A Data Store is simply a key-value pair stored in the database that is available to all records in the system.
Use Data Stores to easily make variables persistent and retrievable.
Data Stores are used primarily in Message Scripts and Poll Processor scripts when you want to get and set functional data that is relevent to the integration but does not belong on the target record.
This is particularly handy in a uni-directional integration where polling the remote system is necessary. You can store data such as:
The last time a request was made
Identifiers that have been seen before
Watermarks
Use getData and setData to work with simple string-like data.
You can also work with objects just as easily by using getDataObject and setDataObject. These functions automatically take care of encoding the object for database storage and decoding it for JavaScript usage again.