Question
Tata Consultancy Services
IN
Last activity: 28 Jul 2021 12:50 EDT
custom header in DX API
Hi,
how can we pass custom header in DX API?
Ex - I am using OOTB createcase API and want to pass the operator id in header. How to do that?
I am using Pega 8.5.2.
Pegasystems Inc.
US
@avisekmondalI'm assuming your referring to HTTP custom header. If yes, then add the header value in the action request handler or extend the action handler to take a parameter or object of header name/value pairs and add to header before call. If using the angular start kit modify the getCase(id) starter kit method to pass parameter with header or modify functions in /src/app/_services folder.
Tata Consultancy Services
IN
@MARTT Thank you.
yes. That's exaclty what I needed. To check how we can pass it from Angular starter kit.
This is bascially we need for the locale identification for localization.
Is there any specific header that we can pass with the language, so that DX API can identify the language and send the content accordingly in template API call?
Thanks again!
Pegasystems Inc.
US
@avisekmondal Browser language is automatically sent and used by Infinity localization engine on each DX API call. For instance on a create case call
Request URL: http://localhost:1080/prweb/api/v1/cases
Accept: application/json, text/plain, */* Accept-Encoding: gzip, deflate, br Accept-Language: es Authorization: Basic cmVwLmNhYmxlY286cGVnYQ== Connection: keep-alive Content-Length: 84 Content-Type: application/json DNT: 1 Host: localhost:1080 Origin: http://localhost:4200 Referer: http://localhost:4200/ sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91" sec-ch-ua-mobile: ?0 Sec-Fetch-Dest: empty Sec-Fetch-Mode: cors Sec-Fetch-Site: same-site Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
Infinity uses the locale to resolve the field value rule from the localization RuleSet first - MyApplicationRuleset_es - before the primary RuleSet: MyApplicationRuleset. The following example show the first name field localized in the CableCO starter kit cableCo rep initial case screen
@avisekmondal Browser language is automatically sent and used by Infinity localization engine on each DX API call. For instance on a create case call
Request URL: http://localhost:1080/prweb/api/v1/cases
Accept: application/json, text/plain, */* Accept-Encoding: gzip, deflate, br Accept-Language: es Authorization: Basic cmVwLmNhYmxlY286cGVnYQ== Connection: keep-alive Content-Length: 84 Content-Type: application/json DNT: 1 Host: localhost:1080 Origin: http://localhost:4200 Referer: http://localhost:4200/ sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91" sec-ch-ua-mobile: ?0 Sec-Fetch-Dest: empty Sec-Fetch-Mode: cors Sec-Fetch-Site: same-site Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
Infinity uses the locale to resolve the field value rule from the localization RuleSet first - MyApplicationRuleset_es - before the primary RuleSet: MyApplicationRuleset. The following example show the first name field localized in the CableCO starter kit cableCo rep initial case screen
The field value definition is
used in the label field for first name
Therefore, no need to insert the locale with code.
Tim
Updated: 28 Jul 2021 12:50 EDT
Tata Consultancy Services
IN
@MARTT Is it applicable for DX API V1? I am using Pega 8.5.2.
I have added Accept-Language = fr in header but still see the English text being returned at front end, not the French.
But when I am updating the operator locale to fr_CA, I can see the French text being displayed.