Readme for Micro Focus Connect AccuWork Connector 24.2

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

The Micro Focus AccuWork for Micro Focus Connect (Micro Focus AccuWork Connector) lets you synchronize AccuWork assets with assets in other Micro Focus Connectors, for example assets found in the Micro Focus Azure DevOps Connector.

AccuRev Connector for Micro Focus Connect (AccuRev Connector) lets you synchronize AccuWork assets like stories, tasks, and change requests with those in other Micro Focus Hub repositories and clients like StarTeam Agile.


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 AccuWork 7.6.1

Unless otherwise specified, for any given Micro Focus 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 any AccuWork asset type.




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.

This connector is an update to the installed connector, you should remove (or move to a directory outside of the connectors) and replace the existing AppData\connectors\mfcConnectorAccuwork\mfcConnectorAccuwork*.jar file and replace it with the one provided.

AccuWork Schema Requirements

You must define or have an equivalent of the following fields in your AccuWork schema.

Field Name Field Type
project Choose
type Choose

If you wish to synchronize Iterations and Releases, then you will need fields that represent these as well as the entries above.

Note: For Choose and List types, you must also create the values for the fields. For example, for the "project" field, specify the project names in the AccuWork schema.

AccuRev Client Requirements

The AccuRev client must be installed on the same machine on which Micro Focus Connect is installed. In addition it should be included in the global path, or provided in the configuration settings so that Micro Focus Connect can find the client.



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:

Finally, you might have to specify one or more of the following fields depending on how you want to synchronize AccuWork assets.



Known Issues

Enhancement Gets Mapped to Story

If the AccuWork types include the type enhancement, this will get mapped to Story instead of UserStory, resulting in an error if you automap your connection because the link field will be present.

Iterations Must Follow Specific Format

Iterations are synchronized only if their names follow the <release>.<iteration> format. The <iteration> can be specified however you like (ITR1, iteration_1, or v23_1, for example), but it must be unique within both the AccuWork and the Hub.

Removing Parent/Child in AccuWork Does Not Remove Relationship in connected Product

Removing parent/child story relationships (epic/story or story/task, for example) in AccuWork will not remove the relationship in the other product in your connection. Changes to parent/child relationships in the other product however, are reflected in AccuWork.

Attachments synchronization is not supported

Fallback users are not supported

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



Technical Notes

Managing Deleted Assets

AccuRev's TimeSafe architecture prevents AccuWork issues from being deleted though no such restriction may exist in the connected Product. However, you can use the On Delete State field to set the AccuWork issue's State field to Cancelled when the corresponding asset is deleted from the other product.

Type Field Must Be Specified in AccuWork Schema

You must have a Type field specified in your AccuWork schema. You can call the values whatever you like (issue, defect, RFE, for example), but they should correspond to the types you wish to map in the other product.
Also, based on the selected Type field values, you need to configure the Data Source Relationships to correspond to the actual relationships model. By default, we have the configured model for the following types:

Synching Change Package Version and Transaction History to Jira

If you want to synchronize change package data to jira and you are using the accusync plugin for jira to display "Change Package" and "Change Package History" tabs with tables of change package data, there are two new internal fields you can configure to sync from AccuRev to Jira. On the Jira side, you must first create two fields to hold the data. Both of the fields must be multi-line text fields. Create an AccuWorkChangePackage field to sync the internal_cpkInfoJira field from AccuRev to Jira. Create an AccuWorkChangePackageHistory field to sync the internal_cpkHistoryJira field from AccuRev to Jira. In order for MFConnect to find the two Jira fields, they must be added to the appropriate Jira screens for the type of issues (story, defect, etc) being synchronized. If you do not want to see the fields in Jira, create a new tab on the page with a single space as the name and put the fields on that hidden tab. Both internal_cpkHistoryJira and internal_cpkInfoJira are truncated at 32k. Corresponding fields internal_cpkHistory and internal_cpkInfo are not truncated at 32k and should not be used with Jira or other systems that limit the response to 32k.



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.