- Overview
- Change concerning data type for the keywords search of the Read related APIs
- Change concerning the operation in one-line text type, multiple-lines text type, email type and URL type Keywords search of the Read related APIs
- Change concerning the operation in the phone number type Keywords search of the Read related APIs
Overview
For PORTERS HR-Business Cloud API Version3.12, which will be released after the middle of December of 2015, the default operation of APIs will be partly changed.
Check whether or not apps that have been already developed are affected by this change.
Change concerning data type for the keywords search of the Read related APIs
[Supported APIs]
Read of Client, Recruiter, Job, Candidate, Resume, and Process
[Operation of Version 3.11.9]
Version3.11.9 had a defect such that numerical type and currency type were also included for the Keywords search although the search targets are the items in one-line text type, multiple-line text type, phone number type, email type, and URL type according to the specifications of this version.
[Operation of Version 3.12]
The operation will be corrected so that the Keywords search applies only to items in one-line text type, multiple-line text type, phone number type, email type, and URL type.
[Example]
Suppose that the following resume is saved in a company DB. Resume.P_ChangeJobsCount is a numerical type item.
|
Registration Data <Item> |
When sending a request with the single-byte number 5 specified for the Keyword
|
Input Parameter .../v1/resume?partition=999999&condition=Resume.P_Id=11034&keywords=5 |
■Response in the case of Version3.11.9
|
Output XML <Resume Total="1" Count="1" Start="0"> |
■Response in the case of Version3.12
|
Output XML <Resume Total="0" Count="0" Start="0"> |
Change concerning the operation in one-line text type, multiple-lines text type, email type and URL type Keywords search of the Read related APIs
[Target APIs]
Read of Client, Recruiter, Job, Candidate, Resume, and Process
[Operation of Version 3.11.9]
Search was performed while distinguishing double-byte characters from single-byte ones, upper-case characters from lower-case ones, and tabs from spaces.
[Operation of Version 3.12]
The following two changes are made in the Keywords search in Version 3.12.
- Search is performed without distinguishing upper-case characters from lower-case ones, tabs from spaces, and double-byte from single-byte of the alphanumeric characters and the following symbols: ！”＃＄％＆’（）＝－｜￥＾［｛＠｀｝］＊：＋；＿／？． ＞，＜～゛-゜。「」、・
- Search is performed without distinguishing the symbols that belong to the following groups from the symbols within the same group.
Group 1 “”〝〞＂”
Group 2 ’’＇'
Group 3 －ー-
[Example 1]
Suppose that the following resume record is saved in a company DB.
|
Registration Data <Item> |
Example 1-1: When sending a request with a single-byte Katakana string specified for the Keyword
|
Input Parameter .../v1/resume?partition=999999&condition=Resume.P_Id=11034&keywords=ｶﾀｶﾅ |
■Response in the case of Version3.11.9
|
Output XML <Resume Total="0" Count="0" Start="0"> |
■Response in the case of Version3.12
|
Output XML <Resume Total="1" Count="1" Start="0"> |
Example 1-2: When sending a request with a double-byte Katakana string specified for the Keyword
|
Input Parameter .../v1/resume?partition=999999&condition=Resume.P_Id=11034&keywords=カタカナ |
■Response in the case of Version3.11.9
|
Output XML <Resume Total="1" Count="1" Start="0"> |
■Response in the case of Version3.12
|
Output XML <Resume Total="1" Count="1" Start="0"> |
[Example 2]
Suppose that the following personal contact information is saved in a company DB.
|
Registration Data <Item> |
Example 2-1: When sending a request with a character string that includes double-byte hyphens for the Keyword
|
Input Parameter .../v1/candidate?partition=999999&condition=Person.P_Id=12017&keywords=赤坂８ー５ー３４ |
■Response in the case of Version3.11.9
|
Output XML <Candidate Total="0" Count="0" Start="0"> |
■Response in the case of Version3.12
|
Output XML <Candidate Total="1" Count="1" Start="0"> |
Example 2-2: When sending a request with a character string that includes single-byte hyphens for the Keyword
|
Input Parameter .../v1/candidate?partition=999999&condition=Person.P_Id=12017&keywords=赤坂８-５-３４ |
■Response in the case of Version3.11.9
|
Output XML <Candidate Total="1" Count="1" Start="0"> |
■Response in the case of Version3.12
|
Output XML <Candidate Total="1" Count="1" Start="0"> |
Change concerning the operation in the phone number type Keywords search of the Read related APIs
When searching for a phone number by the Keywords search in version 3.11.9, the keyword format, which is a phone number, must be exactly the same as the format of the data saved in a company DB.
Version 3.12 allows a keyword, which is a phone number, to be searched for even if it does not exactly match the input data, but the keyword must consist of numbers only (no hyphen must be included).
[Example]
Suppose that the following personal contact information is saved in a company DB.
|
Registration Data <Item> |
Example 1-1: When sending a request with a phone number that includes hyphens for the Keyword
|
Input Parameter .../v1/candidate?partition=999999&condition=Person.P_Id=12017&keywords=090-5768-4331 |
■Response in the case of Version3.11.9
|
Output XML <Candidate Total="1" Count="1" Start="0"> |
■Response in the case of Version3.12
|
Output XML <Candidate Total="0" Count="0" Start="0"> |
Example 1-2: When sending a request with a phone number that includes no hyphen for the Keyword
|
Input Parameter .../v1/candidate?partition=999999&condition=Person.P_Id=12017&keywords=09057684331 |
■Response in the case of Version3.11.9
|
Output XML <Candidate Total="0" Count="0" Start="0"> |
■Response in the case of Version3.12
|
Output XML <Candidate Total="1" Count="1" Start="0"> |