Professional Documents
Culture Documents
2
Document History
Comments:
3
1. Overview
The inline integrity switch is to force integrity check for banks that have not yet gone live. The aim is to catch issues as
soon as they are found and report for suitable remedy action. The purpose of this document is to cover the scope of
the inline integrity switch, the options it supports, and the procedure to enable them.
1.3 Benefits
It helps to find all possible errors in the system before the client goes live. Therefore, immediate actions for the errors
can be done. So as to avoid errors in the system after it is goes live.
4
2. Use cases
2.1 Case 1
When bank is not yet gone LIVE, if parameter record is input, ACTIVITY.INTEGRITY.CHECK attribute record will be only
allowed to set as ERROR since the locking record ENABLE.INTEGRITY.CHECK released by Temenos will be ERROR.
2.2 Case 2
When bank is LIVE, if parameter record is input and even if ENABLE.INTEGRITY.CHECK locking record is available in
the system, the system does integrity check based on the value set in ACTIVITY.INTEGRITY.CHECK field of the
parameter record.
2.3 Case 3
If parameter record is not present, despite the bank being LIVE or not integrity check will happen based on the value
set in the remark field of ENABLE.INTEGRITY.CHECK locking record.
3. Sample Output
3.1 Test Result 1
Enable integrity check locking record
Create a parameter record, input LOG in ACTIVITY.INTEGRITY.CHECK field to check if error thrown stating only value
ERROR allowed in this field since bank is not live yet and remark field of Enable integrity check locking record is set as
ERROR.
5
Create a parameter record, input null in ACTIVITY.INTEGRITY.CHECK field to check if error thrown stating only value
ERROR allowed in this field since bank is not live yet and remark field of Enable integrity check locking record is set as
ERROR.
6
Create a parameter record, input ERROR in ACTIVITY.INTEGRITY.CHECK field and check if the record gets committed
and no error thrown.
Now perform an activity and check if error thrown and transaction gets aborted if there is any integrity error in it.
Inline_AA10001SQ6
8W_BNK_20091223_1547642377.970.csv
7
3.2 Test Result 2
Enable integrity check locking record.
Create a parameter record. Consider the bank is live, so input LIVE in BANK.GO.LIVE.STATUS field, LOG in
ACTIVITY.INTEGRITY.CHECK field and check if the record gets committed and no error is thrown.
8
1. ENABLE.INTEGRITY.CHECK locking record with remark set as ERROR.
Do an activity and check if error thrown and transaction aborted if there is any integrity errors
2. ENABLE.INTEGRITY.CHECK locking record set as LOG (by default the value is ERROR, it is not advised to change
it to LOG or other values)
9
Perform an activity which has integrity errors and check if the record gets committed and the error gets
logged in AA.EXCEPTION.LOG table.
Check AA.EXCEPTION.LOG table to see if log created for the above activity which has integrity error
Inline_AA09357HVX
ZM_BNK_20091223_1547210503.995.csv
4. Reference documents
Refer to the below document to know the detailed overview of the AAssure diagnostic tool, which supports both
inline and offline integrity checks.
Link: AAssure_Diagnostic_Utility.pdf
10
5. Support
If you require more details/clarification about Inline Integrity switch, please feel free to contact the Product AAssure
team at Product_AAssuresupport@temenos.com.
11