Model / INT

Module

INT — Universal Interaction Journal

9 tables defined at field level · 187 fields.

TableDescriptionFields
ACDOCIUniversal Interaction Journal. The same idea as ACDOCA, applied to human interaction: one line per interaction, carrying every dimension that interaction belongs to, whatever system of recor…64
CHNLChannel master. The medium an interaction travelled over — voice, chat, email, portal, field visit, in person, satellite link, letter. Held as master data so that a channel nobody has though…10
IJSATSatellite and remote-link extension of the interaction journal. An interaction carried over a satellite terminal has properties no terrestrial channel has — a pass window, an elevation angle…27
IJTELTelephony extension of the interaction journal. Keyed on the interaction line, so a voice interaction carries its call detail without every other channel inheriting empty columns. Numbers ar…26
ITYPInteraction type master. What kind of human interaction the line records: a case, an incident, a call, a meeting, a task, a service request, a home visit, a sacrament, a class taught. The li…8
PARTYParty registry. Pseudonymous keys for the humans and organisations on either side of an interaction. The registry holds the key, the role, the member it belongs to and the consent governing …15
STSMAPStatus crosswalk. Salesforce case statuses, ServiceNow incident states, telephony dispositions and a parish register's own words all resolve to one canonical status set, while the source val…9
SYSRCSystem of record registry. Every source the interaction journal mirrors from: a Salesforce org, a ServiceNow instance, a telephony platform, a satellite ground segment, a parish register. Re…14
XWALKField crosswalk registry. The combined schema is not achieved by forcing Salesforce and ServiceNow to agree; it is achieved by recording, field by field, how each one maps onto the canonical…14