This readme describes how to configure Micro Focus PPM Connector. Refer to the Micro Focus Community and Micro Focus Connect Help Center for further configuration instructions.
The Micro Focus PPM Connector for Micro Focus Connect (Micro Focus PPM Connector) lets you synchronize PPM requests with assets in other Micro Focus Connectors, for example, assets found in the Jira or Micro Focus Octane Connector.
Copyright 2018 - 2024 Open Text.
The only warranties for products and services of Open Text and its affiliates and licensors ("Open Text") are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
Except as specifically indicated otherwise, this document contains confidential information and a valid license is required for possession, use or copying. If this work is provided to the U.S. Government, consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
| Contents | ||
|---|---|---|
| Features | Installation and Upgrade Information | Technical Notes |
| Prerequisites | Known Issues | Need assistance with the product? |
This version of the connector is certified with Micro Focus PPM 9.64+. It may work with earlier versions as old as 9.52, but this hasn't been certified.
Unless otherwise specified, for any given MF Connect connector from OpenText, all versions of the connector product that are officially released and supported by it's vendor both four months before the time of the release of the connector as well as at the time of using the connector, are supported by OpenText. Not all product versions will be tested and validated by OpenText for each connector release. Instead, OpenText chooses a subset of versions that we deem representative or most important to run validation and certification tests against. These selected versions are mentioned in the respective connector read-me, clearly identifying them as "validated" or "certified". As stated above, this does not mean that Micro Focus Connect does not support other product versions – it only means that no validation test cycle was executed for the other versions.
This version of the connector supports synchronization of all enabled PPM Request Types, including PFM Proposal and Asset, but excluding PFM Project and Program request types.
This connector requires at least build 24.2 of Micro Focus Connect and can be configured using the Micro Focus Connect UI.
The thesaurus.properties file should be copied to the Micro Focus Connect's AppData\data folder.
The following steps are required to run the Connector. For further configuration instructions, see the Micro Focus Connect Release Notes.
The following information contains notes regarding installation, but does not replace the entire process.
In order to use this connector, you will need to collect and enter this information in the Micro Focus Connect user interface:
Whether or not a PPM field is required or read-only depends on request workflow statuses. The Micro Focus PPM Connector cannot identify which PPM fields are required or read-only. As a result, if a PPM field is required or read-only at a point, it is always handled as a non-required and editable field, and it can be mapped as the target field with other Connector’s fields.
If the number of PPM requests exceed 10,000, synchronization will fail. You can increase this limit in PPM 9.60+ by increasing the value of the Server Parameter MAX_REQUESTS_RETURNED_IN_REST_API_CALL (in server.conf or directly in the Administration console. No need to restart PPM).
During synchronization, PPM Connector retrieves and synchronizes all the PPM requests in one shot. It does not support pagination yet, so you must ensure that you have enough memory to load all requests information.
Make sure the PPM server and Micro Focus Connect server are in the same time zone and have their clocks synchronized. Otherwise, some requests may not be synchronized due to time difference.
If a request field contains non-English characters, after the sync, the field value may not be displayed as expected.
When selecting a fallback user a message will state there are no users.
For each supported request type, only Text, Text Area, drop-down-list, auto-complete-list and auto-complete-list SQL User field types are supported in field mappings, regardless of whether the fields are hidden or read-only. And It is also supported to use type rules to add synchronization criteria for filtering PPM request.
1.1 If both the PPM field and the target field are drop-down-list fields and the values in these two fields are the same,
1.2 If both the PPM field and the target field are drop-down-list fields and the values in these two fields are different, you need to set the value mappings for each field value. By default, value mapping will populate automatically in the "Value Maps" page. If not, set it manually. Otherwise, the values will not be synchronized to the target system correctly.
1.3 If the PPM field is a drop-down-list field and the target system field is a textbox/textarea field, the values in the target systyem should be set as the values of the drop-down-list values in PPM System. Otherwise the data synchronization from target system to PPM system would fail.
2.1 If the PPM field is a single-select or multi-select auto-complete-list field, the target system field is a single list or multi-list field, and the values in these two fields are the same,
2.2 If the PPM field is a single-select or multi-select auto-complete-list field, the target system field is a single list or multi-list field and the values in these two fields are different, you need to set the value mappings for each field value. By default,value mapping will populate automatically in the "Value Maps" page. If not, set it manually. Otherwise, the values will not be synchronized to the target system correctly.
2.3 If the PPM field is a single-select auto-complete-list field and the target system field is a textbox/textarea field, the values in the target system should be set as one of the auto-complete-list values in PPM System. Otherwise, the data synchronization from the target system to PPM would fail.
3.1 If the PPM field is a single-user/multi-user field and the target system field is a single user field, the user should be a valid user in both PPM and the target system. Otherwise, the data synchronization between PPM and the target system would fail.
3.2 If the PPM field is a single-user field and the target system field is a textbox/textarea field, the values in the target system should be set as one of the full names in the PPM user field. Otherwise, the data synchronization from the target system to PPM would fail.
Note:
Get support enables you to open a support incident or to submit a bug. You can also browse many helpful support resources.