0

System Settings - General

  • updated 2 mths ago

Within the System Configuration package there are lots of configuration options, organized into different tabs.

This article explains the items in the General tab (where possible). If an option is not (yet) described here, please contact your LogicNets Project Manager for further information.

Extend socket logging

See the error logging section in the web services call part article here. 

Logging profile

[Request more information from your LogicNets Project Manager]

Log inbound webservice calls

[Request more information from your LogicNets Project Manager]

Log outbound webservice calls

[Request more information from your LogicNets Project Manager]

Enable profiler

[Request more information from your LogicNets Project Manager]

Enable session timeout timer

See this article for more information on the session timeout mechansim

Session timeout

See this article for more information on session timeout.

Refresh session token

[Request more information from your LogicNets Project Manager]

Default data model scope

[Request more information from your LogicNets Project Manager]

Cookie consent policy

[Request more information from your LogicNets Project Manager]

Move changelog data to enterprise database 

(Rel 8.1+) [Request more information from your LogicNets Project Manager]

Changelog data pruning

(Rel 8.1+) The changelog table is the source of the data in the Standard Reporting package and can be used for custom reporting applications (requires specific modelling, custom views etc.). Each system or application event adds a record to the table, and therefore the table can grow to a significant size over time (depending on use and scope of LogicNets applications)

This feature allows the System Administrator to prune down any records that are beyond a given timeframe, as follows:

  • the default setting is OFF, and no records will be deleted from the changelog table
  • a value of 366 will insure there is 12 months of changelog events stored in the table, including leap years
  • a value of 549 will insure there is 18 months of changelog events stored in the table, including leap years

Records date-stamped outside of the number of days specified are deleted on a daily basis.

It is recommended to limit the changelog table with large and/or heavy use applications, especially those using the LogicNets Assessment Framework. If the table grows exceptionally large, the first noticeable impact will be that the Standard Reporting package will take longer to present information on screen and recalculate when changing user inputs. Also note that:

  • Logging can be substantially reduced by turning this off in the project settings for each Assessment Framework project - see this article)
  • The changelog is NOT used as the standard means of backup for LogicNets-hosted applications. 
Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 2 mths agoLast active
  • 11Views
  • 1 Following

Home