| Provider's name | Integration with | Functionality provided | Notes |
|---|
| CLM cloud services pluggable provider | BMC Cloud Lifecycle Management | Access to BMC Cloud Lifecycle Management data and operations. | To configure, enter the following information: - clm.rest.uri—The URL to the BMC Cloud Lifecycle Management server.
- super_user.key—The superuser password to access BMC Cloud Lifecycle Management.
- clm.catalog.search.disabled—Select this check box if you want to disable searches in the BMC Cloud Lifecycle Management catalog.
|
| Exchange pluggable provider | Microsoft Exchange server | Allows assets and rooms to be reserved. Displays the availability status on the profile page of the end user console. | To configure using basic authentication, enter the following information: - Login—Use any Exchange user who has access to viewing other user and room schedules and who can schedule rooms.
- Password
- URL—Use the URL to access the Microsoft Exchange web service, which uses the format of https://mail/ .domain.extension/EWS/Exchange.asmx.
Or, to configure using OAuth2 authentication, select the Enable OAuth2 check box and enter the following information: - URL—Use the URL to access the Microsoft Exchange web service, which uses the format of https://mail/ .domain.extension/EWS/Exchange.asmx.
- Client ID—Use the Exchange client ID.
- Client Secret—Use the Exchange client secret that corresponds to the client ID.
- Exchange Tenant ID—Use the Exchange tenant ID.
- Specify additional information as required.
|
| HRCM knowledge pluggable provider | BMC Remedy HR Case Management | Uploads HR knowledge articles to BMC Digital Workplace from the BMC Remedy HR Case Management application. | To configure, enter the following information:
- AR hostname—Specify an AR hostname here.
- AR port—Specify an AR server port here.
- AR password.
- Collect performance statistics—Select this check box if you want to gather performance data.
|
| HRCM service catalog pluggable provider | BMC Remedy HR Case Management | Creates cases using the HR solutions from BMC Remedy HR Case Management. | For eForms to work in BMC Digital Workplace, you must specify the BMC HR Case Management midtier URL in the Midtier URL field, update the settings, and reload the providers. To configure, enter the following information:
- AR hostname—Specify an AR hostname here.
- AR port—Specify an AR server port here.
- Midtier URL—Specify a Mid-tier base URL here.
- AR password.
- useExternalIcon—This flag works only for SRDs that do not have icons specified in BMC Helix Digital Workplace. If the flag is set to true, the icons for SRDs are taken from BMC Service Request Management. If the flag is set to false, the default icons are used.
- Collect performance statistics—Select this check box if you want to gather performance data.
|
| HRCM user details pluggable provider | BMC Remedy HR Case Management | Synchronizes user information from BMC Remedy HR Case Management to MyIT. | Important: Enable this provider only if the BMC Helix Digital Workplace server is not integrated with BMC Remedy ITSM. To configure, enter the following information:
- AR hostname—Specify an AR hostname here.
- Check password expiration—Select this check box if you want to verify the validity of your password.
- AR port—Specify an AR server port here.
- AR password.
- Collect performance statistics—Select this check box if you want to gather performance data.
|
| LDAP pluggable provider | Lightweight Directory Access Protocol (LDAP) | This provider enables sending broadcasts to LDAP user groups. Important: - Be sure to disable the Group pluggable provider if you want to use LDAP. Use of both these providers at the same time might corrupt the rendering of the user groups.
- User login in LDAP must be the same as in Remedy AR System. Users with different logins might not receive broadcasts.
| The following settings are required: - ldap.url — LDAP URL in the format ldap://LDAP_URL
- ldap.auth.user — LDAP admin login name.
- ldap.auth.pswd — LDAP admin password.
- ldap.auth.type — Whether user name and password are required for connection to an LDAP server:
- If yes, type SIMPLE.
- If no, type NONE. - ldap.context.factory — Predefined setting. You must not change the value.
- ldap.domain.name — Reserved for future needs. No need to configure it.
Along with the required settings, other settings might apply to specific scenarios. Although most of the additional settings are predefined, you might need to configure them. Additional settings to manage broadcasts: - ldap.group.base — A base distinguished name (DN) that is the starting point in the directory from which searches initiated by LDAP occur. For example, if you specify a base DN as DC=example, DC=com, the LDAP search for groups examines only the DC=example subtree in the DC=com directory tree.
- ldap.group.attr.id — LDAP attribute that is mapped to a group name.
- ldap.group.attr.name — Reserved for future needs. No need to configure.
- ldap.group.filter — LDAP filter used to search for groups according to search criteria.
- ldap.group.attr.dn — LDAP attribute that is mapped to a group ID.
- ldap.subgroup.filter — LDAP filter used to search for subgroups (nested groups) according to search criteria.
- ldap.subgroup.filter.cn — Reserved for future needs. No need to configure it.
- ldap.user.base — A base distinguished name (DN) that is the starting point in the directory from which searches initiated by LDAP occur. For example, if you specify a base DN as DC=example, DC=com, the LDAP search for users examines only the DC=example subtree in the DC=com directory tree.
- ldap.user.attr.id — LDAP attribute that is mapped to a user name.
- ldap.user.attr.name — Reserved for future needs. No need to configure it.
- ldap.user.filter — LDAP filter used to search for users according to search criteria.
- ldap.user.name.filter — Reserved for future needs. No need to configure it.
- ldap.user.attr.dn — LDAP attribute that is mapped to a user ID.
- ldap.user.attr.email — Stores a user email address in LDAP.
Additional settings to manage the LDAP query load: - ldap.querysize.maximum — Defines a number of results that an LDAP server retrieves upon your query. If no value is specified, the number of results is not limited.
- ldap.querytime.maximum — Defines a timeframe during which an LDAP server is queried. Always configure this setting because an empty value triggers an infinite query.
|
| Group pluggable provider | Remedy Action Request System (Remedy AR System) | This provider enables sending broadcasts to Remedy AR System user groups. Important: Be sure to disable the LDAP pluggable provider if you want to use the Group pluggable provider. Use of both these providers at the same time might corrupt the rendering of the user groups. | You do not need to configure any parameters because the Remedy AR System integration is out-of-the-box and user group settings are automatically synchronized. |
| RKM pluggable provider | BMC Knowledge Management | Searches for knowledge articles in the BMC Knowledge Management database. | To retrieve knowledge articles, you must also enable the ITSM Knowledge pluggable provider. To configure, enter the following information: - Port—Enter the port value.
- Application password.
- Hostname.
- RKM templates—To use a custom template along with the predefined templates, add the template (for example, RKM:CustomTemplate template) to the RKM templates setting.
- rkm.searchResultOption—This setting affects the Similar articles section displayed to the right of the knowledge article. For similar articles, the search term is the original article title. The following options are available:
- words—The preview excerpt shows the words surrounding the search term (words in the original article title).
This option is equivalent to the Words Around Hits option in BMC Knowledge Management. - excerpt—The preview excerpt is from the start of the article.
This option is equivalent to the Excerpt option in BMC Knowledge Management. - none—The preview excerpt excludes snippets that match with the article.
For more information about the search result options, see https://communities.bmc.com/docs/DOC-32647 in BMC Communities. - use.must.have.search.term—This flag is set to false by default.
When the flag is set to false, the search returns knowledge articles that include at least one of matched search keywords. When the flag is set to true, the search returns knowledge articles that have all search keywords in their metadata. - rkm.search.force.leading.trailing.wildcards—This property is set to false by default. If the flag is set to true, BMC Digital Workplace adds additional wildcards to search queries, which generates more search results. When enabled, this parameter interferes with the full text search language-specific tokenization, stemming, and relevance logic. Use this parameter for the English locale only.
- rkm.use.locale—This property is set to false by default. If the flag is set to true, locale-based search of the knowledge articles is enabled.
If you enable rkm.use.locale, a user with the locale supported by RKM sees only knowledge articles in this locale and those without a locale. To see the list of default locales that RKM supports, see
Supported languages and locales
. Apart from the locales that are available in RKM by default, you can also add custom locales. To add custom locales, in the RKM console, open the RKM:LanguageLocalization form and use the following language codes: Click here to view the list of custom locales... | BMC Digital Workplace | Locale ID |
|---|
| Arabic | ar ('ar-eg' mapped here) | | Catalan | ca | | Chinese Traditional | zh-tw ('zh-hk', 'zh-mo' mapped here) | | Danish | da | | Dutch | nl | | Finnish | fi | | Greek | el | | Norwegian | no ('nb', 'nn' - mapped here) | | Polish | pl | | Romanian | ro | | Swedish | sv | | Thai | th | | Turkish | tr | | Welsh | cy |
To add custom locales in the RKM console, see
How to add languages in the Knowledge Management console
. |
| System management pluggable provider | None | Maintenance of the BMC Digital Workplace server. | Not applicable. |
| SRM pluggable provider | BMC Service Request Management | Creates incidents by using the service request definitions (SRDs) from BMC Service Request Management. | Most of the provider settings are predefined. You can update the following settings as needed: - Midtier URL—This field refers to BMC Remedy Mid Tier for BMC Service Request Management.
- skip.fulfillment—If some of your service requests do not use fulfillment, leave this value as true. If the value is set to false, BMC Digital Workplace requires fulfillment to be set by all service requests from BMC Service Request Management.
- useExternalIcon—This flag works only for SRDs that do not have icons specified in BMC Digital Workplace. If the flag is set to true, the icons for SRDs are taken from BMC Service Request Management. If the flag is set to false, the default icons are used.
- Open AIF in new window—If this flag is set to true, service requests of the type AIF open in a new window or tab. If the flag is set to false, these requests open in an iFrame.
- show.additional.crq.details—This flag is set to false by default. If the flag is set to true, the Notes and Summary fields are added to the change request approval details.
The change request approval title duplicates the Summary field.
Search settings: - use.and.search.logic—This flag is set to false by default.
When the flag is set to false, the search returns services that include at least one of the matched search keywords. When the flag is set to true, the search returns services that have all search keywords in their metadata. - search.by.answer.enabled—When this flag is set to true, end users can search for their service requests by submitted answers.
- max.search.weight—Allows SRD results to be on top of all the results returned by search. This parameter is set to 100 by default.
- use.fts.weight—Defines the sequence of SRD results appearance. This flag is set to false by default. When the flag is set to false, the search returns SRDs that are requested more frequently compared to other SRDs. When the flag is set to true, the search returns SRDs, the titles of which better correspond with the search query.
- search.only.active.approvals—If this flag is set to true, only active approvals are searched. If this flag is set to false, both active and inactive approvals are searched.
- search.approvals.created.since.months—Specify the integer value to indicate the number of months. For example, if the value 3 is set and today is 4/19/2020, the active and inactive approvals created on/after 1/19/2020 are searched.
- (Version 20.08.01 and later) srd.search.force.leading.trailing.wildcards—This property is set to false by default. If the flag is set to true, BMC Digital Workplace adds additional wildcards to search queries, which generates more search results. When enabled, this parameter interferes with the full text search language-specific tokenization, stemming, and relevance logic. Use this parameter for the English locale only.
Settings for service requests with the On Behalf Of feature: - obo.enabled.for.all—If this flag is set to false, the rules set in BMC Service Request Management for On Behalf Of requests are used. In addition, BMC Digital Workplace users can search for the Requested for user by first or last name, but not full name.
If the flag is set to true, any employee can create a request on behalf of any other employee. Because a different search is performed for the Requested for user, end users can search by full name in addition to first name, last name, or email address. If your organization has over 50,000 employees, setting this flag to true can improve BMC Digital Workplace performance. - obo.search.transformSearchTermCase—Defines if search is case sensitive in the Request as Someone else dialog box. Enter one of the following values:
- Upper lower—The search is case sensitive.
- None—The search is case insensitive.
- obo.search.prefixWildcard—Defines whether end users can search by a partial phrase match in the Request as Someone else dialog box.
If the setting is enabled, the search returns all keywords that contain the search term. For example, a search with "ary" as a search term returns all results with "ary" at any position of a search keyword (Mary, Laryl, Aryin).
If the setting is disabled, only results with the searched symbols at the beginning of the search term are returned (Aryin).
|
| User Details Pluggable provider | BMC Remedy IT Service Management | Synchronizes user information from the BMC Remedy IT Service Management to BMC Digital Workplace. | Important: If you have installed BMC Digital Workplace with only BMC HR Case Management, enable the HRCM user details pluggable provider. For all other installation scenarios, enable User Details pluggable provider. You can configure the User Details Pluggable provider in User Details Pluggable Provider Settings: - Select the Check password expiration check box if you want to verify the validity of your password.
|
Comments
Log in or register to comment.