Configuring end user display settings
To configure end-user information displayed in People search
- In the BMC Helix Digital Workplace Admin console, navigate to Configuration > User Display Settings.
In the User Data in People search section, select the appropriate check boxes:
Email address—Work email address
Work email address is not displayed in the Request by details in My Activity for order approvals that contain imported SRDs only (services imported from BMC Helix Digital Workplace Catalog). If an order approval contains at least one native SRD (service taken from BMC Helix ITSM), the work email address is displayed.
- Phone number—Work phone number
- Mail stop—Mail station
- User ID—Login ID
Email address, phone number, and mail stop are visible to end users by default.
3. Click Save.
To configure end-user information displayed in request and approval details
- In the Admin console, navigate to Configuration > User Display Settings.
- In the User Data in request/approval details section, select the appropriate check boxes:
Email address—Work email address
Work email addresses are visible to end users by default.
- User ID
3. Click Save.
To suppress the display of passwords in plain text in Request again screens and Service requests reports
By default, an answer submitted for the Password question is encrypted. When end users enter a value in this field, the entered value is substituted by asterisks. In addition, as an administrator, you can configure to hide or display password information on the Request again page and in Service requests report for all services in BMC Helix Digital Workplace.
- As an AR System administrator, log in to BMC Helix Innovation Studio and click Administration.
- Select Digital Workplace Catalog > Service Request.
- Select the Service Requests show password for questionnaire toggle key.
- Click Save.
Examples: User data displayed in People searches
The following table shows all the People searches where user information such as work email, phone, mail stop, and User ID can be displayed:
Functionality | Example |
|---|---|
Ability to request services on behalf of other users; see Submitting-service-requests-for-other-users. Mary's account is locked out, and she asks her colleague Martin to request a computer mouse on her behalf. Martin clicks Request as someone else and searches for Mary. He knows her work phone number, which he selects from the results. |
|
Ability to select and assign alternate approvers; see Delegating-to-alternate-approvers. Allen wants to delegate his approval rights to Mary Mann, so he searches for her and sees her work email, phone, and User ID in the alternate approvers list. User information of other colleagues with the same name is also retrieved. |
|
Ability to select and reassign approvers; see Reassigning-approvals-to-other-users. Bob receives an approval request but due to a limited timeline, he decides to reassign it to his colleague Mary by using the list of approvers. |
|
Ability to search users in the Global search panel. For more information about search, see Search-in-BMC-Helix-Digital-Workplace. Allen wants to find information about Mary Mann. He can see her work phone and User ID in the Global search panel. |
|
Ability to distinguish between users in the results of People searches. Bob, a manager at Apex Global, approves PTO requests. Apex Global has hundreds of employees across the globe, so there's a possibility of Bob approving a request for the wrong person. By using the user ID, Bob is certain to approve only the correct requests. Bob searches and finds two employees named Rosaline, but he confirms the user ID to easily distinguish between the two employees. |
|
Ability to hide user information in the results of People searches. Apex Global has changed email services, so the current work email addresses are no longer valid for employees. Sam, a manager at Apex Global, temporarily hides work email addresses. |
|
Ability to mention other users in posts. For more information about end-user options, see Setting-up-end-user-preferences. Allen, a manager at Apex Global, wants to congratulate Mary on her promotion. He types @ and searches for Mary by a User ID. |
|
Ability to find and follow people. For more information about end-user options, see Setting-up-end-user-preferences. Jane is a new employee at Apex Global. She wants to follow her colleague Mary. Jane can see Mary's work email and phone. |
|
Ability to create people groups. For more information about end-user options, see Setting-up-end-user-preferences. Jane is a new employee at Apex Global. She wants to create a people group to follow her colleagues and adds Mary first. Jane can see Mary's user information. |
|
This capability is available with the Ability to impersonate another user; see Enabling-requesting-services-on-behalf-of-other-users. Bob's account is locked, so he asks Allen to impersonate him and request a service. Allen can see additional information about Bob such as work email and phone. |
|
This capability is available with the Ability to add collaborators on service requests. For more details, see Collaborating-with-other-users-on-service-requests. Allen requests a new printer for the meeting room. He knows that Mary is also going to submit such a request and wants to add her as a collaborator. Mary is now aware of this request and will not create its duplicate. Allen would see only the people whom he can add based on their defined access restrictions in the list of collaborators. Allen can easily find his colleague Mary to add her as a collaborator. |
|
This capability is available with the Ability to add delegated collaborators on service requests; see Delegating-collaborators. Allen wants to order a new computer for his new project. He is taking a couple of days off in the upcoming week. He decides to add Bob, his manager, who can track and take the necessary actions to process the request in his absence. Allen easily finds Bob and adds him as a delegated collaborator. Bob can search for relevant teammates and add more collaborators for the request processing if needed. |
|
This capability is available with the Ability to add individual users to default collaborator groups; see Collaborating-with-other-users-on-service-requests. Allen shares requests with a default collaborator group. He wants to add a new employee Mary to this group. From the list of users, Allen can identify Mary by a work phone number. |
|
BMC Helix Digital Workplace Advanced 
Example: User data displayed in request and approval details
Irene is a support technician who receives dozens of approval requests every day. Martin has asked her to create a new account because his is blocked. When Irene receives Martin's service request, she sees his user ID in parentheses next to his name, so she approves the request.
The following screenshot illustrates where Irene sees the user ID in the approval request event card (she can also see the user ID in the request details and the results of the People search).
