Please enable JavaScript to view this site.

Data Cache Data Model Data Cache Forums

Navigation: » No topics above this level «

dc_incoming_messages: Data Cache Incoming Messages

Trickle loading events received from Customer Service for seeding new tables on basis of deltas.

Catalog: Cache

Schema: Invantive

Alias: ime

Primary Keys: ime_id

Label: Incoming Messages

This is a read-only view. The Data Cache API may not support changing the data or the Invantive SQL driver for Data Cache does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Data Cache API.

View Columns

The columns of the view dc_incoming_messages are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

ime_action

char

Action

☐

Code of triggering action in source system where 'U' stands for 'Update', 'D' for 'Delete' and 'I' for 'Insert'.

ime_appl_client_id

string(240)

Application Client ID

☐

OAuth client ID of the application.

ime_appl_partition_c

string(100)

Partition

☐

Unique textual identifier of the partition within the data container.

ime_created_at

string(60)

Created in

☑

The code of the function in the modules table from within which the user created the record. This value will never change after creation of the record.

ime_created_by

string(60)

Created by

☑

Who created the record.

ime_cs_message_key

string

Customer Service Message Key

☑

Customer Service Message Key.

ime_cs_ref_key

decimal

Customer Service Reference Key

☑

Customer Service ID.

ime_data_container_id

string(240)

Data Container ID

☐

Unique textual identifier of the data container.

ime_date_created

datetime

Created at

☑

The system time in UTC at which the record was created. This value will never change after creation of the record.

ime_date_downloaded

datetime

Download Date

☑

Date/time at which the message was downloaded from Customer Service.

ime_date_forwarded

datetime

Date Forwarded

☐

Moment at which the message was processed.

ime_date_modified

datetime

Updated at

☑

The system time in UTC at which the record was last updated. This value will change for every mutation of the record.

ime_date_occurred_server_local

datetime

Date Occurred Server Local Time

☐

Occurrence at the originating server (server local time).

ime_date_occurred

datetime

Date Occurred

☐

Occurrence at the originating server (UTC).

ime_date_received

datetime

Date Received

☑

Receipt moment at Customer Service.

ime_description

string(240)

Description

☐

Description of the event in human-readable language.

ime_forwarded_flag

char

Forwarded

☑

Whether the message was processed.

ime_id

decimal

ID

☑

Unique identifier.

ime_iiid

string(240)

IIID

☐

Invantive Installation ID.

ime_ip_address_external_sender

string(240)

IP Address External Sender

☑

Internet-side IP-address of the message sender.

ime_iuid

string(240)

IUID

☐

Invantive User ID. A physical person can have multiple IUIDs.

ime_license_contract_code

string(240)

License Contract Code

☐

Code of the Invantive license contract for which the message was registered.

ime_message_key

string(240)

Message Key

☐

A unique ID of the message as presented by the sender.

ime_modified_at

string(60)

Updated in

☑

The code of the function in the modules table from within which the user last updated the record. This value will change for every mutation of the record.

ime_modified_by

string(60)

Updated by

☑

The name of the user in the users table whom last updated the record. This value will change for every update of the record.

ime_object_entity

string(240)

Object Entity

☐

Name of the object entity in the source system.

ime_object_key

string(240)

Object Key

☐

Unique identifier of the object entity in the source system.

ime_object_url

string(2000)

Object URL

☐

Browser URL to display the object in the source system.

ime_orig_system_group

string(240)

Original System Group

☐

Reference for identifying the group of records on the system from which it originated. It is commonly used to group records for later validation in an application control.

ime_orig_system_reference

string(240)

Original System Reference

☐

Reference for identifying the record on the system from which it originated.

ime_provider_name

string(240)

Provider Name

☐

Name of the Invantive connector for which the message was received.

ime_receiving_url

string(2000)

Receiving URL

☑

URL on which the request was received including query string.

ime_session_created

string(240)

Session Created

☑

The ID of the session which created the record. This value will not change after insert.

ime_session_id

string(240)

Session ID

☐

Unique ID of the Invantive session that registered the message.

ime_session_modified

string(240)

Session Updated

☑

The ID of the session which last updated the record.

ime_subobject_entity

string(240)

Subobject Entity

☐

Sub-object, such as line with header.

ime_subobject_key

string(240)

Subobject Key

☐

Unique identifier of the sub-object entity in the source system.

ime_table_full_qualified_name

string(240)

Full Qualified Table Name

☐

Full name of the target table.

ime_text_payload

string

Text of Payload

☐

Full contents of the payload received by a HTTP POST.

ime_transaction_created

string(240)

Transaction Created

☑

The ID of the transaction which created the record.

ime_transaction_modified

string(240)

Transaction Updated

☑

The ID of the transaction which last updated the record.

ime_type

string(30)

Type

☑

Currently always 'WEBHOOK'.

ime_verb

string(30)

HTTP Verb

☐

HTTP verb used to register the message.

 

17-08-2023 08:37 Version 22.1.262-BETA+4120

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer