Professional Documents
Culture Documents
Untitled
Untitled
Page 2 of 69
9.2 To-Be Process Flows...............................................................................................................................23
9.3 Business Requirements & Solutions.......................................................................................................23
9.4 Job Order Information.............................................................................................................................24
10 JOB POSTING DISTRIBUTION AND RECEIVING APPLICATIONS.................................................26
10.1 Process Overview....................................................................................................................................26
10.2 To-Be Process Flows...............................................................................................................................26
10.3 Business Requirements & Solutions.......................................................................................................26
10.4 Job Posting Distribution Information......................................................................................................27
11 APPLICATION MANAGEMENT................................................................................................................28
11.1 Process Overview....................................................................................................................................28
11.2 To-Be Process Flows...............................................................................................................................28
11.3 Business Requirements & Solutions.......................................................................................................28
11.4 Application Inforrmation.........................................................................................................................29
12 PLACEMENT..................................................................................................................................................31
12.1 Process Overview....................................................................................................................................31
12.2 To-Be Process Flows...............................................................................................................................31
12.3 Business Requirements & Solutions.......................................................................................................31
12.4 Placement Information............................................................................................................................32
13 ORDER AND APPROVAL PROCESS.........................................................................................................36
13.1 Process Overview....................................................................................................................................36
13.2 To-Be Process Flows...............................................................................................................................36
13.3 Business Requirements & Solutions.......................................................................................................36
13.4 Order Information...................................................................................................................................39
14 TRANSACTIONS............................................................................................................................................42
14.1 Process Overview....................................................................................................................................42
14.2 To-Be Process Flows...............................................................................................................................42
14.3 Business Requirements & Solutions.......................................................................................................42
14.4 Transactions Information........................................................................................................................42
15 PUSH S-BASED FROM CRM TO AX PROCESS......................................................................................44
15.1 Process Overview....................................................................................................................................44
15.2 To-Be Process Flows...............................................................................................................................44
15.3 Business Requirements & Solutions.......................................................................................................44
15.4 CRM and AX mapping fields..................................................................................................................45
16 ACTIVITIES....................................................................................................................................................48
16.1 Process Overiew......................................................................................................................................48
16.2 To be Process flows.................................................................................................................................48
16.3 Business Requirements and Solution......................................................................................................48
16.4 Activities Information.............................................................................................................................48
17 REPORTS.........................................................................................................................................................49
17.1 Business Support Reports........................................................................................................................49
Page 3 of 69
17.2 Fee Breakdown........................................................................................................................................51
Page 4 of 69
INTRODUCTION
This Functional Design Document (FDD) is prepared based on the Scope of Project documented which were
identified during the Recruitment Business Process and Requirements workshop and with the following persons:
Mai, Nguyen Phuong
Oanh, Tran Thi Kieu
Lan, Ngo Thi Ngoc
Huong, Nguyen Thi Thanh
Nhi, Nguyen Duc Tuyet
Quyen, Dinh Thi
Thuan, Tran
This document is structured in accordance with IGV and NS method for implementation of Microsoft Business
Solutions projects. The findings of this FDD will then form the basis of the Key User Training Documents. The
findings of this FDD will also form the basis of the User Acceptance Test (UAT) Scripts. This ensures that future
tasks are prioritized accordingly and resources used efficiently.
The objective of the Functional Design Document is to provide enhanced documentation actual cycles will be
implemented in the correct project of .
Page 1 of 69
SYSTEM OVERVIEW
1.3 Systems Information
Application/Systems Purpose Comments
Dynamics CRM 365 Manage Sales & Customer Service Dynamics 365 on-premise v9
VIETNAMWORKS VNWs Job and Candidate Management
ENWORLDVN Navigos Search Job Management
PRIMUS Primus Job and Candidate Management
Dynamics AX Financial System
Page 2 of 69
Provide a strong candidate searching on NS database, Primus database, Vietnamworks database
From CRM, job order distribution on different Job boards and receive applications:
• Vietnamworks.com
• enworld.com.vn
• primus.vn
Page 3 of 69
DYNAMICS CRM FUNCTIONAL ENTITIES
1.6 Process Overview
This is the process for Consultant team to conduct the Sales, from Job Order to create Order (P-Based & S-Based).
3 Account Billing Legal information: tax code, legal name, Function Customize Entity Billing
management billing address Account with the required
fields
4 Contact/Candidate An account has more than one contact Function Customize Entity Please refer to 8.7.4 for
Management associated with it, especially when Contact/Candidate with the all required
you're working with a larger company required fields Contact/Candidate
with many departments or locations Information
and you deal with several people to
manage the account.
Candidate are individual profile.
Page 4 of 69
Guarantee period, payment terms. with the required fields
6 Job Order A job order is a job requirement of Function Customize Entity Job Order
Management customer, including: Job description, with the required fields
salary, ….
12 Job posting A Job Order can be distributed to Required Job boards API
Distribution different Job boards:
Vietnamworks.com
Primus.vn
Enworld.com.vn
Page 5 of 69
ACCOUNT MANAGEMENT
1.9 Overview
Business that represents a customer or potential customer. The company that is billed in business transactions.
When Consultant create an Account in CRM, the system run duplicate dectection rules that find duplicated records.
The Duplicated dectection rules are defined in Settings > Data Management > Duplicate Dectection Rules.
Record_Type_Name
Customer Type Option Set
__c
Account_Name_Tex
Account Name Text(255)
Yes t__c
Long Text
Critical Details Critical_Details__c
Area(2000)
See the
Company Status ts2__Status__c Picklist
Yes NSCRM_Picklists_Value.xls
Phone text
See the
Account Source Picklist
NSCRM_Picklists_Value.xlsx
Website URL(255)
Picklist(Multi-
Primary Sector Primary_Sector__c NS confirm later
Yes Select)
See the
Yes Global HQ Global_HQ__c Picklist
NSCRM_Picklists_Value.xlsx
Number of Staff No_of_Staff__c Number
See the
Start of Fiscal Year Fiscal_Year__c Picklist
NSCRM_Picklists_Value.xlsx
Lookup(Accounts
Billing Address
(Billing Entity))
City
Page 6 of 69
Province Lookup
Taxcode
Legal Name
Country Lookup
Rich Text
Account Plan Account_Plan__c
Area(131.072)
See the
Work Start Time Work_Start_Time__c Picklist
NSCRM_Picklists_Value.xlsx
See the
Work End Time Work_End_Time__c Picklist
NSCRM_Picklists_Value.xlsx
Annual_Leave_Days
Annual Leave number
__c
Health_Insurance__ Yes
Two options
Health Insurance c No (default)
Page 7 of 69
LEGAL DETAILS CHANGE PROCESS
1.11 Process Overview
This is the process for Consultant to update legal details (customer legal information). Updating legal details needs
to go through Approval from Finance then updating to AX. Legal details are:
- Company Taxcode
CRM NS and CRM VNW use the same customer code in AX, therefore FA approved LDC of VNW or NS will be
affected them all CRM VNW and NS.
1.1 Is Customer axisted in Based on field “Created in AX” = yes or no. If no, legal details fields are
AX? enable to edit direct in Account CRM form.
1.0 Sales requested LDC From Account ribbon, “Legal Details Change” button is anable to create a Refer 5.3.1 LDC information
Page 8 of 69
form LDC form. The status of LDC is Draft
2.0 Sales request for From LDC ribbon, Sales can submit the LDC for approval. The status of
aprroval LDC is FA review.
3.0 & Approval process Need to be able to configure who are the approvers.
4.0 Approver will receive a notification email when Consultant or BS request
for approval.
Approver can approve or reject the request.
5.0 Update Account in When the Update Legal Details Request is approved, system will update
CRM Account information in CRM based on the approved Update Legal Details
Request.
6.0 API from CRM to AX When the Update Legal Details Request is approved, system will update
Customer information in AX based on the approved Update Legal Details
Request
7.0 Update LDC to VNW When the Update Legal Details Request is approved, system will update
Account Account information in CRM based on the approved Update Legal Details
Request.
Approval Status Option set Draft When user change the status of
Page 9 of 69
Approval Status to Request for
Approval, a notification email
FA Review
will be sent to Finance PIC
Rejected
Completed
Reject Reason Text
Page 10 of 69
CONTACT/CANDIDATE MANAGEMENT
1.15 Process Overview
An account has more than one contact associated with it, especially when you're working with a larger company
with many departments or locations and you deal with several people to manage the account.
Long Text
Critical Details Critical_Details__c
Area(2000)
Salutation Option
Last_Name_Local__
Last Name text(40)
c
First Name
text
(local)
Last Name
text
(Local)
Current
Current_Position__c text(100)
Position
Refer the
Department Department__c Picklist NSCRM_Picklists_Value.xls
x
Refer the
ts2__EEO_Gender__
Gender Picklist NSCRM_Picklists_Value.xls
c
x
Phone Phone Text
Mobile Phone
Page 11 of 69
x
Email Email
Secondary Secondary_Email__
Email
Email c
ts2__LinkedIn_Profil
Linkedin Profile URL
e__c
Mailing Address
Mailing Country
Mailing Street
Mailing City
Mailing
Zip/Postal
Code
Current
Current_Position__c Text(100)
Position
Present Present_Company_
Lookup(Account)
Company _c
Current Current_Company_
Text(255)
Company _c
Refer the
Current Work Current_Work_Cou
Picklist NSCRM_Picklists_Value.xls
Yes Country ntry__c
x
Refer the
Current Work Current_Work_Loca
Picklist NSCRM_Picklists_Value.xls
Location tion__c
x
Refer the
Job Type Job_Type__c Picklist NSCRM_Picklists_Value.xls
x
Status is automatically updated:
when the placement is approved in
CRM “People Status is changed (by
ts2__People_Status
People Status Picklist system) to "Hired".
__c
Active The status of unsuccessful
Hired candidates is changed (by system) to
Inactive "Inactive".
ts2__Candidate_So
Source Lookup(Source)
urce__c
Page 12 of 69
x
Current ts2__Current_Salary
Currency
Monthly Salary __c
Desired ts2__Desired_Salary
Currency
Monthly Salary __c
Page 13 of 69
CANDIDATE SEARCH
1.19 Process Overview
The most important tool for Consultant. They are spending 60% of time of a working day for searching candidates.
We try to make this tool more faster, centralize, save more time of Consultant. This search tool is not Dynamcis
CRM original function. This is a customize tool and will be embedded into CRM that allows to search
NS/Primus/VietnamWorks's resumes. Consultant doesn't need to open Primus/VNW to search.
The target of search tool is 5-6 seconds to return the search result.
Design:
Page 14 of 69
1.21 Business Requirements & Solutions
Step Activity System Requirement Proposed Solution Comments
1.0 Consultant The Candidate search page allows Customize a Search Page that embedded Refer the Search mockup
make a user to search on NS, Primus or into CRM system.
Page 15 of 69
Candidate Vietnamworks Databases.
search in CRM
2.0 API search When Consultant makes a search System required API of Primus and
& candidates the API call to Primus or VNW Vietnamworks to return the search result.
2.1 system to return the search result
& based on the parameters.
3.0
4.0 Download CV Consultant click to download full System required API of Primus and VNW
contact information to check the available credits and allow to
download or not.
5.0 API check the When user click to download full If credits remaining of NS account in
& avaible RS contact information of Candidate, VNW or Primus > required credits of the
5.1 credits in VNW API call to Primus or VNW to check CV allow to download full contact
& or Primus Resume Search credits of that user information and minus credits
6.0 are enough or not. If credits remaining of NS account in
& VNW or Primus < required credits of the
6.1 CV return the warning to CRM.
If the API fail -> return error result include
the error message to API.
7.0 Duplicate Based on contact information of API return candidate full information
Detection resume (email and phone number),
detect in CRM that resume is
existing or not.
8.0 Create a new A new candidate is created in CRM If system detects no duplicated found
Canidate with source (VNW or Primus) create a new candidate
Search Resume
Route: /user/:userId/resume/search
Method: GET
Authentication with Header: Authorization: Bearer {md5(userId + 'vnw2020')}
Request Params
Param (*)
page (default: 1) optional
pageSize (default: 20) optional
searchKeyWords required
id1,id2,id3, ... from Filtering Options locations (multiple separated by
categories optional
comma)
id1,id2,id3, ... from Filtering Options locations (multiple separated by
expectedLocations optional
comma)
Page 16 of 69
homeAddressLocation Id from Filtering Options locations (single)
optional
lastResumeUpdateFrom
timestamp, sorted desc
optional
yearsOfExp Id from Filtering Options optional
salaryCurrency USD/VND optional
salaryRange 1000-2000 optional
jobLevel Id from Filtering Options (single) optional
language Id from Filtering Options (single) optional
languageProficiency
Id from Filtering Options (single) optional
(*) Request with missing optional params, value will be default or All
- Response {
"total" : number,
{
"id" : number,
"credit" : number,
"name" : string,
"jobTitle" : string, "expectedJobTitle": string "latestCompany": string, "yearsOfExperience" : number, "expectedSalary"
: number, "gender" : string,
"birthdate" : timestamp, "locations" : string,
"lastUpdateResume" : timestamp,
"viewStatus": bool }
]}
Page 17 of 69
View Resume
Route: /user/:userId/resume/:resumeId
Method: GET
Authentication with Header: Authorization: Bearer {md5(userId + 'vnw2020')}
Response
{
"code": HttpStatusCode,
"id": number,
"credit": number,
"myCredit": number,
"name": string,
"jobTitle": string, "latestCompany": string, "phone": string,
"email": string, "yearsOfExperience": number, "expectedSalary": number, "gender": string,
"birthday": timestamp, "locations": string, "lastUpdateResume": timestamp "viewStatus": bool,
"employerHistory": string, "educationHistory": string, "certificates": string,
"skills": string,
"CVFile": "link"
Buy Resume
Route: /user/:userId/resume/:resumeId/buy
Method: POST
Authentication with Header: Authorization: Bearer {md5(userId + 'vnw2020')}
Response
{
"code": "HttpStatusCode", "message": "string"
Filtering Options
Route: /filtering-options
Method: GET
Authentication with Header: Authorization: Bearer {md5(userId + 'vnw2020')}
Response
{
"code": "HttpStatusCode", "categories": "OptionValue[]",
"cities": "OptionValue[]", "nationalities": "OptionValue[]", "locations":"OptionValue[]", "yearsOfExperiences":
"OptionValue[]", "levels": "OptionValue[]",
"languages": "OptionValue[]", "languageLevels": "OptionValue[]", "educations": "OptionValue[]", "genders":
"OptionValue[]"
Page 18 of 69
} OptionValue =
{
"id": "number", "name": "string"
PRIMUS-CRM Integration
Page 19 of 69
CONTRACT MANAGEMENT
1.23 Process Overview
This is the process for Consultant to conduct the recruitment process, from the Job Order to Placement.
1.0 Consultant creates a A contract is created with Draft status, Refer: 8.4
Contract in CRM Consultant can edit the contract
information.
2.0 Consultant submits Contract has status “Submitted for Approval Button Group is design based
the contract for Approval” on Contract status and user role:
approval Contract is not able to edit information Consultant click “Submit for Approval”
under this status. ribbon button for approval.
3.0 RD approves the After Consultant submits the contract, Regional Director click “Aprrove” ribbon
contract a email notification is sent to Regional button for approval.
Director for approval. RD can click the
link in the email or navigate to CRM >
Contract: to approve the contract.
An approval contract is not able to edit
information
4.0 RD rejects the After Consultant submits the contract, Regional Director click “Reject” ribbon
contract a email notification is sent to Regional
Page 20 of 69
Director for approval. RD can click the button for approval.
link in the email or navigate to CRM >
Contract: to reject the contract.
An email notification will sent to
Contract Owner with the reject reason.
A rejected contract is able to edit
information and consultant submits the
correction for approval again (step:
2.0;3.0;4.0)
Contract_Descripti
Contract Description Text(150)
on__c
Lookup(User,Grou
Owner
Yes p)
1. Client - New
ts2__Contract_Typ 2. Client - Renewal
Contract Type Picklist
e__c 3. Client - Inactive
Yes 4. PO
Contract has status
1. Draft "Submitted for Approval" can
ts2__Contract_Stat 2. Submitted for be seleted in order but the
Contract Status Picklist
us__c Approval order can not be submitted
3. Approved for BS review or FA review P-
Yes 4. Rejected Based.
Terms_Delivered_B
Terms Delivered By Lookup(User)
y__c
Standard Fee by
Number
Monthly Gross Salary
Guarantee_Period_
Guarantee Period Number
_c
Page 21 of 69
Quarters
Net 0
Net 7
Net 10
Net 14
Net 15
ts2__Payment_Ter Net 21
Payment Terms Picklist
ms__c Net 30
Net 30 after EOM
Net 35
Net 45
Net 60
Net 90
Special_Conditions
Special Conditions TextArea
__c
Page 22 of 69
JOB ORDER MANAGEMENT
1.27 Process Overview
This is the process to manage Purchase Order when customer make an order in VNW website & conduct payment
via Bank transfer.
2.0 Distribute Job order From CRM, consultant can System required job posting API Refer 10. Job Posting distribution
to diferrent Job distribute a job order to of and receiving applications.
board diferrent Jobboards - Vietnamworks.com
- Primus.com
- Enworld.com.vn
3.0 & Application can be - From CRM, receiving System required CRM API to Refer 10. Job Posting distribution
3.1 & applied from Job applications from job receive Applications from Job and receiving applications.
3.2 board or manually board via API. boards
from Consultant - From CRM, Cosultant can
apply candidate to a job
Page 23 of 69
order.
4.0 Job order status is After a successful placement is A workflow run to update JO
updated converted from Application, status = “Close as Won” when
automatically “Closed System update the status of JO Placement is created on from JO
as Won” to “Closed as Won”
5.0 Job order status is - Jobs with no activity A workflow runs to update JO
updated automatically closed after status = “Closes as Lost” when:
automatically or 365 days.
Job Order’s “Last Modified Date”
manually to “Closed - Consultant can update greater than 365 days
as Lost” status of job Order to OR
“Closed as Lost” with Consultant can click to ribbon
reason. button “Closed as Lost” and
select status reason.
6.0 Re-open a closed job Consultant can re-open a closed Consultant clicks to “Re-open”
order JO, and status of closed JO ribbon button
change to “Open”
Lookup(Accou
Account ts2__Account__c
Yes nt)
Lookup(Conta
Client Contact Client_Contact__c
ct)
Internal_Job_Title_
External Job Title Text(80)
Yes _c
ts2__Job_Number_
Job Number Auto Number
_c
Australia
India
Japan
Korea
Job Location JXT_Location__c Picklist New Zealand
Singapore
Thailand
Vietnam
Yes Overseas: Other Areas
Open
Status ts2__Status__c Picklist Closed as Won
Closed as Lost
Status Reason Picklist In Progress Open:
Successful Placement - In Progress
Failed - Closed by Competitor Closed as Won
Failed - Closed by Client - Successful Placement
Pending/Cancelled by client Closed as Lost
- Failed - Closed by
Competitor
- Failed - Closed by Client
Page 24 of 69
- Pending/Cancelled by
client
Will be provided by NS
JXT_Job_Categorie
Sector Picklist Management – change to
s__c
Yes “Sector”
Max Salary
Annual_Fixed_Sala
Min Salary Currency
ry__c
ts2__Application_C Roll-Up
Application Count
ount__c Summary
Send_Out_Count_ Roll-Up
Send Out Count
_c Summary
Placement Count
ts2__Job_Advertise
Rich Text Area
Job Advertisement ment__c
Page 25 of 69
Lookup(User,G
Owner
roup)
Page 26 of 69
JOB POSTING DISTRIBUTION AND RECEIVING
APPLICATIONS
1.31 Process Overview
This is the process distributing a job order on different job boards:
- Vietnamworks.com
- Primus.vn
- Enworld.com.vn
Page 27 of 69
- Enworld.com.vn - Vietnamworks.com
- Primus.com
- Enworld.com.vn
2.0 Job is online A Job is online on which JB that The API of Job boards return:
Consultant has selected. - JobID
API returns JobID to CRM - Job information
2.1 Error response When a job push to JB is failed, the API The API should response:
& response to CRM: - Unauthorized
3.0 - Error code - No job services available
- Error message - Forbbiden
5.0 Job seeker applies to API job When a Job seeker applies to a API job, The API return application:
the application will be pushed to CRM - JobID
under JobID accordingly
- Resume file
- Application information
Email: test.test1@yopmail.com
Page 28 of 69
APPLICATION MANAGEMENT
1.35 Process Overview
This is the process manage Application status change in CRM.
1.1 Update Candidate Status The related Candidate status will be The CRM workflow run to update
& when Application Status is updated automatically to: Candidate status when Application
1.2 “New” Status changes.
- “New-Candidate Applies” if
Candidate applies on Job board
- “New-Consultant Applies” if
Consultant applies.
2.1 Update Candidate Status The related Candidate status will be The CRM workflow run to update
when Application Status is updated automatically to “Send Out” Candidate status when Application
Status changes.
Page 29 of 69
“Send Out” when Applications status is “Send Out”
3.1 Update Candidate Status The related Candidate status will be The CRM workflow run to update
when Application Status is updated automatically to “First Interview” Candidate status when Application
“1st Interview/Haken when Applications status is “1st Status changes.
Introduction” Interview/Haken Introduction”
5.1 Update Candidate Status The related Candidate status will be The CRM workflow run to update
when Application Status is updated automatically to “Final Interview” Candidate status when Application
“Final Interview” when Applications status is “Final Status changes.
Interview”
7.0 Consultant converts When the Candidate accepts the offer, Refer 12.
Application to Placement Consultant convert Application to Placement
Placement with status “Offer Accepted” Process
7.1 Update Candidate Status The related Candidate status will be The CRM workflow run to update
when Placement is updated automatically to “Offer Candidate status when the
generated Accepted” Placement is generated Placement is generated.
8.0 Update Candidate people When the Application is rejected, the The CRM workflow run to update
status to “Inactive” Candidate people status is updated to Candidate people status when the
“Inactive” Application is rejected.
Page 30 of 69
ct__c ate)
Lookup(Accoun
Yes Account ts2__Account__c t)
New
Rejected
Send Out
1st Interview/Haken Introduction
2nd Interview and onwards
First_Interview_Date__
First Interview Date c Date
Final_Interview_Date__
Final Interview Date c Date
Calculated_Created_D
Created Date ate__c Formula
Created By Lookup(User)
Page 31 of 69
PLACEMENT
1.39 Process Overview
This is the process to manage Placement status change.
2.0 Consultant submit When Consultant click “Submit for Application status is “Offer
Placement for review Review” ribbon button. Accepted” AND Consultant role
The Placement status is changed “Submit for Review” is enabled to
to “Submitted for Review” click.
All fields are read only
Page 32 of 69
3.0 Order is automatically From step #2, Order is Refer 13. Order Approval
generated automatically generated with Process
status “Draft”
4.0 Placement status is The Placement status is The workflow run to update
updated to “Approved” automatically “Approved” if the Placement status when Order
Order status is updated to “P- status is “P-Based”
Based”
4.1 Update Contact People When the placement approved, The workflow is run when
Status the contact people status is Placement status is changed.
updated to “Hired”
Currency Picklist
Applicable Applicable_TC_Co Lookup(Contrac
Yes T&C/Contract ntract__c t) Contract Information
Placement_Percen
Placement % tage2__c Formula Standard fee from Contract.
Page 33 of 69
= TRUE, ( Allowance_Amount_2__c *
Number_of_months_Allowance_2__c ),0)) +
(IF( Included_in_Billable_Salary_Allowance_3__c
= TRUE, ( Allowance_Amount_3__c *
Number_of_months_Allowance_3__c ),0))
Monthly Gross Monthly_Gross_Sal
Yes Salary ary__c Currency
Number of Months Number_of_Mont
(Salary) hs_Salary__c Number
Accommoda
Allowance_Types_ tion
Allowance Types 1 1__c Picklist
Allowance Amount Allowance_Amoun
1 t_1__c Currency
No. of months Number_of_month
(Allowance 1) s_Allowance_1__c Number
Included_in_Billabl
Included in Billable e_Salary_Allowanc
Salary e_1__c Checkbox
Allowance_Types_
Allowance Types 2 2__c Picklist
Allowance Amount Allowance_Amoun
2 t_2__c Currency
No. of months Number_of_month
(Allowance 2) s_Allowance_2__c Number
Included_in_Billabl
Included in Billable e_Salary_Allowanc
Salary e_2__c Checkbox
Allowance_Types_
Allowance Types 3 3__c Picklist
Allowance Amount Allowance_Amoun
3 t_3__c Currency
No. of months Number_of_month
(Allowance 3) s_Allowance_3__c Number
Included_in_Billabl
Included in Billable e_Salary_Allowanc
Salary e_3__c Checkbox
Placement_Date__
Placement Date c Date Permanent Placement Information
Start_Confirmed__
Start Confirmed c Checkbox
Page 34 of 69
Client_PO_Numbe
Client PO Number r__c Text(100)
Lookup(Contact
Yes Billing Contact Billing_Contact__c )
LEFT(Billing_Contact_Fields__c,
Work Phone Work_Phone__c Formula FIND('|',Billing_Contact_Fields__c)-1)
LEFT(TRIM(SUBSTITUTE(Billing_Contact_Fields__c
,
Work_Phone__c+'|',' ')),
FIND('|',TRIM(SUBSTITUTE(Billing_Contact_Fields
__c,
Work Email Work_Email__c Formula Work_Phone__c+'|',' ')))-1)
LEFT(Billing_Contact_Fields2__c,
Gender Gender__c Formula FIND('|',Billing_Contact_Fields2__c)-1)
LEFT(TRIM(SUBSTITUTE(Billing_Contact_Fields2_
_c,
Gender__c+'|',' ')),
FIND('|',TRIM(SUBSTITUTE(Billing_Contact_Fields
2__c,
Position Position__c Formula Gender__c+'|',' ')))-1)
Page 35 of 69
$User.UIThemeDisplayed == 'Theme3',
'/apex/' &
$Setup.ts2__ApplicantManagementSystem__c.ts
2extams__Prefix__c & 'AMSMoveCandidates?
id=' & Id,
'/apex/' &
$Setup.ts2__ApplicantManagementSystem__c.ts
2extams__Prefix__c & 'AMSProxyPage?
redirectto=' &
$Setup.ts2__ApplicantManagementSystem__c.ts
2extams__Prefix__c &
'AMSMoveCandidates&id=' & Id
),
IMAGE($Setup.ts2__ApplicantManagementSyste
m__c.ts2extams__Image_Relative_Path__c &
"res/img/move.png", "Move"),
'_blank'
)&""
),
""
)
&
IF(
$Setup.ts2__ApplicantManagementSystem__c.ts
2extams__Snooze_Button__c,
(
HYPERLINK(
'/apex/' &
$Setup.ts2__ApplicantManagementSystem__c.ts
2extams__Prefix__c & "AMSSnoozeCandidates?
stage=application&Id=" & Id ,
IMAGE($Setup.ts2__ApplicantManagementSyste
m__c.ts2extams__Image_Relative_Path__c &
"res/img/snooze.png", "Snooze"),
'_blank'
) & " "), "")
),(
IF( $Setup.ts2__ApplicantManagementSystem__c
.ts2extams__Snooze_Button__c,
(IMAGE($Setup.ts2__ApplicantManagementSyst
em__c.ts2extams__Image_Relative_Path__c &
"res/img/snooze_disabled.png", "Snooze") & "
"), "")
))
Approval_Status__
Approval Status c Picklist
Page 36 of 69
ORDER AND APPROVAL PROCESS
1.43 Process Overview
This is the process to manage Order approval process in CRM. Consultant, BS, FA team can track, manage the
Order's status insight CRM.
2.0 Consultant submits Order for When Consultant click ribbon button Order “Draft” AND
BS approval. “Submit for BS approval”. Consultant role can see
Order has status "BS Review P- “Submit for BS approval”
Order status will be changed to “BS
Based" button.
Review P-Based”. Consulant and BS
cannot edit the Order. All fields are locked.
BS approver will receive an email
notification.
Page 37 of 69
3.0 BS reject the Order BS person can reject the Order and Order “BS Review P-Based”
input the reject reason. AND BS role can see “Reject”
Order status will changed to “BS AND “Approve” button.
Rejected P-Based”. All fields are enable to edit.
Order Owner (Consultant) will be
received an email notification.
3.1 Consultant correct the Order Consultant corrects the order and Order “BS Rejected P-Based”
and submit for approval again click “Submit for BS approval”. AND Consultant role can see
Order status will be changed to “BS “Submit for BS approval”
Review P-Based”. Consulant and BS button.
cannot edit the Order. All fields are locked.
BS approver will receive an email
notification.
4.0 BS submits for FA approval “FA From step #2.0, BS person approve Order “BS Review P-Based”
Review to confirm P-Based” the Order. AND BS role can see “Reject”
Order status will be changed to “FA AND “Approve” button.
Review P-Based”. All fields are locked.
FA approver will receive an email
notification.
5.0 FA rejects the P-Based FA rejects the Order “FA Review P- Order “FA Review P-Based”
Based” and input reject reason. AND FA role can see “Reject”
Order status will be changed to “FA AND “Approve” button.
Rejected P-Based” All fields are locked.
BS and Consultant will receive an
email notification.
5.1 Consultant/BS correct the order Consultant or BS correct the order Order “FA Rejected P-Based”
and submit again and click “Submit for approval”. AND BS/Consultant role can
Order status will be changed to “FA see “Submit for Approval”
Review P-Based”. button.
6.0 FA approves P-Based FA approves the order “FA Review P- Order “FA Review P-Based”
Based”. AND FA role can see “Reject”
Order status will be changed to “P- AND “Approve” button.
Based”. All fields are locked.
Consultant and BS will receive an P-Based date field is updated
email notification. =(today)
6.1 Revert P-Based revenue In case of revert revenue of P-Based. Refer 14. Transaction.
BS team can create negative
transactions under the P-based.
7.0 Reminder Consultant or BS will input the date Before 1 week and 3 working
for Due Date. The workflow will run to date
notify Consultant, Team Manager and
BS to update information or attached
file into Order
8.0 Consultant submit for BS From P-Based, Consultant submits Order “P-Based” AND
review S-Based Order for BS approval. Consultant role can see
Order status will be changed to “BS “Submit for approval” button.
Review S-Based”. All fields are locked.
BS will receive an email notification.
Page 38 of 69
9.0 BS rejects S-Based BS person can reject the S-Based and Order “BS Review S-Based”
input the reject reason. AND BS role can see “Reject”
Order status will changed to “BS AND “Approve” button.
Rejected S-Based”. All fields are enable to edit.
Order Owner (Consultant) will be
received an email notification.
9.1 Consultant correct the order Consultant corrects the order and Order “BS Rejected S-Based”
and submit again click “Submit for approval”. AND Consultant role can see
Order status will be changed to “BS “Submit for approval” button.
Review S-Based”. Consulant and BS All fields are locked.
cannot edit the Order.
BS approver will receive an email
notification.
10.0 Hold on: LDC BS person approves the Order “BS Refer 5 Legal Details
Review S-Based”. Change Process
If Account.IsPendingLDC? = yes ->
Order status will be updated to “Hold
on: LDC”.
The Order “Hold on: LDC” will be
update to “BS Review S-Based” after
the LDC is approved by FA.
11.0 BS submits for FA review S- BS person approves the Order “BS Order “BS Review S-Based”
Based Review S-Based”. AND BS role can see “Reject”
If Account.IsPendingLDC? = no -> and “Approve” ribbon button.
Order status will be updated to “FA All fields are locked.
Review S-Based”.
12.0 FA rejects the S-Based FA rejects the Order “FA Review S- Order “FA Review S-Based”
Based”. AND FA role can see “Reject”
Order status will be updated to “FA and “Approve” ribbon button.
Rejected S-Based”. All fields are locked.
BS and Consultant will be received an
email notification.
12.1 Consultant/BS corrects the Consultant/BS corrects the order and Order “FA Rejected S-Based”
Order and submits again click “Submit for approval” again. AND Consultant/BS role can
Order status will be changed to “FA see “Submit for approval”
Review S-Based”. button.
13.0 S-Based FA approves the Order “FA Review S- Order “FA Review S-Based”
Based” and FA role can see “Reject”
Order status will be updated to “S- and “Approve” ribbon button.
Based”. All fields are locked.
BS and Consultant will be received an
email notification.
15.0 Revert S-based revenue in BS can revert S-based revenue in BS opens the S-Based and
CRM CRM (S-Based has created in AX). create negative transactions.
The negative transactions
cannot sync to AX.
Page 39 of 69
15.1 Revert S-based revenue in AX In AX, FA person can revert revenue FA opens the S-Based and
S-Based. create negative transactions.
Currency Picklist
Yes Transaction Type Transaction_Type__c Picklist
Page 40 of 69
OR
pull from the Placement object
Page 41 of 69
Gender__c+'|',' ')),
FIND('|',TRIM(SUBSTITUTE(Billi
ng_Contact_Fields2__c,
Gender__c+'|',' ')))-1)
TEXT(Billing_Contact__r.Depart
Division Name Division_Name__c Formula ment__c)
TEXT(Billing_Contact__r.ts2__E
Gender Gender__c Formula EO_Gender__c)
LEFT(Billing_Contact_Fields__c,
FIND('|',Billing_Contact_Fields_
Work Phone Work_Phone__c Formula _c)-1)
LEFT(TRIM(SUBSTITUTE(Billing
_Contact_Fields__c,
Work_Phone__c+'|',' ')),
FIND('|',TRIM(SUBSTITUTE(Billi
ng_Contact_Fields__c,
Work Email Work_Email__c Formula Work_Phone__c+'|',' ')))-1)
Manually checked by
consultant. This is to trigger
the Order get updated and
schedule to send a Success
Enabling Survey survey (HR
Start Confirmed Start_Confirmed__c Checkbox Onboard)
Start Confirmed's Start_Confirmed_s_Dat
Date Checked e_Checked__c Date/Time
Created By Lookup(User)
Page 42 of 69
BS input date for Due date,
remind send to BS and
Consultant and team manager
before 1 week, 3 working
Due Date Date time days.
BS input P-Based
No. (transaction)
Page 43 of 69
TRANSACTIONS
1.47 Process Overview
1.48 To-Be Process Flows
1.49 Business Requirements & Solutions
1.50 Transactions Information
Required? Field Name API Name Type Value Note/Formula
Transaction Item
Name Auto Number
Yes Order (EW) Order_EW__c Lookup (Order)
Page 44 of 69
Currency Picklist
Transaction Item Order_Item_Amount_
Amount _c Currency
Transaction Item Order_Item_Quantity
Quantity __c Number
Order_Item_Amount__c
*
Transaction Item Order_Item_Quantity__
Total Order_Item_Total__c Formula c
Page 45 of 69
PUSH S-BASED FROM CRM TO AX PROCESS
1.51 Process Overview
Continute CRM order approval process. Order status is “S-Based” will be automatically pushed into Dynamics AX
(create AX Sales Order)
Page 46 of 69
1 Create PO When Finance approve PO, CRM -Create new WCF API to work with AX AIF
in AX connect to AX to create PO service.
-Create new field AX PO ID in CRM PO Entity.
-Create new field CRM PO/SO Id in AX Sales
Table.
-WCF will create PO via AX AIF service.
-If AX create PO fail, AX will return error
result include error message to WCF API,
WCF API will track error log and continue to
return error message to CRM. CRM show
error message and stop approve process.
-If AX create PO successfully, AX mark this
PO is integrated from CRM and post
confirmation, invoice later by batch job
4 Write System have to write log in CRM WCF will connect to CRM organization
integration when: service to write log into log table.
log in CRM - WCF cannot connect to AX AIF
service.
- WCF create AX PO successfully.
- WCF create AX PO fail.
PO Single/PO
Sales order type
Package/SO
Sales header Enum Single/SO Package
Customer code String (20)
Invoice customer String (20)
Currency String (3)
Email
Mode of delivery String(10) Get from Customer data
Page 47 of 69
- If sales order type is PO: get
from customer data
Payment term String(10) - If sales order type is SO: get
from AR parameter >
VTVPostingPaymTerm
Method of payment String(10) Get from Customer data
Site String (10) Get from Customer data
Warehouse String (10) Get from Customer data
Sales group Id String(10)
Sales assigned
String (20)
(SalesTaker)
Employee Id
Sales in charged
String (20)
(SalesResponsible)
Employee Id
Sales tax group String (10) Get from Customer data
Tax exempt number String (20) Get from Customer data
Total discount amount Real
Page 48 of 69
Reference sales order number
String (20)
Reference sales order line
number
Real
Delivery date Date System date
Page 49 of 69
ACTIVITIES
1.55 Process Overiew
1.56 To be Process flows
1.57 Business Requirements and Solution
1.58 Activities Information
Required? Field Name API Name Type Value Note/Formula
Call
BD Call
Candidate Engagement
Career Counselling
Complaint
Complaint Action
Type Auto Number Other
Subject Text
Lookup all CRM entities
Related To Look up
Long Text
Comments Area(32000)
Yes Account Lookup Account
Name
Yes Mobile From Contact
Yes Phone From Contact
Yes Email From Contact
Status Picklist
Priority Picklist
Yes Assigned To Lookup(User)
Created By Lookup(User)
Page 50 of 69
Page 51 of 69
REPORTS
1.59 Business Support Reports
Contract Report:
- Year
- Month
- Input Date
- Tax code
- Short name
- Company Name
- Client Source
- Sector
- PIC
- Team
- Signed Date
- Minimum Fee
- Fee
- Expiry Date
- Days to expiration
- Payment term
- Credit term
- Refund
- Guarantee Date
- New Client
- Renew Client
- Appendix
P-Based Tracking
- Name of Consultant
- Code
- Type
- Team
- Starting Date
- Jan
- Feb
- Mar
- Quarter To Date
- Q1 Target
- Variance vs Target
- Apr
- May
Page 52 of 69
- June
- Quarter To Date
- Q2 Target
- Variance vs Target
- H1 Revenue
- H1 Target
- Variance vs Target
- Jul
- Aug
- Sep
- Quarter To Date
- Q2 Target
- Variance vs Target
- Oct
- Nov
- Dec
- Quarter To Date
- Q4 Target
- Variance vs Target
- H2 Revenue
- H2 Target
- Variance vs Target
- YTD Revenue
- YTD Target
- Variance vs Target
S-Based Tracking
- Billing Year
- Billing Month
- Code
- Consultant
- Consultant code
- Team
- Client
- Position
- Candidate
- Placement Date
- Starting Date
- Due Date
- Ebill Date
- Amount (VND)
- No of Bill
- % Defer
- Defer - Amount (VND)
Page 53 of 69
- Defer - Amount (USD)
- Affter Defer – Amount (VND)
- Affter Defer – Amount (USD)
- Revert Date
- Revert Year
- Revert Month
- Revert Amount (VND)
- Revert Amount (USD)
Page 54 of 69
Page 55 of 69
Recruitment Fee Breakdown-Minimum Fee-2TimesCharge
Page 56 of 69
Recruitment Fee Breakdown-Full Fee
Page 57 of 69
Recruitment Fee Breakdown-Full Fee-2TimesCharge
Page 58 of 69
Recruitment Fee Breakdown-Fixed Fee
Page 59 of 69
Recruitment Fee Breakdown-Fixed Fee-2TimesCharge
Page 60 of 69
Recruitment Fee Breakdown-Discount
Page 61 of 69
Recruitment Fee Breakdown-Discount-2TimesCharge
Page 62 of 69