Micro Focus Connect does not dictate these type mappings. For example, Micro Focus ALM Octane Defects synchronize with Azure DevOps Bugs. A type in one data source synchronizes to an equivalent type in the other. Type maps are the most convenient, typically the most logical, and satisfy equivalency. This can be done using synchronization criteria.
Micro focus octane how to#
The other challenge when working with large data sets on any given product, is to determine how to select the appropriate subsets to synchronize. The more complex mappings present a challenge in determining how to guide the appropriate artifact subsets into their corresponding projects, which can be done using calculated values. For example, one project can spread from one data source to one or more projects on another data source, in either or both directions. A connection can span multiple projects on either side. This also includes relationships between objects and their parents.
When synchronizing object hierarchies across products, a connection can spread across multiple types. Element typeĭata source (end point instance of a product) The data source comprises types, types comprise fields and relationships across types comprise links. Each data source represents an end point instance of a product. Micro Focus PPM (project and portfolio management)Ī Micro Focus Connect connection represents a synchronization between two data sources. As of December 2020, Micro Focus Connect supports the following set of connectors (products). Each product is represented by a connector, a spoke. The hub is the core product-agnostic service. Micro Focus Connect supports a hub and spoke model. The only other noteworthy aspect of the Master data source is that, for any given item, if a field value being synchronized deadlocks, that is, a change was made to both source and target at the same moment, then the Master value is chosen to break the deadlock. Micro Focus Connect can run unidirectional or bi-directional synchronizations that can be set/controlled at the connection level, the individual artifact type level, and the field level. The choice of Master or Target does not represent the direction of synchronization. Only Micro Focus products may be selected as Master. Synchronizations may be executed between Micro Focus ALM/QC, Micro Focus Octane, JIRA, Azure DevOps, Rally, Version One, etc.
Synchronizations are executed between a Master, which is a Micro Focus product, and a Target, which is any product in the market, including those Micro Focus provides.
Micro focus octane update#
It can create, update and delete artifacts in a product based on equivalent changes made in another product. Micro Focus Connect is a cross product artifact synchronization engine.
0 kommentar(er)
