Readme for Micro Focus Connect VersionOne Connector 24.2

This readme describes how to configure Micro Focus VersionOne Connector. Refer to the Micro Focus Community and Micro Focus Connect Help Center for further configuration instructions.

The Micro Focus VersionOne Connector for Micro Focus Connect (Micro Focus VersionOne Connector) lets you synchronize VersionOne assets like Stories and Tasks with assets in OpenText Products, for example assets found in the 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.

  Installation and Upgrade Information Technical Notes
Prerequisites Known Issues Need assistance with the product?


Supported Versions

This version of the connector is certified with VersionOne (hosted)

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.

Supported Assets

This version of the connector supports VersionOne asset types, as well as custom fields and types.




This connector requires at least build 24.2 of Micro Focus Connect and can be configured using the Micro Focus Connect UI.

The file should be copied to the Micro Focus Connect's AppData\data folder.

The following are required to run the Connector. For further configuration instructions, see the Micro Focus Connect Release Notes.

  1. Create a Connector directory. For example: C:\Program Files\Micro Focus\Connect\AppData\connectors\mfcConnectorV1
    • NOTE: If this is being installed into an existing connector directory, you must remove the existing mfc*.jars
  2. Copy the following libraries (and the provided Connector jar) into the connector directory you created.



Installation and Upgrade Information

The following information contains notes regarding installation, but does not replace the entire process.

Required Connection Information

In order to use this connector, you will need to collect and enter this information in the Micro Focus Connect user interface:



Known Issues

Micro Focus Connect Deletes All Restored Items

If delete items is set to true (it is false by default) for the Version One data source, Micro Focus Connect deletes all of the items restored from the recycle bin in Version One.

Converted VersionOne Asset Deleted on master side of Micro Focus connection.

Converting a VersionOne asset to a different type will cause the corresponding synchronized asset on master side of Micro Focus connection to be deleted. If the assets of the new type are being synchronized, a new item of the corresponding type will be created.

One sprint may not encompass another in VersonOne

Writing sprints to VersionOne will fail if the dates of the sprint are encompassed by an existing sprint in V1. The error will include "Error writing to output stream at com.connect.v1.V1SyncItem.update"

Problem with Non-Ascii Content

A work around for this problem is to perform the following steps:

  1. Go to C:\Program Files\Micro Focus\Connect\WebServer\bin
  2. Copy tomcat8w.exe as ConnectWebServerw.exe
  3. Launch ConnectWebServerw.exe (alternatively, start tomcat8w //ES/ConnectWebServer)
  4. Go to the "Java" tab
  5. In the "Java Options" append to the end argument list the following, every statement should be on a new line: -Dfile.encoding=UTF8

Fallback users are not supported

When selecting a fallback user a message will state there are no users.



Technical Notes

Reference Items in Same Projects in Relationships

Only items from the same project can be referenced in a Relationship. For example a Backlog Item can only reference an Epic that is in the same project.

VersionOne Connector Does Not Support Synchronizing Schedule Assets

VersionOne will throw an error if you attempt to add a sprint to a project which doesn't have a sprint schedule. The Version One connector does not suppport synchronizing Schedule assets.

Mapping Tests but using Regression Tests

If your connection is mapping VersionOne Test type, but you are using VersionOne RegressionTests, the RegressionTests will not sync until they are part of a Test Set.

Sprints only sync once a schedule is created

Until you create a schedule in VersionOne, Sprints will not sync.

Support for Access Tokens

In order to use an Access Token for authentication, set the User property for the datasource to "AccessToken" and set the password to the access token value from VersionOne UI.

Temporary Performance Issues

Reading items from VersionOne is now taking twice as long as previous versions. Micro Focus Connect development is looking into this issue.

Temporary Lack of Support for Non-Ascii characters

Non-Ascii characters may show up as ? in fields, or may result in exceptions from VersionOne when an update is perfored. Micro Focus Connect development is looking into this issue.



Need assistance with the product?

Get support enables you to open a support incident or to submit a bug. You can also browse many helpful support resources.