CCMS Low-Level Design

Court Case Management System

Version 1.0

Authors: CCMS Team

Last Modified Date: Thursday, 11th November 2020

1
 CCMS Low-Level Design

Document Control Information

Document Author: CCMS Team

Document Owner: Mashreq

Project Manager: Sandeep T

Document Revision History:

Version Date Author Summary of changes

0.1 11th Nov, 2020 CCMS Team Documented the low-level design for CCMS Portal.

Document Reviewers & Approvers:

Name Role Reviewer Reviewer &

Only Approver

Ashis Sethy Eidiko EA NA Yes

2
 CCMS Low-Level Design

Contents

1 Introduction......................................................................................................................................................6
1.1 Purpose.....................................................................................................................................................6
1.2 Scope........................................................................................................................................................6
1.3 Not in Scope.............................................................................................................................................6
1.4 Intended Audience...................................................................................................................................6
1.5 Overview..................................................................................................................................................6
2 Application Landscape......................................................................................................................................7
2.1 System Architecture.................................................................................................................................9
2.2 Solution Architecture..............................................................................................................................10
3 To-Be Business Process...................................................................................................................................10
3.1 Main Process................................................................................................................................................10
4 Data Model:.......................................................................................................................................................11
4.1 Business Object Model.................................................................................................................................11
4.2 Entity Relationship Model............................................................................................................................13
4.3 Teams...........................................................................................................................................................14
5 Service Interface Definition............................................................................................................................14
5.1 Internal Services.....................................................................................................................................14
5.1.1 BPM Services..................................................................................................................................14
5.2 External Services.....................................................................................................................................15
5.3 Services exposed in CCMS......................................................................................................................16
5.4 Sending, receiving and processing emails...............................................................................................16
5.5 Home Page.............................................................................................................................................16
5.6 Maker Process........................................................................................................................................17
5.7 Checker Process......................................................................................................................................19
5.8 Dubai Portal Email Notification...............................................................................................................20
5.9 RM Email Notification.............................................................................................................................20
5.10 TMS Queue Email Notification................................................................................................................20
5.11 Exception Email Notification...................................................................................................................20
5.12 Deployment Plan....................................................................................................................................20

3
 CCMS Low-Level Design

6. User Interface Design.....................................................................................................................................21

6.1 Coach Views............................................................................................................................................21
6.2 Coaches..................................................................................................................................................21
6.2.1 Maker Screen..........................................................................................................................................21
6.2.2 Checker Screen.......................................................................................................................................35
6.2.3 Verify EDMS Status Maker......................................................................................................................36
6.2.4 CCMS View Screen..................................................................................................................................36
7 Exception Handling.........................................................................................................................................37
8 Auditing..........................................................................................................................................................39
9 Logging...........................................................................................................................................................39
10 Data Persistence.............................................................................................................................................39
Instance Purge Timeline...........................................................................................................................39
11 Design Decisions.............................................................................................................................................40
12 Reusability......................................................................................................................................................42
13 Additional Capacity Planning..........................................................................................................................42
14 Document Retention Policy............................................................................................................................43
15 Technical Debts...............................................................................................................................................43

4
 CCMS Low-Level Design

Glossary:

Acronym/Term Description

BPMN Business Process Model and Notation

IBM BAW IBM Business Automation Workflow

SOR Database System of Record

LDAP Lightweight Directory Access Protocol

CCMS Court Case Management System.

EDMS Enterprise Document Management System

MFT Managed File Transfer aka NFS

RPA Blue Prism based Robotic Process Automation

5
 CCMS Low-Level Design

1 Introduction
1.1 Purpose
This document provides a comprehensive architectural overview of the Court Letter system, using number
of different architectural views to depict different aspects of the system. It is intended to capture and
convey the significant architectural decisions, which have been made on the system. This also captures the
Low-Level Design which is common across the project.

1.2 Scope
This design document is intended to articulate the Solution design of the Court Letter Application. The
solution architecture will evolve through multiple iterations within the System Development Lifecycle
(SDLC).

CCMS Product Backlog.

1.3 Not in Scope

 Handling of Arabic character based Case-Reference Numbers : Any case which has a case
reference number in non-Latin characters will not be processed through this solution.

1.4 Intended Audience

Name Role Organization

Suresh T Enterprise Architect Mashreq
Rajanikanth Reddy Kongari Technology Manager Mashreq
Sandeep T Platform Owner Mashreq
Srinivas Pilli EA Eidiko
Ashis Sethy BPM Architect Eidiko

1.5 Overview

The Court Letter Solution will be implemented using the IBM BAW Platform. The diagram below depicts
the conceptual Solution Architecture leveraging IBM BAW platform.

6
 CCMS Low-Level Design

The process has following business functionalities:

SL.No Business Function Description

1 CCMS Maker

2 CCMS Checker

2 Application Landscape
The Court Letter Generation Process follows a layered architecture to provide separation of responsibilities
among pieces of the architecture. The important components are:

 BAW (IBM BAW)

 Java (Micro Services using Spring Boot)
 RPA (BluePrism)
 Atomic (Shell Scripts)

BAW
BAW functions as the workflow engine to facilitate the maker-checker process; which in turn produces
the final response to be provided for a given court case. The BAW workflow is defined using IBM BAW
product. IBM BAW integrates with Java, Application Database and OMW-Flex to facilitate the
completion of the maker-checker process.

IBM BAW deliverables and its dependencies are shown below:

 Snapshot for the Court Case Management System (CCMS) Process Application

Dependent Toolkits:

o Content Management (8.6.0.0)

o System Data (8.6.0.0)
o UI Toolkit (8.6.0.0)

Java – (Microservice)
Java/J2EE is deployed on IBM Websphere Application Server and serves as the main processing engine
for communication between RPA, EDMS, Email Server and BPM. It also handles computing intensive
jobs like generation of PDF files, processing of the incoming on-demand requests from RPA and
supporting RPA daily batches.

7
 CCMS Low-Level Design

RPA
RPA aims at simulating the lookup of new cases on the CCMS portal and responding back to the same
when the appropriate response has been decided through the BPM maker-checker workflow. RPA
operates 3 stages namely;

1. Stage 1: Pull data and documents from the CCMS portal for cases that has not been processed
yet. Use the “maker” credentials for the same.
2. Stage 2: Push data and documents back to the CCMS portal after a response has been finalized.
Use the “maker” credentials for the same.
3. Stage 3: Approve the case for which the Stage 2 has been completed. Use the “checker”
credentials for the same.

Deliverables for the RPA component

1. CCMS_Stage1.bprelease
2. CCMS_Stage2.bprelease
3. CCMS_Stage3.bprelease

Atomic
Atomic is used to facilitate file transfer between the RPA and Java NFS. This consists of a series of shell
scripts that can be invoked on demand requesting for the files/folders to be transferred from the
source to the destination NFS.

2.1 External Events

 Cases are posted on CCMS Portal, available for Mashreq to read and respond.

2.2 Internal Events

 RPA extracts cases along with attachment from CCMS Portal.
 RPA notifies Java and Java downloads the attachments from RPA servers using Atomic.
 Java will extract the details and creates a case in BPM.
 BPM Component will fetch details of Customer and Accounts from BIS portal via Java layer and Flex
cube via OMW layer and show on maker screen.
 All the case data will be available on Maker Screen with details provided by RPA from CCMS Portal.
 Maker will review the case details.
 Once The “Maker” finishes his/her task, a task is created for checker and relevant case response
documents are generated using Java Services (PDF Generator).
 Java transmits the documents to EDMS system and pushes the same to RPA servers.
 Java persists the case related metadata into Application Schema.
 BPM upon receipt of the Java acknowledgement BPM will create the EDMS Based on the Maker
action for Account Freeze/unfreeze/amount block/amount unblock by moving documents to the
EDMS via java layer. BPM completes the instance.
 A new task is created for the Checker showing all the details available along with the documents.
 Once the “checker” approves, BPM passes on relevant information to Java Case Response for CCMS
Updates.
 RPA calls Java as per a predefined schedule to get response data for all cases since the last pull.

8
 CCMS Low-Level Design

 RPA uploads the documents and necessary metadata to CCMS portal and updates the status back
to Java layer, which relays the same to the BPM environment.

The application Integrates with following systems :

External System Description

EDMS This system will be used to store documents
OMW All the calls to core banking system will go via OMW
RPA RPA extracts cases along with attachment from CCMS
Portal
BIS Portal Search This system will provide details of customer based on
name.
Prime System This system will provide all details of customers credit
card details.
2.1 System Architecture

9
 CCMS Low-Level Design

2.2 Solution Architecture

3 To-Be Business Process

3.1 Main Process:

10
 CCMS Low-Level Design

4 Data Model:
4.1 Business Object Model:
Instances created in CCMS utilize the following major business objects.

1. CCMS_Account_SummaryDetails_BO
2. CCMS_AccountBlockDetailsBO
3. CCMS_AccountBLockSummaryDetails_BO
4. CCMS_AccountDetails
5. CCMS_AccountStatementDetails_BO
6. CCMS_AuditTrials
7. CCMS_BISPortalDataBO
8. CCMS_BISPortalRequestParam
9. CCMS_CancellationOfStandingInstruction
10. CCMS_CaseDetails
11. CCMS_CertificateDetails_BO
12. CCMS_CifBo
13. CCMS_Comments
14. CCMS_Correspondense_Details
15. CCMS_Court_Comp_Req_ReqTypeBO
16. CCMS_Court_Comp_Req_ReqTypeBO2
17. CCMS_CourtComplaintDetails
18. CCMS_CourtLetterResponseDetailsBO
19. CCMS_CourtRequestDetails
20. CCMS_CourtRequestTypeDetails
21. CCMS_CourtResponseDetails
22. CCMS_CourtsTemplateBO
23. CCMS_CourtTemplateTabBO
24. CCMS_CreditCardSummary_BO
25. CCMS_CreditCradStatementDetails_BO
26. CCMS_CustomerDetailsResponse_BO
27. CCMS_CustomerSearchDetails
28. CCMS_CustomerSearchRequest
29. CCMS_DocTagg
30. CCMS_DueDateBO
31. CCMS_EdmsDocDownloadBO
32. CCMS_ExceptionDetails_BO
33. CCMS_InwardRemittance_Bo
34. CCMS_InwardRemittanceTabBO
35. CCMS_IslamicAccountDetails_BO
36. CCMS_LetterData
37. CCMS_Loan_Details_BO
38. CCMS_LoanDetails
39. CCMS_MMCDetails_BO

11
 CCMS Low-Level Design

40. CCMS_OutStandingAmount_BO
41. CCMS_OutwardRemittance_BO
42. CCMS_PayorderCancelation_Reissue
43. CCMS_POCancellationFormBO
44. CCMS_POCancellationTabBO
45. CCMS_QueryloanDetails_BO
46. CCMS_ReassignSearchBO
47. CCMS_Response_BO
48. CCMS_ResponseDocs
49. CCMS_ScreenParamBO
50. CCMS_SearchCriteriaBO
51. CCMS_SearchDetails
52. CCMS_SearchParameters
53. CCMS_SearchResult
54. CCMS_ServiceLog
55. CCMS_StandingInstructionBo
56. CCMS_TaskDetailsBO
57. CCMS_TaskReassignmentAuditBO
58. CCMS_TemplateAccountDetails
59. CCMS_TransactionDetails
60. CCMSCourtTemplateVisibilityBO
61. CCMSInwardRemittanceMMCPayOrderDetails_BO
62. CustomerSearchBO

12
 CCMS Low-Level Design

4.2 Entity Relationship Model:

Besides the 6 core tables shown above, the following common (shared framework) tables are used by
the application:
1. CCMS_ACCOUNT_BLOCK_DETAILS
2. CCMS_ACCOUNT_DETAILS
3. CCMS_ACCOUNT_STATEMENT
4. CCMS_ACCOUNT_SUMMARY
5. CCMS_APP_DATA
6. CCMS_AUDIT_TRIALS
7. CCMS_BIS_PORTAL_DATA
8. CCMS_CASE_DETAILS
9. CCMS_COMMENTS
10. CCMS_CONFIG_DATA
11. CCMS_CORRESPONDENCE
12. CCMS_COURT_BENEFICIARY
13. CCMS_COURT_COMPLAINT_DETAILS
14. CCMS_COURT_REQUEST_DETAILS
15. CCMS_COURT_REQUESTTYPE_DETAILS
16. CCMS_COURT_RESPONSE_DETAILS
17. CCMS_CREDIT_CARD_SUMMARY

13
 CCMS Low-Level Design

18. CCMS_CUSTOMER_DETAILS
19. CCMS_CUSTOMER_SEARCH_DETAILS
20. CCMS_DOC_MIME_TYPES
21. CCMS_DOCTAGG
22. CCMS_DUBAIPORTAL_EMAILCONTENT
23. CCMS_EDMS_DETAILS
24. CCMS_EDMS_DOC_DOWNLOAD
25. CCMS_JAVA_HTML_TEMPLATE
26. CCMS_JAVA_RPA_DATA
27. CCMS_JAVA_SERVICE_AUDIT
28. CCMS_LETTER_DATA
29. CCMS_LOAN_DETAILS
30. CCMS_LOAN_DETAILS_NEW
31. CCMS_LOAN_OUTSTANDING_DETAILS
32. CCMS_MMC_DETAILS
33. CCMS_PRIME_TRANSACTION
34. CCMS_REPLY_ATTACHMENT
35. CCMS_SCREEN_PARAM
36. CCMS_SERVICE_LOG
37. CCMS_TASK_REASSIGNMENT_AUDIT
38. CCMS_TEMPLATE_CONFIGURATION

4.3 Teams
Following actors will be working on case based on role.

Teams
CCMSCamMaker
CCMSCamChecker
CCMSAssigner

5. Service Components & Service Interface Definition

5.1 Internal Services
5.1.1 BPM Services

Service Name Protocol Invocation Style Invoked from tasks

CCMS Home Page
CCMSViewScreen

14
 CCMS Low-Level Design

5.2 External Services

OMW Business Functionality Service Description URL Request, Response, Fault

Service Data Model
Name

Customer Get CIF id’s http://

Search www.mbcdm.customerservices.com/
customerSearch

Account Get all accounts (basic http://www.mbcdm.accountservices.com/

Summary details) for a given customer. accountSummary

Account 1)Account Name http://www.mbcdm.accountservices.com/

Details 2)Account type accountDetails
3)Currency
4)Account Open date
5)Account Close Date
6)Account Status
7)Debit Turnover
8)Credit Turn Over
9)Current Balance
10)Authorized Signatories
Islamic Get Account details for http://www.mbcdm.accountservices.com/
Account Islamic Account IslamicAccountDetails
Details
Account Get Account Block Summary http://www.mbcdm.accountservices.com/
Block Details AccountBlockSummary
Summary
Amount Query Amount Block Details http://www.mbcdm.accountservices.com/
Block AmountBlocksQuery
Query
Loan Query Loan Details http://www.mbcdm.accountservices.com/
Details QueryLoanDetails

Customer Query Customer MMC http://www.mbcdm.accountservices.com/

MMC Details MMCProductDetails
Details
Credit Get Credit Card Summary http://
Card Details www.mbcdm.creditcardservices.com/
Summary creditCardSummary

15
 CCMS Low-Level Design

Account Get Account Statement http://www.mbcdm.accountservices.com/

Statemen Between Dates accountStatement
t
Between
dates

5.3 Services exposed in CCMS

Service Name Business Functionality URL Request/Response

CreateCCMSInstance Initiate a BPM JSON over HTTPS
Instance for the given Input : caseReferenceNumber
court case. (String)
caseType(String)
Output : response (String)
[Success/Failed].

CCMSEDMSCaseCreation EDMS ID Generation JSON over HTTPS

for the given file name Input : caseRefNo(String)
filename(String)
Output : status(String)
[Success/Failed]
CCMSUpdateRPAStatus End point to JSON over HTTPS
communicate if the Input : caseRefNo (String)
response upload status (String) [Success/Failed]
passed or failed. reason (String)

5.4 Sending, receiving and processing emails

 BPM Activity sent outgoing mail using SMTP
 RM will send mail using SMTP.
 Mail inbox checks based on scheduled time intervals.

5.5 Home Page

Once user clicks on the Landing page icon, it will redirect to the below Home Page where the user will
perform the actual task.

16
 CCMS Low-Level Design

Note:

The highlighted sections in the home page called tabs. Based on user privileges, the tab will be
varied.

My Queue:

Once cases are created, users can able to see both the CCMS Portal and Dubai Portal Email cases in
My Queue Section.

Re Sub Queue:

Whenever checker refer the cases back to maker, then checker referred cases are will be available
in Re Sub Queue.

Search:

Based on different search criteria users can able search and check the status of the cases.

Task Reassignment:

Whenever “CCMS Assigner” users want to assign cases back to other users, then users can re-assign
the single or multiple cases to others by clicking re-assign button under Task Reassignment section.

17
 CCMS Low-Level Design

5.6 Maker Process

 Court letter application only deals with Mashreq Customer Accounts (Non-customers are not
fetched from any system).
 Court Letter response documents to CCMS portal contains only the account, block-summary and
MMC Details explicitly selected by the “Maker”.
 Response document generated by BPM, using Java, must have a name same as the unique case-
reference number provided by Java.

18
 CCMS Low-Level Design

5.7 Checker Process

 When maker submit the case, cases will be landing in checker queue. Once checker claim the case,
checker can able to see information as Read Screen mode along with documents.
 Checker will verify information with documents, if checker required any more information
regarding customer, cases will be referring back to Maker for getting additional information.
 After verifying customer information, checker will approve the cases.

19
 CCMS Low-Level Design

5.8 Dubai Portal Email Notification

When dubai portal email cases are created in BPM. we will get mail notification with below template.

5.9 RM Email Notification

Based on Account Action mail will send to RM. we will get mail notification with below template.

5.10 TMS Queue Email Notification

Based on Amount Block request is issued on the attached Accounts mail will send to TMS Queue. we will
get mail notification with below template.

5.11 Exception Email Notification

When exception raises in service we will get mail notification with below template.

5.12 Deployment Plan

20
 CCMS Low-Level Design

6. User Interface Design

6.1 Coach Views
Document all Coach Views designed for the solution and no Exclusive Coach-View will be developed
for this application.
 RequestDetailsCV
 CCMS Fetch Customer Search Details
 CCMS Customer Details
 FetchAccountDetails 2
 AccountStatementCV
 CCMS Account Block Summary CV
 CCMS LoanDetails CV
 CCMS CustomerMMCDetails CV
 CCMS Credit Card Summary
 CCMS ReplyAndAttachmentsCV
 CCMS Need Info
 CCMS Correspondence Details
 CCMSCourtsTemplateCV

6.2 Coaches
Coach Description Actors
CCMS Maker will check & enters the
customer’s data and upload documents.
Maker Screen CCMS Maker
Finally, Case submitted to CCMS Checker for
further process.
CCMS Checker Can receive data from CCMS
Maker for quality checking. CCMS Checker can
Checker Screen send the case to CCMS Maker. if customer’s CCMS Checker
data is incomplete. Otherwise, CCMS Checker
will approve the case.
Verify EDMS Status Documents will be uploaded and deleted from
CCMS Maker
Maker Local File System after completion of cases
CCMS View Screen To displays customer’s data in read only mode All users

6.2.1 Maker Screen

 Court Letter Maker Screen: Request Details

1.CCMS Portal Case: For CCMS portal case will get below information from CCMS Portal via
RPA and Java.
 Request Details
 Defendant Details
 Complainant Details
 Request Type Details

21
 CCMS Low-Level Design

2.Dubai Email Case: For Dubai Portal Email case, user should enter all the data before
submitting to Checker.

Note:

For Dubai Portal Email cases, User will enter the data manually and they have option to save the
“Court Request” and “Reply and Attachment” information by clicking “Save” button in CCMS_Maker screen.

 Court Letter Maker Screen: Customer Search

Search Screen:
BIS Portal Search: When Search parameter contains name, then it will go for BIS Portal
Search.

Flex Call: Except name, when search parameter contains other fields like License number,
Emirates ID, Passport, Nationality and DOB then it will go for Flex call.

22
 CCMS Low-Level Design

 Court Letter Maker Screen: Customer Information Details

 Display the information about customer based on customer search criteria.
 CCMSMaker can add multiple customer information on selection of different CIF.
 On selection of CIF number, RM Name of respective customer should appear
automatically.
 By clicking Get Account Details button, will get information about customer
account details, Loan Details, Customer MMC Details and Credit Card Summary
(Prime System).
 By clicking Get Documents button, will get customer related EDMS documents.
Here, Java service fetching document by using scheduler and scheduler will run
every 5min.

23
 CCMS Low-Level Design

 By Clicking “Eye Icon” will get more information about customer details.

24
 CCMS Low-Level Design

 Court Letter Maker Screen: Customer Account Details

 By Clicking “Eye Icon” will get additional information about customer and on selection of
“from and to dates" will get customer account statement.

Note:

 By Default, will get span of 6-month Account Statement and maximum span of 1-year account
statement will get.
 BPM having the functionality to generate statements in different formats such as:
 PDF
 Excel Sheet

25
CCMS Low-Level Design

26
 CCMS Low-Level Design

 Court Letter Maker Screen: Customer Account Block Details

 On selection of Account number and by Clicking Get Account Block Details button, will get
existing account blocked information about customer.

 Court Letter Maker Screen: Customer Loan Details

Can able to select multiple loan of customer and by clicking “Eye Icon” will get detailed loan
information about customer.

 Court Letter Maker Screen: Customer MMC and Credit Card Details
 User can able to select multiple MMC details of customer.
 Credit card details of customer for purpose of viewing card statement.

27
CCMS Low-Level Design

28
 CCMS Low-Level Design

 Court Letter Maker Screen: Reply and Attachment Details

 The users can select the customer relation type; customer name will be appearing
automatically.
 Based on court request user should select the reply action, reject reason and CCMS
Response Status.
 User can enter English/ Arabic comments in comment field.

29
 CCMS Low-Level Design

 Court Letter Maker Screen: Selected Account Details under Reply and Attachment Section
 The account details that are selected in the “Account Details Section” will be available under
“Selected Account Details Section”.

 Court Letter Maker Screen: Need Info under Reply and Attachment Section
BPM having a separate “Button” called Need Info under Reply and attachments tab. The main purpose
of this is to obtain the missing information from court.
Below are few fields need to be incorporated in BPM.
Subject:
Please select the following which is missing
o EID/ passport required
o Trade license required
o Court order/letter/final judgement required
o Wrong attachments
o Attachments not clear
o Other issue in the request
Request :
Once user select any one of the items with the respected subjected and then Request the details to
court provide the necessary details. User should be able to add comments in comments box in ARABIC.

Note:

 Currently Need Info only applicable for CCMS Portal case.

30
 CCMS Low-Level Design

 Court Letter Maker Screen: Correspondence Details

 Here, user can see the correspondence details of the particular customer.

 Court Letter Maker Screen: Template Section

 The user can select required template and generate pdf from template selection based on
request action.
 Court name will be auto-populated in all templates from Request Details.
 The Account numbers will be auto-populated in the dropdown that the user selected
account from “Account Details section”.

31
 CCMS Low-Level Design

 On selection of Account number, currency and amount will be auto-populated and can add
multiple account details.

 Court Letter Maker Screen: Final Court Templates (Arabic Template) in Template Section
 The user can select required template and generate pdf from Final Court Templates based
on request action.
 The Account numbers will be auto-populated in the dropdown that the user selected
account from “Account Details section”.
 On selection of Account number, currency and amount will be auto-populated and can add
multiple account details.

32
 CCMS Low-Level Design

 Court Letter Maker Screen: Upload Document

 User can upload the document from BPM and they can see, user uploaded documents and
EDMS documents.
 If user want to send document to CCMS Portal, need to select the “Send CCMS Response”
check box.
 If user want to send document to Dubai Portal Email, need to select the “Send Email
Response” check box.
 After uploading, User can delete the document, if document not required or uploaded
wrong document.

33
 CCMS Low-Level Design

 Court Letter Maker Screen: Generate Closure Letter

 By Clicking “Generate Court Letter PDF” button, BPM generate the Closure Letter.
 BPM having the functionality to generate Closure Letter in different formats such as:
 PDF
 Excel Sheet

34
 CCMS Low-Level Design

6.2.2 Checker Screen

 CCMS Checker Can receive data from CCMS Maker for quality checking. CCMS Checker can send the
case to CCMS Maker. if customer’s data is incomplete. Otherwise, CCMS Checker will approve the
case.
 In CCMS Checker, customer details are displayed as “Read Only Mode”.

Upload Document Section:

The attached document will be sent to CCMS/Dubai Portal Email from BPM:
 The Specific template which is selected in “Send CCMS Response” for CCMS Case and “Send
Email Response” for Dubai Portal Email, will be printed along with seal and stamp of the bank
and same will be scanned and sent to BPM post that checker will be sent to CCMS/Dubai Portal
Email.

35
 CCMS Low-Level Design

6.2.3 Verify EDMS Status Maker

 Whenever submitting case to EDMS, BPM generate Auto emails to RMs signed by the user
name.
 Only for corporate customer’s notification/intimation will be received to RM as auto email.
 RM details to be fetched from CIF in flex.
 Auto email templates for RM based on the request raised from court.

Based on account action type, sending EDMS request to CCMS Freeze and Un Freeze Matrix Services.

Customer Type Action Type Action

CIBG Freeze/ block amount in the account BPM Needs to send it to TMS Application

SME/RBG Freeze/ block amount in the account BPM Needs to Send it to Retails maintenance Queue
CIBG /SME/RBG accounts Total freeze / account flagging BPM Needs to send it to CAM maintenance Queue

CIBG /SME/RBG accounts Inward remittance BPM Needs to send it to CPC_FTO queue

CIBG /SME/RBG accounts Outward remittance BPM Needs to send it to CPC_FTO queue

6.2.4 CCMS View Screen

 In CCMS View Screen, the users can check and view the customer related information as “Read
Only Mode”.

36
 CCMS Low-Level Design

7. Exception Handling
BPM Level Exceptions
Process exception: This occurs when there is a problem with one of the components used by a process or
service. Process exceptions are often caused due to temporary errors such as connectivity failure, timeouts,
or design time code errors.

Business exception: This is an exception that occurs due to the outcome of a decision in the process. The
actual process internally triggers this type of fault. A business exception is designed as part of a business
process and is raised by the business process if the process cannot proceed due to:

 Data validation failure

 Insufficient privileges
 Known business conditions on which the process should be put on hold

RPA Level Exceptions

Ste
p Steps Exception
No.
1 Login to CCMS System Exception: Application Launch Exception
E1: Application Launch
Hit the Application three times. If fails to launch
Exception
after three times then send Mail to SME and
E2: Login Failure Exception terminate the process.
E3: Action Timeout
Exception Operation team manually execute the process
E4: Session Timeout
Exception

37
 CCMS Low-Level Design

2 Cases not in E6: Case not found/ not Action Timeout Exception
Report Bounced accessible Exception
Update the status in the excel and proceed the
Screen
next data
3 Export Cases to E3: Action Timeout
Excel Exception
E4: Session Timeout Session Timeout Exception
Exception Click ok and continue process again
4 Fetch details E3: Action Timeout
from screen Exception
File not found / file not accessible exception
E7: Fetch Details Exception

5 Download the E3: Action Timeout

Try three time access mechanism send mail to
attachment from Exception
SME and stop process
screen E8: Download Exception

6 Internal Excel file E9: File not found Exception

Data not found / Data not accessible exception
7 RPA input File E5: File not found/ not
accessible Exception
Try three time access mechanism send mail to
SME and stop process

8 Update CCMS System Exception:

E3: Action Timeout Fetch Details Exception
Exception
E4: Session Timeout
Exception Update Excel and send to BPM with reason
E10: Update Exception

9 Upload System Exception: Download Exception

Attachment E3: Action Timeout
Exception
E4: Session Timeout Update excel with the exception reason and send
Exception to BPM

E11: Upload Attachment

Exception File not found or corrupt Exception
Keep duplicate copy of the file in another location
10 Reject Case System Exception:
E3: Action Timeout
Exception Update Exception
E4: Session Timeout

38
 CCMS Low-Level Design

Exception Update the excel with the reason and send to BPM

E12: Reject case Exception

Upload Attachment Exception
Update the excel with the error and send to BPM

Reject case Exception

Update excel with the rejection reason and send
to BPM

8. Auditing
Currently Auditing is performed in two ways. One is at Action level and second one will be in Field level.
 Case level Audit is captured in the following tables.

Database Table: CCMS_AUDIT_TRIALS

Business Object: CCMS_AuditTrials

9. Logging
By default, log, error, and trace information for all processes and applications on a process server is written
to the application specific log files. We have implemented the logging through:

Logging will be achieved using log4j framework.

 appLog.js - takes care of logging.

10. Data Persistence

All application level data is stored in the Application Database schema created for the Court Letter
project. Both Java and BPM have access to the application database for CRUD operations. The
application database schema is hosted on an Oracle database, managed by the Mashreq Database
Group.

 Java used JDBC to connect to the Application database and carry out the CRUD operations.
 BPM uses the IBM BPM Database connectors to connect to the Application database.
Instance Purge Timeline
Instances created in IBM BPM Platform will be available for processing for 90 days. Post 90 days the
instances will be purged from the system.

39
 CCMS Low-Level Design

11. Design Decisions

DD – 001

Problem Login to Portal (Captcha)

Statement

Solution Option 1: Login through BOT. Option 2: Login using command center
Options personnel.

Pros: Pros:
 Seamless Design.  Can Login to the CCMS Portal by
 No human Intervention to entering CAPTCHA Code.
enter Captcha.

Cons: Cons:
 Accuracy of reading captcha is  BOT timing need to be tightly
very low. coordinated with the Command Center
team.
 Not a seamless design.

Recommended Option-2
Option

Justification BluePrism’s inbuilt OCR for captcha recognition was not deemed up-to-the-mark (about
50% accuracy).

DD – 002

Problem Instantiation of cases on BPM and transmission of data captured by RPA into BPM
Statement

Solution Option 1: Call BPM REST service with Option 2: Use Java as a mediator.
Options data

Pros: Pros:
 Direct communication avoiding  Higher volume can be handled.
an intermediary.  Immediate response, as won’t have to
 Save on development time wait for actual instance creation.
required to build mediation  Better retry opportunity in case of
services. BPM being unavailable during BOT
running hours.
 Image standardization could be

40
 CCMS Low-Level Design

carried out before creation of BPM

instance.

Cons: Cons:
 Lower throughput because of  Additional layer requires additional
wait for actual instance development effort
creation.
 Retry because of the non-
availability of BPM system
during BOT runs becomes a
challenge.
 Synchronization between Java
(Image Server) and BPM need
to be carried out, so that
images/documents are
available before task is
exposed to the user.

Recommended Option-2
Option

Justification Image/document standardization can only be carried out through Java layer. Better
scalability and offloading of heavy database operations on to the Java layer.

DD – 003

Problem Interfacing with OMW-Flex for Customer/Account Search

Statement

Solution Option 1: Use BPM Services pre-built Option 2: Develop OMW-Flex interface in the
Options for OMW-Flex interaction Java layer.

Pros: Pros:
 Connectors and Service  Better capacity and capability of
contract already available. handling SOAP-XML request and
 Business objects need not be response.
modeled from scratch.  Better scalability.

Cons: Cons:

41
 CCMS Low-Level Design

 XML Parsing in BPM is heavy.  Additional effort required to develop

the connectors and establish a
common data format for BPM
consumption.

Recommended Option-1
Option

Justification Pre-built connectors available that can be leveraged, thereby lowering the time-to-
market.

12. Reusability
Below are the list of reusable components (internal and external) that are part of the overall solution.
Sl No. Component New/Existing Business Functionality Description

1 Flex_Account Existing Customer Details,

(FA_30052018_V3.3 Account Details

2 Generic Exception Handling TK Existing Handling BPM Exception

(GEH.07.03.2018.001)

3 AppLogJS Existing Logging

4 Atomic File Transfer Existing Copying files between Copy files from RPA to Java
servers Servers and vice-versa.
Java Reusable components are provided here.

13. Additional Capacity Planning

Disk-space Memory Disk-Space(Server) Disk-Space (Database)
(NFS)
BPM NA 300 MB1 NA OLTP : 400 MB2
Staging : 2 GB3
Archival :
RPA 10 GB NA NA 400 MB
JAVA 250 GB2 1 GB NA NA

Note:
1. Lifespan of CCMS process is identified as maximum of 30 days from the time the instance is
created.

42
 CCMS Low-Level Design

2. As of now archival of completed instance data (post retention period) is yet to be finalized with
business.
3. IBM Techline sizing needs to be initiated to arrive at recommended hardware configuration
required to host this application.

1: Maximum 5 active users at any given point of time. Expected memory usage is around 300 MB.

2: Avg. cases 125 per day * 20 MB Document Per Case * (30 day lifespan + 30 day retention post
completion)

3: Staging/Reporting schema (1 table with 18 columns) capacity is calculated for all cases processed
over a period of 2 years.

14. Document Retention Policy

RPA
Documents will be retained at a maximum for 1 day. Downloaded documents are deleted once
picked up by Java-Atomic. For documents that are uploaded, those are deleted once
successfully uploaded.

Java
Java will keep the documents in its NFS for the whole duration of case being active in BPM
system. Hence the maximum retention period is 30 days post completion of instances in BPM.

15. Technical Debts

System Component Debt Description Impact Remediation
BPM Process Workflow for Court Tight coupling Split the common/reusable
Application Letter project is between both services and BO into their
developed as part of the Police Letter own toolkit and use them as
the Court Case and Court Letter required.
Management project Timeline for the same need
System Process deliverables. to be identified as this will
Application (Police need major refactoring
Letter). This helps effort.
reuse the common
components
between the two
projects. But makes
the deployment
package and
dependencies
heavier.
BPM Data Archival Data for cases are Reports/search Identify appropriate

43
 CCMS Low-Level Design

cleaned-up 30 days beyond 30 days reporting strategy and

after completion of after completion transfer the required data
the instance on BPM. of instances is into the archival tables
not possible. before purge. Will initiate
discussion with business with
respect to their reporting and
regulatory requirements and
decide on the timelines.
Java Completed/Purged There is no search Data and Create a global search
Case Search feature available for documents for feature for completed cases
completed cases, completed that can show case-data and
that are instances, which documents for cases that
subsequently purged are have been completed and
from the BPM subsequently archived from the BPM
system. purged cannot system. As agreed by the
be searched for. Management, this feature
will be rolled out for all
corporate trains after the
September go-live.

44