Professional Documents
Culture Documents
in
2023
KONSULTERA SOLUTIONS PVT LTD
Intake Application
Release Note (2023)
Page 1 of 5
Release Document
Environment: Production
Date: 29/11/2023
Build: -
Release Details
This release is for the UAT environment. The purpose of this release is to test improved functionality on the UAT
environment before rolling it out on production.
Release Scope
The following features are included in this release:
Admin Role:
The user login to the system using login credentials (username and password) or by
selecting SSO (i.e., Login with Microsoft).
Dashboard:
The users will have the ability to view the following Admin log statistics of existing
data in the system consisting of customer profile details (i.e., ID, Customer Name,
Address, Country, City, State, Zipcode, Status, and Action).
The users will have the ability to search based on ID, Customer Name, Address,
Country, City, State, Zipcode, and Status.
The users will have the ability to edit the customer details.
The users will have the ability to allocate SME and User.
Customer Creation:
The following actions can be done on the customer creation:
Customer Profile – The admin have the ability to fill in the customer profile
details such as ID, Customer Name, Address, Country, City, State, and
Zipcode.
Page 2 of 5
SME Allocation - The user can assign the subject matter group from the
subject matter expert by using the following action buttons as mentioned
below:
o To assign a member to the project: Select a member in the left
section and use the single arrow button to move that selected
member from unassigned to assigned.
o To assign all members, use the double arrow button.
o To unassign a member from a project: Select the member from
the right section and use the single arrow button to move that se-
lected member from assigned to unassigned.
o To unassign all members, use the double arrow button.
Customer User - The customer section consists of the following features:
o User List – The added users will be listed in the user list. The user
can create a profile by clicking on the “+ Add User” and can also
edit/update details by clicking on the edit option from the action
button.
o User Profile - The user should fill in the following details to create
a user profile (i.e., Company, First Name, Last Name, Email,
Phone Number, Country, State, City - dropdown list of countries,
and Zipcode)
SME Role:
The user login to the system using login credentials (username and password) or by
selecting SSO (i.e., Login with Microsoft).
The users will have the ability to view the following SME log statistics related to the ticket
(i.e., Total Records, Completed Request, Cancelled Request, and Active Request).
The users will have the ability to search, filter, and sort based on Ticket No., Submitted On,
Transaction Deal/Name, Comp Id, Company, Created By, Status, Assigned To, and
Completed On.
The users will have the ability to view lists of all the tickets that have been assigned by
clicking on the “Assigned To Me” button and can also assign to themselves by clicking on the
“Assigned To” tab.
The users will have the ability to view lists of all the tickets that have been assigned to other
users by clicking on the “All” button.
Action Button: The action button has the following actions that can be performed:
View: The user can view and can also change the status of the ticket only for the
tickets that have been assigned to self.
Log: The user view all the log details such as Status, Updated On, Updated By, and
Remarks.
Transfer Request: The user can transfer the ticket to another SME.
Cancel: The user can cancel the request with comments only to those requests that
have been assigned to themselves.
Supervisor Role:
The user login to the system using login credentials (username and password) or by
selecting SSO (i.e., Login with Microsoft).
The users will have the ability to view the following Supervisor log statistics related to the
ticket (i.e., Total Records, Completed Request, Cancelled Request, and Active Request).
Page 3 of 5
The users will have the ability to search, filter, and sort based on Ticket No., Submitted On,
Transaction Deal/Name, Comp Id, Company, Created By, Status, Assigned To, and
Completed On.
The users will have the ability to view lists of all the tickets that have been assigned by
clicking on the “Assigned To Me” button and can also assign to themselves by clicking on the
“Assigned To” tab.
The users will have the ability to view lists of all the tickets that have been assigned to other
users by clicking on the “All” button.
Action Button: The action button has the following actions that can be performed:
View: The user can view and can also change the status of the ticket only for the
tickets that have been assigned to themselves.
Log: The user view all the log details such as Status, Updated On, Updated By, and
Remarks.
Customer Role:
The user login to the system using login credentials (username and password).
The users will have the ability to view the following customer log statistics related to the
ticket (i.e., Total Records, Completed Request, Cancelled Request, and Active Request).
The users will have the ability to search, filter, and sort based on Ticket No., Submitted On,
Transaction Deal/Name, Comp Id, Company, Created By, Status, Assigned To, and
Completed On.
The users will have the ability to view lists of all the tickets that have been assigned.
Action Button: The action button has the following actions that can be performed:
View: The user can view and can also change the status of the ticket only for the
tickets that have been assigned to themselves.
Log: The user view all the log details such as Status, Updated On, Updated By, and
Remarks.
Edit: The ticket can be edited and can only upload the documents.
Cancel: The user can cancel the request with comments only to those requests that
have been assigned to themselves.
The user can also create a new request by clicking on the “+ New Request” button from the
dashboard. Once the new request is created, the SME and the Supervisor will receive it.
Deployment Specifications:
The KT team will deploy the code on the Production server by directly accessing the Production server using VPN
and RDP.
Build Version:
Environment details
OS Azure Hosted
Database Postgres DB
Page 4 of 5
Deployment URL
Credentials
Page 5 of 5