Audit Logs

Users' activity in the Temenos DigitalOrigination app is recorded for audit purpose. This data is available in the form of logs in the Spotlight app.

To record each type of user activity, an event must be defined in the database. By default, some subevent types have been defined in the Temenos DigitalOrigination app under the ONBOARDING_APP event type. Any activity related to these subevent types will be recorded and displayed under the Customer Specific logs of the Spotlight app. However, some information that is set as the Personally Identifiable Information (PII) shall not be displayed in the logs for security purpose.

Here is the list of the default subevent types and the corresponding Personally Identifiable Information (PII) information that is hidden.

The following eventsubytes are supported from the 2020.07 version onwards.

Event Triggered	Hidden PII
FUNDINGSTATUS_UPDATE	["Insights", "CIF"]
FUNDINGALLOCATION_UPDATE	[""]
FUNDINGTYPE_UPDATE	[""]
PAYMENTDETAILS_UPDATE	["DebitIBAN", "DebitCurrency", "BankName"]
FUNDINGPRODUCTS_SELECTION_GET	[""]
FUNDINGTYPE_GET	[""]
FUNDINGPRODUCTS_GET	[""]
PRODUCTSELECTION_UPDATE	[""]

Creating a New Event

Apart from the default subevent types, you can create new subevent types to record activity that you want to capture. The process of creating a new subevent type includes the following:

• Create a Subevent in the Data base
• Dispatch the Subevent Type in Fabric
• Configure Personally Identifiable Information (PII)

Create a subevent in Data base

To create a new subevent type , you must add the event and subevent type in the database. To do so, follow these steps:

1. Open the required data base.
2. In dbxdb.eventtype table, add a new record to determine the activity type of ONBOARDING_APP as customer.
3. In dbxdb.eventsubtype table, add a record to determine the new event sub type. This must be mapped to ONBOARDING_APP event type.
4.  In dbxdb.eventconsumertypes table, add the record with event type as ONBOARDING_APP.

Dispatch the subevent type in Fabric

Now that you have added the subevent type in the database, you must dispatch the subevent type. You can do this using an existing postprocessor called LogServicePostprocessor or using the API to dispatch the subevent type.

If you want to dispatch the new subevent by using common postprocessor, LogServicePostprocessor, follow these steps:

1. Sign in to your Quantum Fabric Console. The applications page opens.
2. Select the Origination app.
3. Navigate to Configure Services > Objects > createApplication.
4. In the Advanced section, based on where you have defined the dispatch method, you can add the package and class name of the LogServicePostprocessor in the Postprocessor field and click Save.
5. Publish the app.
   The event subtype has been dispatched.

If you want to dispatch the new subevent by using an API from scratch, follow these steps:

You can dispatch a subevent type from Quantum Fabric in two ways.

• In Object service layer
• In Integration service layer

Dispatch an event in the Object Service Layer

To create an event in the object service layer, follow these steps:

1. Open <folder>\OnboardingServer\Fabric\java\OnBoardingServices\src\main\java\com\temenos\onboarding.
2. Write the dispatch method in the preprocessor or postprocessor of the object layer.
   • If you do not want to send a response directly but want to send it in a JSON data in the object service layer, write the following code. For example, if you want to hide the PII details while displaying the logs, you can use this API.

     public static Result dispatch(FabricRequestManager requestManager, JsonObject responseData, String eventType, String eventSubType, String producer, String StatusId, String Account, String customerId, JsonObject customParams)
     //Here, eventType and event subType are the ones defined in the data base.

   • If you want to display the complete response, write the following code.

     public static Result dispatch(FabricRequestManager requestManager, FabricResponseManager responseManager, String eventType, String eventSubType, String producer, String StatusId, String Account, String customerId, JsonObject customParams)
     //Here, eventType and event subType are the ones defined in the data base.
     

3. Sign in to your Quantum Fabric Console. The applications page opens.
4. Select the Origination app.
5. Navigate to Configure Services > Objects > createApplication.
6. In the Advanced section, based on where you have defined the dispatch method, you can add your package and class name in the Postprocessor or Preprocessor field and click Save.
7. Publish the app.
   The event subtype has been created.

Dispatch an event in the Integration Service Layer

To create an event in the integration service layer, follow these steps:

1. Open <folder>\OnboardingServer\Fabric\java\OnBoardingServices\src\main\java\com\temenos\onboarding.
2. Write the following dispatch method in postprocessor or preprocessor of Integration layer.

   public static Result dispatch(DataControllerRequest requestManager, DataControllerResponse responseManager, String eventType, String eventSubType, String producer, String StatusId, String Account, String user, String appId, JsonObject customParams)

3. Sign in to your Quantum Fabric Console. The applications page opens.
4. Select the Origination app.
5. Navigate to Configure Services > Integration and select the required service.
6. In the Advanced section, add the package and class name in the postprocessor field and click Save.
7. Publish the app.
   The event subtype has been dispatched.

Configure Personally Identifiable Information (PII)

To configure the PII values for the subevent types, you must make changes in the following files:

• AuditLogServiceName.properties
• PIIAuditFieldMapping.json

To set the PII, follow these steps:

1. Open the AuditLogServiceName.properties file. You can find the file at konyonboarding/Fabric/java/OnBoardingServices/src/main/resources/AuditLogServiceName.properties.
2. Map the corresponding audit log event subtype ServiceName_operationName. For example:

   Application_createCoApplicant = ONBOARDING_ISCOAPPICANT

3. Open PIIAuditFieldMapping.json file. You can find the file at konyonboarding/Fabric/java/OnBoardingServices/src/main/resources/PIIAuditFieldMapping.json.

4. Enter the field names that you must hide from the request, ServiceName_operationName_request. For example:

   "Application_createCoApplicant_request" :  ["FirstName","LastName","DateOfBirth","Email","MobileCountryCode","MobileNumber"]

5. Enter the field names that you must hide from the response, ServiceName_operationName_response. For example:

   "Application_createCoApplicant_response" : ["CoAppParty_id"]

Once this event type has been created, when you perform a related activity in the Temenos Digital Origination app, the corresponding activity is recorded. The recorded activity with the corresponding event subtype will be displayed in the Logs section of the Spotlight app. To know more about the Logs, click here.