What decides Time zone for my application?
Hello,
Our application is hosted on the Pega cloud ,supposed to be in CST for local users and in Phillipines timezone for PHI users. All applications are defaulted to GMT per Pega Cloud team. I noticed that the operator timezone setting decides how the date and time are displayed to that particular end user. I have a couple of questions in that regard:
Hello,
Our application is hosted on the Pega cloud ,supposed to be in CST for local users and in Phillipines timezone for PHI users. All applications are defaulted to GMT per Pega Cloud team. I noticed that the operator timezone setting decides how the date and time are displayed to that particular end user. I have a couple of questions in that regard:
- Which timezone will be used for the SLA's and report generations etc - server or operator level? Example: If a user from Phillipines set an SLA for a task and that will be picked up to work by somebody from the US timezone, which timezone will the SLA adhere to? and how will it work?
- If I needed to update operator timezones, is there an easy way to do per access group?
- Is there any other setting we can do at an application level that decides what timezone should be followed by all users irrespective of their location?
- Can managers change timezone for people reporting to them>If so, how can this permission be given to them?
I am relatively new to Pega development and would appreciate any help I get to understand the way the application time zone works. I have already read lots of article including https://community.pega.com/sites/default/files/help_v81/procomhelpmain.htm#data-/data-admin-/data-admin-operator-/data-admin-operator-id/general.htm but did not get a straight forward answer to my questions above.
Thanks,
Divya
***Edited by Moderator Marissa to update SR Details***
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
- For SLA's it will start calculating from the current date-time, so if the goal is 12hrs, it will be 12hrs only irrespective of the timezone of the operator.
- Use an activity to get the list of operators based on Access Group and loop through results and set the timezone for each operator and commit the changes.
- For changing the timezone of the application other than GMT, Please find the article below.https://community.pega.com/knowledgebase/articles/changing-time-zone-pega-and-alert-log-entries-pega-722-and-earlier
- For changing the timezone of the operator from the manager portal, you can use show the list of reporting users and when the manager selects the user, show them the selected user's operator profile and make changes and submits it. (I think this option is not available in OOTB)
AFNI Inc
US
@kanap2 Thank you for your input. I did have a couple of questions about your last 2 points.
- https://community.pega.com/knowledgebase/articles/changing-time-zone-pega-and-alert-log-entries-pega-722-and-earlier is for Pega 7.2.2 and earlier. Is there any article available for Pega 8.1 and later?
- For changing the timezone of the operator from the manager portal, you can use show the list of reporting users and when the manager selects the user, show them the selected user's operator profile and make changes and submits it. (I think this option is not available in OOTB) -- It is not available OOTB. Can you please give me a basic overview on the best place to start looking for options to make this change. Any reference article or anything that will help.
Thank you once again for you input.
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
- I shared the wrong link, I don't think we can configure the timezone inside the application. We need to configure it in the JVM. Please find the below article which might be helpful.https://collaborate.pega.com/question/how-pega-gets-timezone-server
- I didn't find any references. Please find the high-level design steps below:
- Show the list of operators who reports to the manager.
- On click of the operator, run local action which gets the operator details with required fields editable.
- On Submit of the Flow action, commit the changes to the DB.