You are on page 1of 67

Table of Contents

Document Version Control..................................................................................................................................4


1 INTRODUCTION..............................................................................................................................................0
1.1 Purpose of the document...........................................................................................................................0
1.2 Document structure...................................................................................................................................0
2 SYSTEM OVERVIEW......................................................................................................................................2
2.1 Systems Information.................................................................................................................................2
2.2 High Level Diagram..................................................................................................................................2
2.3 Vision and Scope.......................................................................................................................................2
3 DYNAMICS CRM FUNCTIONAL ENTITIES.............................................................................................4
3.1 Process Overview......................................................................................................................................4
3.2 To-Be Process Flows.................................................................................................................................4
3.3 Business Requirements & Solutions.........................................................................................................4
4 ACCOUNT MANAGEMENT..........................................................................................................................6
4.1 Overview...................................................................................................................................................6
4.2 Account Information.................................................................................................................................6
5 LEGAL DETAILS CHANGE PROCESS.......................................................................................................8
5.1 Process Overview......................................................................................................................................8
5.2 To-Be Process Flows.................................................................................................................................8
5.3 Business Requirements & Solutions.........................................................................................................8
5.4 LDC Information.......................................................................................................................................9
6 CONTACT/CANDIDATE MANAGEMENT...............................................................................................11
6.1 Process Overview....................................................................................................................................11
6.2 To-Be Process Flows...............................................................................................................................11
6.3 Business Requirements & Solutions.......................................................................................................11
6.4 Contact/Candidate Information...............................................................................................................11
7 CANDIDATE SEARCH..................................................................................................................................14
7.1 Process Overview....................................................................................................................................14
7.2 To-Be Process Flows and Mockup..........................................................................................................14
7.3 Business Requirements & Solutions.......................................................................................................15
7.4 API Information......................................................................................................................................16
8 CONTRACT MANAGEMENT......................................................................................................................20
8.1 Process Overview....................................................................................................................................20
8.2 To-Be Process Flows...............................................................................................................................20
8.3 Business Requirements & Solutions.......................................................................................................20
8.4 Contract Information...............................................................................................................................21
9 JOB ORDER MANAGEMENT.....................................................................................................................23
9.1 Process Overview....................................................................................................................................23

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

Document Version Control


Version Date Author Reason for update
1.0 15/Oct/2020 Quyen Nguyen Initial

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.

1.1 Purpose of the document


The purpose of the Functional Design Document (FDD) is the second point of the solution and system development
and is a collaborative effort between all business and technology stakeholders. The purpose of the Functional
Design Document (FDD) is to design requirements for the requested system solution.

The objective of the Functional Design Document is to provide enhanced documentation actual cycles will be
implemented in the correct project of .

The purpose of the FDD can be summarized as follows:


 To specify and document design for the implementation cycles
 To form the basis of planning of next phases
 To form the basis of quality assurance
 To form the basis of user acceptance testing

1.2 Document structure


Each Functional Design Document resembles a functional area (Business Unit) within the business. These
documents will then unpack the process design for the different functions within the Business Unit by providing:

 Company/Business Unit overview


 Vision and Scope
 Process Overview
 To-Be process flow
 Business requirements and solution
 Entity Information

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

1.4 High Level Diagram

1.5 Vision and Scope


NVG has a project vision and scope as following:
 The new platform to support current businesses and able to extend to new businesses in the future.
 Centralize and standardize all business processes and data in one solution.
 Easy to maintain and scale up and down.
 Provide strong features for headhunt services and relationship management.

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).

1.7 To-Be Process Flows


This process describes all the steps to manage Sales process

1.8 Business Requirements & Solutions


List of all requirements
No Activity System Requirement Type Proposed Solution Comments
.
1 System User Person who access into CRM and who Function
management owns the objects in the CRM database

2 Account Business that represents a customer or Function Refer 4. Account


Management potential customer. The company that is Management
billed in business transactions

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.

5 Contract A contract is included Service standard Function Customize Entity Contract


Management fee percentage, Minimum fee,

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, ….

7 Application An individual who applies for a job Function Customize Entity


management & order. And Application status tracking Application and AMS with
AMS system the required fields

8 Placement Placement is a type of order, after


management candidate accept the offer, consultant
will convert the placement to P-Based

9 Sales Order Consultant generate SO from


Placement when Candidate has passed
the probation and Customer is ready to
pay.
10 Activities The activity and notes area helps us
Management keep track of all the interactions with
your customers. Record all important
conversations with the customer or the
communication regarding a record in
Dynamics CRM.
11 Candidate In CRM, Consultant can search Customize a web page and
Searching Candidate of VietnamWorks and Primus embaded into CRM. with
that they don’t need to open VNW or required API from VNW
Primus. and Primus.

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

13 Report Dynamics CRM provide a strong Customize report by SSRS


reporting that can help a business gain that based on NS
a better understanding of who their requirement
customers are, what they are buying
and also see how loyal the customer
really is.

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.

1.10 Account Information


Required? Field API Name Type Value Notes/Formula

Record_Type_Name
Customer Type Option Set
__c

Yes Account Number   AutoNumber

Account_Name_Tex
Account Name Text(255)
Yes t__c

Company (Local Company_Local_Na


Text(255)
Name) me__c

Long Text
Critical Details Critical_Details__c
Area(2000)

See the
Company Status ts2__Status__c Picklist
Yes NSCRM_Picklists_Value.xls

Parent Account   Lookup(Account)

Phone   text

Yes Owner   Lookup(User)

See the
Account Source   Picklist
NSCRM_Picklists_Value.xlsx

Company's Business See the


Picklist
Type NSCRM_Picklists_Value.xlsx

Year Founded Year_Founded__c Text(155)

Website   URL(255)

Yes Primary Industry Primary_Industry__c Picklist NS confirm later

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)

This field is read only.


Yes The value is “Yes” mean
Two options
No (default) this customer has been
Is Created in AX? created in AX.

This field is read only.


Yes The value is “Yes” mean
Two options this customer has the
No (default) Legal details change is
Is Pending LDC? pending.

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 Legal Name

- Company Taxcode

- Company Billing address

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.12 To-Be Process Flows


This process describes all the steps to update legal details

1.13 Business Requirements & Solutions


List of all requirements
Steps Activity System Requirement Comments

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.

1.14 LDC Information


Required Field Type Description Notes
?
Yes Title Text (50)

yes Account Link to Account

Old Legal Name Display current Account Legal Name


Old Tax Code Display current Account Tax Code
Old Billing Address Display current Account Billing Address
Street Text (150) Street
Old Billing Address Display current Account Billing Address
District Link to District District
Old Billing Address Display current Account Billing Address
City/Province Link to City/Province City/Province
Old Billing Address Display current Account Billing Address Read only field, display the
Country Link to Country Country information of the Account

New Legal Name

New Tax Code

New Billing Address


Street Text (150)

New Billing Address


District Link to District
When a new form is created, all
New Billing Address
the New are copied from the
City/Province Link to City/Province
Old. If user edits the New, the
New Billing Address field will be highlighted (in
Country Link to Country yellow) in the form

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.

A Candidate is individual profile and can be applied to different job order.

1.16 To-Be Process Flows


1.17 Business Requirements & Solutions
1.18 Contact/Candidate Information
Require Field API Name Type Value Notes/Formula
d?
Contact Record
  Record Type
Type

Yes Contact No Contact_No__c Auto Number

Long Text
Critical Details Critical_Details__c
Area(2000)

Salutation   Option

Last_Name_Local__
Last Name text(40)
c

First Name   text

Name Name Text

First Name
  text
(local)

Last Name
  text
(Local)

Account Name Account Lookup(Account)

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

Other Phone   Phone

Preferred Preferred_Languag Picklist Refer the


Language e__c NSCRM_Picklists_Value.xls

Page 11 of 69
x
Email   Email

Secondary Secondary_Email__
Email
Email c

Skype Skype__c text(50)

ts2__LinkedIn_Profil
Linkedin Profile URL
e__c

Contact Status Refer the


Contact_Status_Clie
(Client/Account Picklist NSCRM_Picklists_Value.xls
nt_Account__c
) x
Linked Linked_Candidate_
Lookup(Contact)
Candidate _c

Contact Owner   Lookup(User)

Mailing Address    

Mailing Country    

Mailing Street    

Mailing City    

Mailing
Zip/Postal    
Code

Yes Birthdate   Date

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

Sourced By Sourced_By__c Lookup(User)

Salary Currency Salary_Currency__c Picklist Refer the


NSCRM_Picklists_Value.xls

Page 12 of 69
x
Current ts2__Current_Salary
Currency
Monthly Salary __c

Annual Variable Annual_Variable_Sa


Currency
Salary lary__c

Other Cash Other_Cash_Allowa


Currency
Allowances nces__c

Desired ts2__Desired_Salary
Currency
Monthly Salary __c

Desired Total Desired_Total_Com


Currency
Compensation pensation__c

Resume Last ts2__Resume_Last_


Date/Time
Updated Updated__c

ts2__Text_Resume_ Long Text


Text Resume
_c Area(32000)
Refer the
Marital Status Marital_Status__c Picklist NSCRM_Picklists_Value.xls
x
Refer the
Citizenship Citizenship__c Picklist NSCRM_Picklists_Value.xls
x
Linked Contact Linked_Contact__c Lookup(Contact)
Refer the
Application Application_Status_
Picklist NSCRM_Picklists_Value.xls
Status _c
x
Candidate No. Candidate_No__c Auto Number

Primary Desired Primary_Desired_R Refer the


Picklist (Multi-
Region (Multi egion_Multi_Picklist NSCRM_Picklists_Value.xls
Select)
Picklist) __c x
English Resume English_Resume_La
Date/Time
Last Update st_Updated__c

Rich Text Area


English Resume English_Resume__c
(131072)

Local Language Local_Language_Re


Resume Last sume_Last_Update Date/Time
Update d__c

Local Language Local_Language_Re Rich Text Area


Resume sume__c (131072)

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.

1.20 To-Be Process Flows and Mockup

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

8.1 Override Candidate newest information is If system detects duplicated candidate 


candidate updated in CRM. override contact information.
Information

1.22 API Information


NS-VNW API Integration:

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

education Id from Filtering Options (single) optional


nationality Id from Filtering Options (single) optional
gender Id from Filtering Options (single) optional
age 25-30 optional

(*) Request with missing optional params, value will be default or All

- Response {

"code" : HttpStatusCode, "myCredit" : number, "candidates" : {

"total" : number,

"page" : number, "data" : [

{
"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.24 To-Be Process Flows


This process describes all the steps to manage the Contract.

1.25 Business Requirements & Solutions


List of all requirements
Steps Activity System Requirement Proposed Solution Comments

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)

1.26 Contract Information


Required? Field API Name Type Value Notes/Formula

Record Type   Record Type Permanent


Yes Contract Number   Auto Number

Contract_Descripti
Contract Description Text(150)
on__c

Yes Account ts2__Client__c Lookup(Account)

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.

ts2__Contract_Not Long Text


Contract Notes
es__c Area(32000)

Yes Start Date ts2__Start_Date__c Date

Yes End Date ts2__End_Date__c Date

Terms_Delivered_B
Terms Delivered By Lookup(User)
y__c

Standard Fee % Standard_Fee__c Percent

Standard Fee by
Number
Monthly Gross Salary

Yes Minimum Fee Minimum_Fee__c Currency

Fix Fee Currency

Guarantee_Period_
Guarantee Period Number
_c

Guarantee Period By Guarantee_Period_ Picklist Days


By__c Weeks
Months

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

Payment Terms Payment_Terms_M


Text(100)
(Migration) igration__c
10%
VAT VAT__c Picklist
0%

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.

1.28 To-Be Process Flows


This process describes all the steps to manage Job Order status change by system or user manual.

1.29 Business Requirements & Solutions


List of all requirements
Req id Activity System Requirement Proposed Solution Comments

1.0 Consultant create a Refer 9.5 Job Order Information


Job order

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”

1.30 Job Order Information


Requir Field API Name Type Value Notes/Formula
ed?
Long Text
Critical Details Critical_Details__c
Area (2000)

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

Yes Internal Job Title   Text(80)

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

Openings ts2__Openings__c Number


Refer the
Job Level Job_Level__c Picklist
NSCRM_Picklists_Value.xlsx
Refer the
Job Type Job_Type__c Picklist
NSCRM_Picklists_Value.xlsx
ts2__Estimated_Sta
Date Required Date
rt_Date__c

Primary Recruiter ts2__Recruiter__c Lookup(User)

Team Team__c Lookup(Team)

Lead Provider Lead_Provider__c Lookup(User)

Source     Same with Account Source

Applicable Applicable_T_C_C Lookup(Contr


Yes T&C/Contract ontract__c acts)

Primary Job Primary_Job_Funct Will be provided by NS


Picklist
Function ion__c Management

Will be provided by NS
JXT_Job_Categorie
Sector Picklist Management – change to
s__c
Yes “Sector”

Edu/Certification Education_Require Refer the


Picklist
Requirements ments__c NSCRM_Picklists_Value.xlsx
Industry-related
Certification_Requi Picklist (Multi-
Experience Refer the
rements__c Select)
Requirements NSCRM_Picklists_Value.xlsx
Currency   Picklist

Max Salary    

Annual_Fixed_Sala
Min Salary Currency
ry__c

Benefits Benefits__c Text Area

Salary Notes Salary_Notes__c Text Area

Job Description Job_Description__c Rich Text Area

Post Job ts2__Post_Job__c Checkbox

Days to Remain Days_to_Remain_


Number
Open Open__c

Date Closed ts2__Date_Filled__c Date

ts2__Application_C Roll-Up
Application Count
ount__c Summary

Send_Out_Count_ Roll-Up
Send Out Count
_c Summary

1st Interview Count    

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

1.32 To-Be Process Flows

1.33 Business Requirements & Solutions


List of all requirements
Step Activity System Requirement Proposed Solution Comments
s
1.0 Consultant can push a job From CRM, Consultant can decide to A custom html page design to help Refer 10.6 Post
order from CRM to difrrent post a job on one of 3 JBs or all of them. Consultant input further Job page
Job board (JB) There are 3 JBs: information of JB requires fields to information
post a job there.
- Vietnamworks.com
System required job posting API of:
- Primus.com

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

4.0 Repost? Consultant can repost the API job has


failed.
Repeat step #1.

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

5.1 Generate Application in The application will be generated in CRM


CRM when receiving from API.
An email message is sent to Consultant
in-charged.

1.34 Job Posting Distribution Information

Name: Tram Tram

Số điện thoại: 0123456789

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.36 To-Be Process Flows

1.37 Business Requirements & Solutions


List of all requirements
Step Activity System Requirement Proposed Solution Comments
s
1.0 Application is generated Application can be generated from 2 System required API to push Refer 10.3 > 5.0
with status is “New” souces: Applications from Job Boards & 5.1
- Candidate applies to a job from
Jobboard
- Consultant applies a candidate to a
job 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.0 Consultant changes status of The Application is updated to “Send Out”


Application to “Send Out” by manually when Consultant sends this
application to Client.

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.0 Consultant change status of The Application is updated to “1st


Application to “1st Interview/Haken Introduction” by
Interview/Haken manually when Candidate has the 1 st
Introduction” interview with client.

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”

4.0 Consultant change status of The Application is updated to “2nd


Application to “2nd Interview Interview and onwards” by manually
and onwards” when Candidate has the 2nd interview with
client.

5.0 Consultant change status of The Application is updated to “Final


Application to “Final Interview” by manually when Candidate
Interview” has the final interview with client.

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”

6.0 Consultant change status of The Application is updated to “Offer


Application to “Offer Extended” by manually when Candidate
Extended” passes the 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.

1.3 Consultant rejects the From Application in status: New; Send


2.3 Application. Out; 1st Interview/Haken Introduction; 2nd
Interview and onwards; Final Interview;
3.2
Offer Extended, Consultant can reject the
4.1 Application and input reject reasons.
5.2
6.1

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.

1.38 Application Inforrmation


Requir Field API Name Type Value Notes/Formula
ed?
Long Text Area
Critical Details Critical_Details__c
(2000)

Yes Candidate ts2__Candidate_Conta Lookup(Candid

Page 30 of 69
ct__c ate)

Email ts2__Email__c Formula

Internal Job Title ts2__Job__c Master-Detail

From Job Order


External Job Title Internal_Job_Title__c Formula

Lookup(Accoun
Yes Account ts2__Account__c t)

From Job Order


Job Location JXT_Location__c Formula

Yes Application No. Auto Number

Record Type Record Type

New
Rejected
Send Out
1st Interview/Haken Introduction
2nd Interview and onwards

ts2__Application_Statu Final Interview


Overall Status s__c Picklist Offer Extended

Candidate Not Interested


Job Order Cancelled
Job Order Filled – Placed
Job Filled By Client/Competitor
Consultant Rejected After
Screening
Client Rejected

Overall Reject ts2__Overall_Reject_Re Candidate Withdrew


Reason ason__c Picklist Sent by Other Source

First_Interview_Date__
First Interview Date c Date

First_Interview_Feedba Long Text


Interview Feedback ck__c Area(10000)

Final_Interview_Date__
Final Interview Date c Date

Calculated_Created_D
Created Date ate__c Formula

Created By Lookup(User)

Last Modified By Lookup(User)

Page 31 of 69
PLACEMENT
1.39 Process Overview
This is the process to manage Placement status change.

1.40 To-Be Process Flows


This process describes all the steps to create a new Product Price List

1.41 Business Requirements & Solutions


List of all requirements
Step Activity System Requirement Proposed Solution Comments
s
1.0 Placement is generated. Consultant converts Application On the Application form, a ribbon
“Offer Extended” to Placement button is enable when application
that has status “Offer Accepted” has status “Offer Extended”
Consultant can edit Placement
information.

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”

3.1 Order status “P-Based” Refer 13. Order Approval


Process

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”

1.42 Placement Information


Require Field API Name Type Value Notes/Formula
d?
Long Text Area
Critical Details Critical_Details__c
(2000)

Record Type Record Type


Lookup(Contact
Candidate ts2__Employee__c )
Lookup(Accoun
Account ts2__Client__c t)

Job ts2__Job__c Master-Detail Job Order


Official_Job_Title__
Yes Official Job Title c Text(150)
Related ts2__Related_Appli Lookup(Applica
Application cation__c tion)
Placement Placement_Recruit
Recruiter er__c Lookup(User) From Job Order
Responsible_Team
Responsible Team __c Formula From Job Order

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.

Minimum Fee Minimum_Fee__c Formula Minimum Fee from Contract


Guarantee_Period
Guarantee Period __c Formula Guarantee Period from Contract
Guarantee Period Guarantee_Period
By _By__c Formula Guarantee Period By from Contract
Payment_Terms__
Payment Terms c Formula Payment Terms from Contract
Special_Conditions
Special Conditions __c Formula Special Conditions from Contract
Billable Salary Billable_Salary_2__ Formula Salary Information (VN & SG Only) |
c ( Monthly_Gross_Salary__c *
Number_of_Months_Salary__c )+
(IF( Included_in_Billable_Salary_Allowance_1__c
= TRUE, ( Allowance_Amount_1__c *
Number_of_months_Allowance_1__c ),0)) +
(IF( Included_in_Billable_Salary_Allowance_2__c

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

Invoicing Date Invoicing_Date__c Date


Expected_Payment Invoicing_Date__c +
Expected Payment _Date_Calculation_ Applicable_TC_Contract__r.Payment_Terms_Day
Date _c Formula s__c
ts2__Start_Date__c +
Refund_Expiry_Dat Applicable_TC_Contract__r.Guarantee_Period_D
Refund Expiry Date e_Calculation__c Formula ays__c
Yes Start Date ts2__Start_Date__c Date
Yes Start Date Start_Date__c Formula Related_Offer__r.Candidate_Start_Date__c
IF(Billable_Salary__c *
Placement_Percentage2__c>
Minimum_Fee__c,Billable_Salary__c *
Placement_Percentage2__c,
Placement Fee Placement_Fee__c Formula Minimum_Fee__c)
Entity to be Entity_to_be_Invoic Lookup(Accoun
Yes Invoiced ed__c t)

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)

Division Name Division_Name__c Formula TEXT(Billing_Contact__r.Department__c)


Entity_to_be_Invoiced__r.BillingStreet & "," &BR()
&Entity_to_be_Invoiced__r.BillingCity & "," & BR()
&Entity_to_be_Invoiced__r.BillingState & " " &
BR()
&Entity_to_be_Invoiced__r.BillingPostalCode & "
Billing_Address_2_ " & BR()
Billing Address _c Formula &Entity_to_be_Invoiced__r.BillingCountry

Billing Address Billing_Address__c Text Area


Invoicing/Billing Invoicing_Billing_C
Comments omments__c Text Area
Candidate_Source
Candidate Source __c Text(100) Split fee company
Candidate Sourced Candidate_Source
By d_By__c Text(50)
Split_Fee_Compan Lookup(Accoun
Split fee Company y__c t)
Split_Fee_Percent_
Split fee Percent _c Percent
Split_Fee_Amount_
Split fee Amount _c Currency
Split_Fee_Amount_
Split fee Amount new_field__c Currency = Placement Fee * Split Fee %
Control ts2extams__Contro Formula IF(
l_Buttons__c AND(
NOT(ISPICKVAL( ts2__Related_Application__r.ts2
__Application_Status__c,'Rejected')),
ISPICKVAL( ts2__Job__r.ts2__Status__c ,'Open'),
NOT(ISPICKVAL( ts2__Related_Application__r.ts2
__Application_Status__c ,'Incomplete'))
),
(
IF(
$Setup.ts2__ApplicantManagementSystem__c.ts
2extams__Move_Button__c,
(
HYPERLINK(
IF(

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

Status ts2__Status__c Picklist


ts2extams__Substa
Substatus tus__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.

1.44 To-Be Process Flows


This process describes all the steps to manage Customer Service Request

1.45 Business Requirements & Solutions


List of all requirements
Step Activity System Requirement Proposed Solution Comments
s
1.0 Consultant create Order from When Consultant click “Generate A ribbon button “Generate
Placement. Order”, all Placement information is Order” is design to create
Order has status is “Draft”. mapped into Order. Order that associate with
Consultant can edit Order Placement.
information

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.

FA approver will receive an email All fields are enable to edit.


notification.

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.

14.0 S-Based will be generated Refer 14. Push S-based


automatically in Dynamics AX from CRM to AX
Process

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.

16.0 Issue negative invoice From the step #15.1, FA issue e-


invoiced for the negative transactions
to customer.

1.46 Order Information


Requir Field API Name Type Value Notes/Formula
ed?
Yes Order Number Order_Number__c Auto Number

Currency Picklist
Yes Transaction Type Transaction_Type__c Picklist

Responsible Team Responsible_Team__c Picklist

TeamID TeamID__c Picklist

Record Type Record Type


Lookup(User,Gr
Owner oup)
Placement_Recruiter__
Placement Recruiter c Lookup(User)

Order Note Order_Note__c Text Area


Lookup(Placem
Placement Placement__c ent) Placement Details
Lookup(Accoun
Account Account__c t)
Lookup(Job
Job Order Job_Order__c Order)
Lookup(Contact
Candidate Candidate__c )
Placement__r.Official_Job_Title
Official Job Title Official_Job_Title__c Formula __c
HYPERLINK("/"&
Sale_Summary__r.Contract__c,
Sale_Summary__r.Contract__r.
Contract Contract__c Formula Name)
Placement__r.Contract_Type_n
Contract Type Contract_Type__c Formula ew__c
TEXT(Sale_Summary__r.Manag
Managing Country Managing_Country__c Formula ing_Country__c)

Order Date (P-Date) Order_Date__c Date


Service Provided Service_Provided_Date
Date (S-Date) __c Date

Invoicing Date Invoicing_Date__c Date


Expected Payment Expected_Payment_Da
Date te2__c Date
Refund Expiry Date Refundable_Date__c Date Refund Expiry Date calculation:
Start_Date__c +
Applicable_TC_Contract__r.Gu
arantee_Period_Days__c

Page 40 of 69
OR
pull from the Placement object

Billable Salary Billable_Salary__c Currency

Placement Fee Placement_Fee__c Currency


Sum the total amount on all
related order items "Total"
field - The field is a
convenience so that order
items in different currencies
(which is not common, but
may happen) can be
automatically converted into
Total_Order_Amount_ the currency that the order will
Total Order Amount _c Currency be processed in
Placement__r.Split_Fee_Amou
Split Fee Amount Split_Fee_Amount__c Formula nt__c
Split_Fee_Amount_Ne
Split Fee Amount w_Field__c Currency
Total_Order_Amount__c -
Net Total Order Net_Total_Order_Amo Split_Fee_Amount_New_Field_
Amount unt__c Formula _c

Split Fee Split_Fee__c Checkbox Split Free/Replacement Details


Placement__r.Split_Fee_Compa
Split Fee Company Split_Fee_Company__c Formula ny__r.Name
Split_Fee_Company_N Lookup(Accoun
Split Fee Company ew_Field__c t)
Split_Fee_Percent_Ne
Split Fee Percent w_Field__c Percent
Split_Fee_Comment__
Split Fee Comment c Text(150)
Billing_Account__r.BillingStreet
&', '&
Billing_Account__r.BillingStreet
&', '&
Billing_Account__r.BillingState
&', '&
Billing_Account__r.BillingPostal
Code &', '&
Billing_Account__r.BillingCount
Billing Address Billing_Address__c Formula ry
Entity_to_be_Invoiced__r.Billing
Street & ","
&Entity_to_be_Invoiced__r.Billi
ngCity & ","
&Entity_to_be_Invoiced__r.Billi
ngState & ", " &
Entity_to_be_Invoiced__r.Billing
PostalCode & ", " &
Entity_to_be_Invoiced__r.Billing
Billing Address Billing_Address_2__c Formula Country

Client PO Number Client_PO_Number__c Text(100)


Invoicing/Billing Invoicing_Billing_Com
Comments ments__c Text Area
Lookup(Contact
Billing Contact Billing_Contact__c )
Position Position__c Formula LEFT(TRIM(SUBSTITUTE(Billing
_Contact_Fields2__c,

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

Left the Company Left_the_Company__c Checkbox


Left the Company Left_the_Company_Da
Date te__c Date
Terminate sending Terminate_sending_su
surveys rveys__c Checkbox

Level 1 Approver Level_1_Approver__c Lookup(User) Order Approval

Level 2 Approver Level_2_Approver__c Lookup(User)


Draft
BS Review P-Based
BS Rejected P-Based
FA Review P-Based
FA Rejected P-Based
P-Based
BS Review S-Based
BS Rejected S-Based
FA Review S-Based
FA Rejected S-Based
Approval Process Hold on: LDC
Status Approval_Status__c Picklist S-Based Refer 13.2 and 13.3

Processed Date Processed_Date__c Date

Paid Date Paid_Date__c Date

Amount Paid Amount_Paid__c Currency

Invoiced Date Invoiced_Date__c Date

Invoice Number Invoice_Number__c Text(100)

Refund Date Refund_Date__c Date


Orders_Credit_Term__
Credit Term c Text(30)

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)

Team Team__c Lookup(Team)


Yes Recruiter Recruiter__c Lookup(User)
Placement
Dispatched Labor
OutPlacement
Retainer
Yes Service Category Service_Category__c Picklist RPO
Initial Fee
Sourced Resumes
Market Map
Permanent Hire
Hours Worked
Direct Contract
Temp to Perm Conversion
Expenses
Commutation
Training
Fee
Other
Monthly Management Fee
Direct Sourcing Placement
External Agency Placement
Employee Referral
Service Service_SubCategory Internal Transfer
Yes SubCategory __c Picklist Direct Applicant
Transaction Item Order_Item_Descripti
Description on__c Text Area
1. CDD withdrew - Working
environment
2. CDD withdrew - Another
offer, Counter offer
3. CDD withdrew - Family
issue
4. Client rejected – didn’t
meet the expectation
Refund/ 5. Client rejected – Canceled
Termination Refund_Termination_ offer
Reason Reason__c Picklist 6. Other

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

Processed Date Processed_Date__c Date

P-Based No. P_Based_No__c Text(100)

Paid Date Paid_Date__c Date

Amount Paid Amount_Paid__c Currency

Invoiced Date Invoiced_Date__c Date

Invoiced Number Text(100)

Refund Date Refund_Date__c Date

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)

1.52 To-Be Process Flows

1.53 Business Requirements & Solutions


List of all requirements
No. Activity System Requirement Proposed Solution Comments

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

2 Update AX When AX create PO successfully, When AX return successfully message to


PO Id to AX PO id must be update to CRM WCF, AX will include AX PO id and CRM PO
CRM PO PO id also, then WCF will find CRM PO by PO id
and update AX PO Id to CRM PO.

3 Mandatory Sales order type: PO Package, PO


PO Single
information Item, Quantity, Amount, Discount
must have Amount, Customer Id
in AX

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.

1.54 CRM and AX mapping fields


  AX CRM
Note
Entity Field name Data type Fixed value Field name
Sales number String (20)      
Customer requisition
CRM sales order
(PurchOrderFormNum)
String (20)     number

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      

Total discount percentage Real


     
Get primary address from
Delivery address String (250)
Customer data    
VAT Form number String (20)      
VAT Serial number String (20)      
VAT Company name String (200)      
VAT Description String (250)      
New AX field in Table
Case String (60)
SalesTable
   
New AX field in Table
Attention String (80)
SalesTable
   
New AX field in Table
Total invoice text String (1000)
SalesTable
   
New AX field in Table
Customer PO number String (80)
SalesTable
   
Combine of Customer and
Financial dimension
RecId Sales group    
           
Sales number String (20)      
Item number String (20)      
Sales unit String (10) Get from Item data    
Quantity Real      
Sales lines Unit price Real      
Discount amount Real      
Discount percentage Real      
Amount Real      
Line number Real      

Page 48 of 69
Reference sales order number
String (20)      
Reference sales order line
number
Real      
Delivery date Date System date    

- If sales order type is PO: get


Ledger account from get from AR parameter >
VTVAccountPosting
RecId - If sales order type is SO: blank    

- If sales order type is PO: get


Item sales tax group
from get from Item data
String (10) - If sales order type is SO: blank    

Financial dimension Combine of sales header


RecId dimension and item dimensions    

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

Due Date Date

Reminder Set Checkbox

Status Picklist

Priority Picklist
Yes Assigned To Lookup(User)

Created By Lookup(User)

Last Modified By Lookup(User)


Create Recurring
Series of Tasks Checkbox
Start Date
End Date
All-Day Event? Checkbox

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)

Non fianical KPI


Sendout and 1st Interview Count by Activities
New Job Order select time: month, Quarter, year

1.60 Fee Breakdown


Recruitment Fee Breakdown-Minimum Fee

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

You might also like