Complete the Profile tab to define the contact information, application access, and localization information for an operator. The access groups that you specify affect which rulesets, ruleset versions, and portals the user can access.
|Operator image||Optional. Associate a photograph, graphic, or other image with this operator.
If no image is specified, a default image from the binary file rule
images.dialogprofileimage.gif appears. |
For best results:
|Title||Optional. Enter a title, such as Mr. or Ms.|
|First name||Optional. Enter the first name for this user.|
|Last name||Optional. Enter the last name for this user.|
|Full name|| Enter the full name of this user. This text is present in the standard portal
displays including Dev Studio, Case Manager, and Case Worker
portals. Enter up to 50 characters. |
A few standard portal displays use the Short Description field — not the Operator Full Name value — to identify operators. To have the system present the full names on such displays, copy the Operator Full Name value to the Short Description field.
|Position/job title||Optional. Enter the job title or position of this user.|
|Phone||Optional. Enter the business phone number of the user. (If your system includes the optional PegaCALL component, a different property pyExtension holds the phone number; that property does not appear on the Operator ID form.)|
| Optional. Enter an email address for messages sent from this user or sent by
an application to this user. |
Application accessSpecify which applications this operator will access by populating a list of access groups.
|Access Groups|| For each row in the grid, select the name of an access group (a
Data-Admin-Operator-AccessGroup instance) for this user.
Designate a default access group by clicking the radio button next to the desired
access group name. Use the expand icon to see a list of roles associated with the
access group. |
|Application||Displays the name and version of the application this operator has access to. Click to open the rule.|
|Roles||Expand the Access Group item to display the access roles that are available to this operator. Click to open the access role rule.|
|Default locale|| Optional. You can associate an initial locale with this operator that affects
the processing and presentation of dates, times, and numbers. |
For example, enter
If the Internet Options locale setting for the user's workstation should apply for the application, leave this field blank.
If the field is not blank and the system contains locale-specific rulesets corresponding to rulesets that this user can access, the user can work with an entire localized application.
|Time zone|| Optional. Select a time zone to be used for presenting dates and times to this
user in: |
For example, select
As a best practice, if all or nearly all operators in an organization are in a single time zone and follow a common business day calendar, leave this field blank for those operators who share the organizational calendar and time zone. Complete the Calendar and Time Zone fields only for the operators who are exceptions.
These values are grouped by zone, not alphabetically, in the drop-down list, starting with the zone that is 12 hours away from Greenwich, England. Time zone codes follow the Olson TZ database, used in the ICU4J 3.4.4 library and most UNIX systems. Details on the Olson TZ database are available from http://en.wikipedia.org/wiki/Tz_database.
Do not type a three-letter code in this field, as such codes are ambiguous in certain cases and may produce incorrect presentation of daylight savings time in other cases. For details, see the Pega Community article Issue: Avoid three-letter time zone codes because they do not support Daylight Savings Time.
Settings in this field only affect the presentation of
As a best practice, if your organization has all its staff and servers in a single time zone, leave the Calendar and Time Zone fields blank. If most staff and all servers are in a common time zone, leave the Calendar field blank but complete a Time Zone value for the exceptional operators. If the organization has operators and servers across many time zones, create a Calendar for each time zone and specify both the Calendar and Time Zone fields in every operator ID instance.