Data Model

The Microservices have multiple entities and each entity has a different role to play. The entities and their respective roles are explained.

Following is the entity relationship diagram for the Consent Management Microservice.

Version 1.0

The data models for the Consent Management Microservice are explained.

Consent Entity

This entity performs the following:

  • Stores customer specified consent details.
  • Describes the scope of the access.
  • Grants permission for access.
  • Manages confidential banking data.

The following table explains the various consent attributes.

Attribute Description
Bank Name Holds the name of the bank.
Consent Type Indicates the type of the consent given. Example: Money Management.
Party ID Indicates the Customer ID.
Block Date Indicates the date to block consent.
Consent Block Holds the details required to block consent.
Consent Given Checks if consent is given.
Consent Withdraw Checks if the consent is withdrawn.
Creation Date Indicates the date for creating the consent.
Expires Date Indicates the date of the consent expiry.
Period Days Indicates the number of days the consent will be active.
Withdraw Date Indicates the date of withdrawal of the consent.
Withdraw Notes Contains other details regarding the withdrawal.
company Legal Unit Branch Company code.

Version 2.0

Click the following image to view the data model.

Table Attributes
MasterConsent
  • masterConsentId-PK- record id. The id is given by the user.
  • Description - Description of the MasterConsent record, defined for a contract between the Financial Institution and customers, for the services provided by the Financial Institution.
ConsentType
  • consentTypeId - PK - record id. The id is given by the user, based on masterConsentId and based on the nature of ConsentType which can be:                                             
  • Info - shown just for information and no need any explicit actions from the end users.   
  • Check - show the content and request the user to provide the explicit consent with a check.
  • eSign - show the consent and start the eSignature process.
  • hSign - show the consent and require to be print some documents, to be signed and hard copies to be uploaded into our apps.

  • masterConsentId - FK - id of MasterConsent record.

  • retentionPeriod - how long the personal data is retained.
  • description - Description of the ConsentType record.
TermConditionCode
  • termCondCodeId - PK - record id. The id is autogenerated.
  • termConditionCode - code defined for the TermConditionCode record. The code is given by the user.
  • consentTypeId - FK - id of ConsentType record.
  • title - title of TermConditionCode record.
  • retentionPeriod - how long the personal data is retained.
  • description - desctiption of TermConditionCode record.
InfinityApps
  • appId - PK - record id. The id is given by the user.
  • name - name of the application.
  • description - description of the application.
  • status - can be ACTIVE or INACTIVE.
TermNConditionApps
  • termNConditionAppId-PK- record id. The id is auto generated.
  • termConditionCodeId-FK- id of TermConditionCode.
  • recordappId-FK- id of InfinityApps record.
  • status - can be ACTIVE or INACTIVE.
  • isConsentMandatory - can be TRUE or FALSE.
TermsNConditionContent
  • termsNConditionContentId - PK - record id. The id is auto generated.
  • termConditionAppsId - FK - id of TermNConditionApps record.
  • language - GB / FR / IT / NL / ES / DE.
  • versionNo - record version.
  • description - description of TermNConditionContent record.
  • content - content details.
  • contentType - URL / TEXT.
  • status - ACTIVE / DRAFT / ARCHIVED.
  • legalEntityId - Branch Company code.

Relation between Status and SaveAndPublish in Create API:

TestCase SaveAndPublish StatusExistingRec Updated ExistingRec with Create a new rec with
SaveFirstRecActive true - - status=ACTIVE, version=1.0, autogenerated ID
SaveFirstRecDraft false - - status=DRAFT, version="", autogenerated ID
SaveActiveRecArchived true Active version+=0.1, status=ARCHIVED status=ACTIVE, version=<same>, autogenerated ID
SaveActiveRecDraft false Active - status=DRAFT, version = null, autogenerated ID
SaveDraftRecArchived true Draft if there is no Active record: version = 1.0, Status = ACTIVE -
if exists Active record: version+= 0.1, Status = ARCHIVED
SaveDraftRecDraft false Draft version=null; Status=DRAFT -
PartyConsentDetails
  • partyConsentId - PK - record id. Autogenerated id.
  • masterConsentId - FK - id of MasterConsent record.
  • termsNConditionContentId - FK - id of TermsNConditionContent record.
  • partyId - branchId-accountId .For ex. GB0010001-100100.
  • bankName - name of the bank.
  • externalUserId - external user id.
  • description - description
  • effectiveDate - date when partyConsentDetails record become effective.
  • managingOfficer - managing officer
  • purpose - purpose
  • country - country
  • consentGiven - YES / NO.
  • retentionPeriod - how long the record is retained.
  • expiryDate - the date when partyConsentDetails record expires.
  • isBlocked - partyConsentDetails record is blocked or not. TRUE / FALSE.
  • notes - notes regarding the cause of blocking.
  • blockedFrom - blocked from date.
  • blockedTill - blocked till date.
  • consentWithdraw - consent withdraw.
  • withdrawDate - the date of withdrawal of the PartyConsentDetails.
  • withdrawNotes - withdraw notes.
  • providerReferenceId - provider reference id.
  • status - ACTIVE / INACTIVE / WITHDRAWN.
  • dateLastUpdated - date last updated.
  • branchRef - branch id (GB0010001).
  • channelId - ONLINE / EMAIL.
  • applicationId - Infinity Customer Origination id.
  • legalEntityId - Branch Company code.
ConsentTypeDetails
  • consentDetailsId - PK - record id.
  • partyConsentId - FK - record id of PartyConsentDetails record.
  • consentType - FK - record id of ConsentType record.
  • accountId - account id - For example: 100100.
  • consentGiven - YES / NO.
  • givenDate - date when consent was given.
  • retentionPeriod - how long the consentTypeDetails record is retained.
  • expiryDate - the date when the consentTypeDetails record expire.
  • isBlocked - ConsentTypeDetails record is blocked or not. TRUE / FALSE.
  • blockNotes - notes regarding the cause of blocking.
  • blockedFrom - blocked from date.
  • blockedTill - blocked till date.
  • consentWithdraw - consent withdraw.
  • withdrawNotes - withdraw notes.
  • withdrawDate - the date of withdrawal of the PartyConsentDetails.
  • legalEntityId - Branch Company code
Field Name
|
Application/Table name
Expand/ Collapse
Share
Print

In this topic

Temenos Headquarters SA
2 Rue de l'Ecole-de-Chimie
CH - 1205 Geneva
Switzerland

Copyright © 2020- Temenos Headquarters SA

Contact Us

knowledge@temenos.com

Published on :
Tuesday, May 23, 2023 9:36:49 PM IST