Configuration data

The generic model includes two categories of configuration data. This generic data can be imported into custom applications and then expanded upon as required for use in more specific scenarios.

The categories of configuration data are classification and value. The following sections describe the configuration data that is available for these categories.

Classification schemes

The following classification schemes are included:
  • DC_FLAG
  • DEBIT_CREDIT_FLAG
  • DELETEFLAG
  • EVTPRI
  • EVTSEV
  • EVTTYPE (For more information, see Classification codes.)
  • FILTERPERIOD (For more information, see Date and time search criteria.)
  • MASTERFLAG
  • MSG_VALIDATION
  • OBJREL
  • OBJSTATUS_BAT (For more information, see Classification codes.)
  • OBJSTATUS_PT (For more information, see Classification codes.)
  • OBJSTATUS_TXN (For more information, see Classification codes.)
  • OBJTYPE
  • PREF_DEFAULT_PAGE
  • PREF_LIST_ROWSPAGE
  • PREF_LOCALE (For more information, see User preferences locale selection.)
  • PREF_YN
  • TRANSPORT
  • TIMEZONE

Values

Two types of value categories are included. The value category types are CORE and GUI. The following table shows the value keys that are associated with each value category type.

Table 1. Value keys for the value category types
Value category type Value keys
CORE IN_FRAG_BAT_GUARD

This value is used by EndMapper (v1) as a semaphore to synchronize the threads that are processing inbound fragments in parallel when a batch record may need to be inserted to the database.
IN_FRAG_PT_GUARD

This value is used by the Log PT flow as a semaphore to synchronize the threads that are processing inbound fragments in parallel when a transmission record may need to be inserted to the database.
PROFILING_FLAGS

For more information about this value, see Trace levels.
PROFILING_LEVEL

For more information about this value, see Trace levels.
PROFILING_MAX_SVC_TRACE_SIZE

For more information about this value, see Trace levels.
FORCE_EVENT_ID

This value is used to allocate an ID to every event, even if the event is not being persisted to the database (this mitigates the rare case where one event raised can cause two transitions of an FSM). This defaults to allocating IDs if the entry is absent or unrecognized.
GUI

For more information about this category, see Date and time search criteria.

 FILTERPERIODDEFAULT
LAST5MINS
LAST10MINS
LAST30MINS