Scope Change Number (Must match with the change log entry) Date: 24/07/2023

(For Avenues Tech use only) Partner: IDFC

Product: DigiRemit
Project Name: Lien Cancellation Admin Tool + Source Identifier – Transaction Report.
CRF Created By: Chetan Naik
Developer Name:
Production Movement By:

Type of Change Priority Change (Related to Function) Request Type

☒Business Change or Need ☐Critical ☒ Operational ☒ Paid
☐ Scope Change or Need ☒High ☐ Compliance ☐ At no Cost
☐ Scheduled Change ☐Normal ☒ Service
☐ Error Correction ☐Low ☐ Miscellaneous
☐ Regulatory Requirement ☐ Internal Changes
☐ Network, Server & System
☐ Cosmetic
☐ Functionality
☒ Admin tool Development
☐ Others (Please Specify):
Is AMC Applicable

☐ Yes – If yes, please specify …………. (Percentage of AMC) OR ………………. (Fixed Cost) per annum
Applicable from DD/MM/YYYY (For Fable Fintech Finance use only)
☐ No
Checklist (For request Initiator)
☒ Required Screenshots Provided ☐ Required URLs provided ☐Login credentials provided (Cases to case basis)
☐ Flow Chart ☒ Details of Admin tool involved.
Version Control

Version Number Date Issued Author Reviewed By Update Information

1.0 24/07/2023 Chetan Naik - Initial Draft based on BRD.

1.1 28/07/2023 Chetan Naik - Update Doc as per clients’

comments over mail.
1.2 22/08/2023 Chetan Naik - Updated Doc as per discussion
with Bank on Fables Query.

Description of the Requested Change(s)

Contents
Requirement ........................................................................................................................................................ 2
Existing System:.................................................................................................................................................... 2
Expected Changes:................................................................................................................................................ 2
User Story 1: Lien Cancelation Admin Tool.......................................................................................................... 2
Development Changes:.................................................................................................................................. 2
Benefits: ....................................................................................................................................................... 3
Structural Validations on Input fields: ............................................................................................................. 4

1
 User Story 2: Source Portal Identifier. ................................................................................................................ 4

Requirement
• To Create a new Lien Cancellation Tool with a user-friendly interface to enhance the efficiency of the lien
cancellation process.
• To provide an Identifier for each portal, so that it can be easily identified that using which portal the
transaction has been raised.

Existing System:
• As part of the existing process, the cancellation of liens is carried out using the Fable Backend. This is
accomplished by either executing a query or making specific alterations to the backend system.
• No such identifier is present to identify that using which portal the transaction has been raised.

Expected Changes:
User Story 1: Lien Cancelation Admin Tool.
1. The purpose of this change request is to introduce a new Lien Cancellation Tool, which will enable
superadmin users to cancel liens for specific transactions. Refer Image 1.0
2. The tool will require the entry of a Transaction Reference Number or Account Number as input. Any one
field is required to fetch the details.
• If the Transaction Reference Number is provided and the superadmin user clicks on submit, the system
will automatically retrieve and display essential customer details and lien information associated with
the transaction reference Number.
• If the Account Number is provided and the superadmin clicks on submit, the system will automatically
retrieve and display essential customer details and lien information associated with the Account Number
provided.
• If both Transaction Reference Number & Account Number is provided and the superadmin user clicks
on submit, the system will automatically retrieve and display essential customer details and lien
information associated with the transaction reference Number and not the Account Number.
3. The information presented will include Transaction reference Number, Account Number, UCIC, Date of
transaction booking, Trace Number, lien marking request response, lien cancellation response, and a new
field for "Remarks" related to the transaction for which the lien needs to be cancelled.
4. Additionally, the functionality of the Cancel button will be made conditional, allowing it to be actionable only
when the lien cancellation request response is unavailable, and the user has entered remarks in the
provided field.
5. The actionable Cancel button will be used by superadmin users to proceed with the cancellation of the lien
for the particular transaction.
6. Once the Lien Cancelation is done successfully, the Lien cancelation request response will be updated
against the Transaction Reference Number and the admin user will be displayed with success message for
the same. Refer Image 1.1
7. If the Lien Cancelation Fails due to any unforeseen technical challenges an error message to be displayed to
the user. Refer Image 1.1
Development Changes:
To create a new Lien Cancellation Tool with a user-friendly interface to enhance the efficiency of the lien
cancellation process.
1. Account Number Input: Integrate an input field in the Lien Cancellation Tool to allow superadmin users to
enter the Account Number associated with the lien cancellation.

2
 2. Transaction Reference Number Input: Integrate an input field in the Lien Cancellation Tool to allow
superadmin users to enter the Transaction Reference Number associated with the lien cancellation.
3. Retrieval of Customer and Lien Information: Upon entering a valid Transaction Reference Number or
Account Number, the system will automatically retrieve and display the following crucial details related to
the transaction:
a. Transaction Reference Number
b. Account Number
c. UCIC (Unique Customer Identification Code)
d. Transaction Booking Date.
e. Trace Number
f. Lien Marking Request Response
g. Lien Cancellation Request Response
h. Remarks: A input field to capture remarks for the transaction requiring lien cancellation.
i. Cancel Button.
4. Condition-based Cancel Button: Configure the functionality of the Cancel button to be actionable only when
the lien cancellation request response is not available within the DR system, and the user has entered
remarks in the provided field. This will allow superadmin users to proceed with the lien cancellation process
for the specific transaction.
5. Authorization and Security Measures: Implement appropriate authorization controls to ensure that only
superadmin users have access to the Lien Cancellation Tool. The Lien Cancelations taken place via the admin
tool provided to be stored in the backend along with the User name and time stamp of the activity.
Benefits:
1. Streamlined Lien Cancellation Process: The new tool will expedite lien cancellations, reducing manual efforts
and processing time for superadmin users.
2. Informed Decision Making: Superadmin users will have access to essential customer and lien details,
enabling them to make well-informed decisions regarding lien cancellations.
3. Improved Data Accuracy: The automated information retrieval will minimize data entry errors, ensuring
accurate and reliable lien-related data.
4. Enhanced User Experience: The user-friendly interface will enhance the overall experience for superadmin
users during the lien cancellation process.
Image 1.0

3
(The above image is for presentable purposes)
Image 1.1

(The above image is for presentable purposes)

Structural Validations on Input fields:

1. Transaction Reference Number: min max length: 22, Data type: Varchar, Special Characters: not allowed.
Example: DIGIREMI24072023000002
2. Account Number: Min/Max Length: 11, Data Type: Numeric, Special Characters: not allowed.
Example: 10000011881
3. Remarks: Min length: 03, Max length: 150, Data Type: Varchar, Special Characters: not allowed.
Example: Lien Cancellation due to ABC XYZ Reasons.

User Story 2: Source Portal Identifier.

Admin Tool: MIS > Transaction Report.
• There should be an Identifier for each portal, so that it can be easily identified using which portal the
transaction has been raised.
1. For transactions made through the API, the Channel will reflect as online, and the Source Portal will
reflect as Optimus Mob.
2. For transactions made through the WEB, the Channel will reflect as online, and the Source Portal will
reflect as Optimus Web.

4
 3. For transactions made through the Branch, the Channel will reflect as Branch, and the Source Portal will
also reflect as Branch.
4. Only transactions with ref no. DIGIREMI are to be considered for this change.

Channel Source portal

Branch Branch
Online Optimus Mob
Online Optimus Web

Note:
• IDFC Comments:
DIGIREMIT has 3 ways through which transactions are initiated Branch, Web and Mobile. For branch, source
portal value will be Branch, for native journey (mobile) source portal is currently showing OptimusAPI, which
we want to change to Optimus Mob, but for web, the old journey is going to be discontinued and those will
also come through same api that we are using currently for native. In that case, please let us the tag through
which optimus will send the value Optimus Web, so that if that tag contains value, it will be shown in source
portal as Optimus Web for this journey.

Fable: We will have to define new client code for Web flow for the above-mentioned scenario.

Impact Due to Suggested Change(s)

Impact Summary

Development Estimation

Resource Required (Man days): Effort Estimation Approved by:

(Project to be commenced post-approved by Partner)

Authorization

Project Manager’s Name & Signature: Date: Click or tap to enter a date.

Developer’s Name & Signature: Date: Click or tap to enter a date.

CRF Reviewed & Approved by: Date: Click or tap to enter a date.

Note:
1. Complete scope of work to be defined appropriately by the request initiator.
2. Request initiator can use subsequent pages for screenshots & additional information.
3. Avenues Technology/Fable shall provide timelines & effort estimation only for the scope defined in the CRF. In case of addition to the scope of work,
the timeline may differ.
4. The above timelines shared by Avenues Technology/Fable are for estimation purposes. The actual timeline may differ.