CT ID Creation

Registration Process

ADD OUTLOOK DATA process

 Request type and Allocation Category fields should automatically add the following
o Request Type: CT ID Creation – New Request – [PMT] Catered and for Testing - OKAY
o Allocation Category: automatically the user reflects in the field – New Request - [PMT]
Catered and for Testing - OKAY
o This removes the manual editing the request in registration – New Request - [PMT]
Catered and for Testing - OKAY
o Once registered, this should be reflected in the Users panel not in Job for Allocation -
[PMT] Catered and for Testing - OKAY

o Service Type – automatically add the “Account Maintenance” – New Request - [PMT]
Catered and for Testing – not yet resolve
o Please correct the entities spelling - [PMT] Catered and for Testing – waiting for the
forms

MANUAL process

 Workflow Type: pop-up form should be removed, it should be in task-in process – Indicated in
User Story was in Registration Module
  Request Type: should automatically add CT ID Creation – New Request - [PMT] Catered and for
Testing – HIDE - OKAY
 External Reference: once the data added, this should be reflected in Entity/Affiliation
Name/Number – New Request - [PMT] Catered and for Testing - OKAY
 Allocation Category: automatically the user reflects in the box – New Request - [PMT] Catered
and for Testing - OKAY
 Once registered, this should be reflected in the Users panel not in Job for Allocation - [PMT]
Catered and for Testing - OKAY

TASK-IN/OUT Process

 Click Task-in and pop-up the form to input the Number of Entities, then submit and close the
form – Indicated in User Story was in Registration Module (not specified on request)
 Click Task-out and pop-up the form to input the Number of Records, then click submit and close
the form – Indicated in User Story was in Registration Module (not specified on request)

MDM Process
MANUAL registration

 Workflow Type: pop-up form should be removed, it should be in task-in process - Indicated in
User Story was in Registration Module
 Request Type: should automatically add MDM – New Request - [PMT] Catered and for Testing –
HIDE - OKAY
 External Reference: once the data added, this should be reflected in Task Title – New Request -
[PMT] Catered and for Testing – cannot yet verified due to no complete record in the reports
 Allocation Category: automatically the user reflects in the box – New Request - [PMT] Catered
and for Testing HIDE - OKAY
 Once registered, this should be reflected in the Users panel not in Job for Allocation - [PMT]
Catered and for Testing HIDE - OKAY
TASK-IN/OUT Process

 Click Task-in and pop-up the form to input the following - Indicated in User Story was in
Registration Module
o Task Type with dropdown (Participant or Customer)
o Task ID
o Status – New Request
o Comments – New Request
 Click Task-out and pop-up the form to input the Number of Records, then click submit and close
the form – New Request

RETURNED MAIL
Registration Process

 Task Transmittal Type, Entity Number and Entity Name/Customer Name should be in task-out
process - Indicated in User Story was in Registration Module
 Once the files completed and reflected in Browse, it should have a confirmation the total
uploaded files. – New Request - [PMT] Catered and for Testing - OKAY
 Click submit and automatically allocated the designated users and close. - [PMT] Catered and for
Testing – not yet resolve

TASK-IN/OUT Process

 Click Task-in
 Click Task-out and pop-up the form to input the following
 o Transmittal Type with dropdown
 Invoice
 Renewal Invoice
 Communication
 Bulletin
 Post Card
 Letter
o Entity Name
o Entity number
o Status with dropdown – New Field
 CAN BE PROCESSED
 CANNOT BE PROCESSED
 DEAD END
o Remarks – New Field
o Number of Records with default “1” as value – New Field
o Then click submit and close the form

Account Maintenance
Registration Process

ADD OUTLOOK DATA process

 Request type and Allocation Category fields should automatically add the following
o Request Type: Account Maintenance – New Request - [PMT] Catered and for Testing -
OKAY
o Allocation Category: automatically the user reflects in the field – New Request - [PMT]
Catered and for Testing - OKAY
o This removes the manual editing the request in registration – New Request - [PMT]
Catered and for Testing - OKAY
o Once registered, this should be reflected in the Users panel not in Job for Allocation –-
[PMT] Catered and for Testing – not yet resolve

MANUAL registration
  Pop-up form should be in task-out process - Indicated in User Story was in Registration Module
 Request Type: automatically add Account Maintenance – New Request - [PMT] Catered and for
Testing – HIDE - OKAY
 External Reference: automatically add in Email Subject in Account Maintenance Details – New
Request - [PMT] Catered and for Testing – cannot verified
 Allocation Category: automatically the user reflects in the field – New Request - [PMT] Catered
and for Testing - OKAY
 Once registered, this should be reflected in the Users panel not in Job for Allocation - [PMT]
Catered and for Testing - OKAY

TASK-IN/OUT Process

 Click Task-in and pop-up the form to input the Number of Entities to calculate the TAT (this will be
adjusted once the number of records filled the complete output based on the TAT table) – New
Request
 Click Task-out and pop-up the form to input the following
o Service Type: automatically add Account Maintenance – New Request
o Request Type: with dropdown
 Name Change
 Discontinuance
 DNP
 Affliation
 CPQ
 Delaware request
 Mutli-Activity Request
 Delivery Instruction
 Creation/Deactivation of C/CST Records
 Agent Resignation
 Invoice Revision
 Representations
 Others {Default}
o Entity/Affiliation Name/Number – for Remove, this is already reflected in the Email
Subject – Field was included on request
o Requestor: automatic for Add outlook process/for manual input the data – New Request
 o Number of Entities
o Estimated Records
o Status – New Request
 Already Discontinued
 Already Updated
 Closed request
 Completed
 Disregard
 Duplicate
 Query/Pending

State Audit
Registration Process

ADD OUTLOOK DATA process

In Edit, the following should be

 Email Request – should automatically the add the External Reference – New Request - [PMT]
Catered and for Testing – OKAY
 Estimated Records – TAT should be based on the added number of records based on the TAT
table – Done - [PMT] Catered and for Testing OKAY
 Allocation Category: should be added to allocate user – [PMT] Catered and for Testing - OKAY
  Batch Count: should be added to add number of users to be allocated, default value “1” – Counts
assigned user of “State Audit” Workflow
 CRM# - this should be in Task-out process - Indicated in User Story was in Registration Module
 Submit – this should be Registered and automatically remove in the Job Registration the once
click. – New Request
 Add to Queue – this will automatically reflect in Job for Allocation
 Once registered, this should be reflected in the Users panel not in Job for Allocation – [PMT]
Catered and for Testing – cannot verified due to error below

TASK-IN/OUT Process

 Click Task-in
 Click Task-out and pop-up the form to input the following – New Request
o Total Output
o CRM#
FEEDBACK AS OF 10/24/2022
CT ID CREATION
1. Outlook Registration
a. Allocation Category
i. user did not reflect in the column
ii. it will not automatically display in the user’s panel

b. it did not display in user’s panel and allocation category

[Roel] This serves as a New Request because it is only accepting the role ‘Specialist’ to auto reflect the
user in the Allocation category. The role ‘Registration’ was not considered where this was currently
being used that causes the allocation category value not auto reflecting.

2. Manual Registration
a. External Reference – did not displayed on the input/data added in Entity/Affiliation
Name/Number – [Roel] The form “View Details” will be removed in the registration
module and will be transferred to the Task-out module.
b. Allocation Category - user did not reflect in the column [Roel] Same as above
explanation regarding the additional role ‘Registration’.
3. Task-in – this should not be displayed in task-in process

4. Reports
a. Type of Request – should be CT ID Creation that automatically displayed; it was already in
the form under Request Type
STATE AUDIT
1. Outlook Registration
a. Allocation Category
i. user did not reflect in the column

[Roel] This serves as a New Request because it is only accepting the role ‘Specialist’ to auto reflect the
user in the Allocation category. The role ‘Registration’ was not considered where this was currently
being used that causes the allocation category value not auto reflecting.

2. Task-in Process
a. this pop-up form should not be displayed in task-in process

3. Task-out process
a. Service Type should be State Audit that automatically displayed; it was already in the
form under Request Type
 b. Output Value field should be automatically captured as the Estimated Records added in
the form. New Request.

4. Reports
a. The completed request did not reflect in the reports.
MDM Process
Complete task did not reflect in the report.

The Status should be updated for the completed jobs to reflect in the status. [Roel] As per PD, [1]
the pop out form should be removed in Task-in and Task out. [2] Output value should also be
updated in Number of Records field Project database. [3] Add ‘Claimed’ in the list item of
selection in the Project Status.

Account Maintenance
1. Outlook Registration
a. Allocation Category
i. user did not reflect in the column

[Roel] This serves as a New Request because it is only accepting the role ‘Specialist’ to auto reflect the
user in the Allocation category. The role ‘Registration’ was not considered where this was currently
being used that causes the allocation category value not auto reflecting.

ii. it was registered twice, please advise. PD verification

2. Task-in Process
a. Pop-up form should not be displayed

3. Task-out Process
a. Assigned Name should automatically reflect based on the user task-in the request Full
Name Default
b. Date Completed should automatically displayed based on the date in the machine
Current Date
c. Service Type should automatically “Account Maintenance”, it is already in the form
Request Type.

d. Output Value should reflect the Estimated Records New Request

4. Reports – output did not display in the reports.