Sparx Systems Pro Cloud Server

Key Features and Benefits

• Via Sparx Pro Cloud Server, Hub synchronizes requirements in Sparx EA to other requirements management, Agile planning, test management, or other tool of choice, allowing information to flow freely. 

• Hub improves collaboration by allowing business analysts to use the tool most appropriate for the job, while enabling developers, testers, and other teams to receive work in their tool of choice
.
• Hub enables traceability between models and requirements in Sparx EA and other artifacts in SDLC tools.

Common Integration Patterns

• Providing Developers with Early Visibility into Requirements
• Providing Testers with Early Visibility into Requirements
• Associating Planning Items to Implementation Artifacts
• Aligning Testing Teams across Testing Tools
• Populating Requirements into PLM Tools

Demo Videos

Sparx Systems Enterprise Architect (Sparx EA)

The Sparx Pro Cloud Server connector allows users to access artifacts within Sparx Systems Enterprise Architect (Sparx EA). Users must have both Sparx EA and Sparx Pro Cloud Server in order to synchronize artifacts using Planview Hub. When configuring your Repository Connection in Hub, you will connect using your Sparx EA credentials.

Supported Editions

Planview Hub only provides support for ‘Premium Editions’ of Sparx Systems Pro Cloud Server that allow unlimited tokens. Token Editions are not supported.

Minimal User Permissions & Hub User

We recommend that you create a new user within your external tool, to be used only for your Hub integration. This is the user information you will enter when setting up your repository connection within Planview Hub. By creating a new user, you will ensure that the correct permissions are granted, and allow for traceability of the modifications that are made by the synchronization. 

In general, your user account should have sufficient permissions to create, read, and update artifacts in your repository. However, depending on the use case, your user may need different permissions. For example, if you are only interested in flowing data out of your repository, your user may not need to have full CRUD access, as the 'create' and 'update' permissions may not be needed.

Your user should have a secure password or token. Please be aware that Hub will not allow you to save a repository connection utilizing a weak password/token, such as 'tasktop.'

To use the Sparx Systems Pro Cloud Server connector, your Hub user should have the following permission set:

• Update Elements

Connecting to the Sparx Systems Pro Cloud Server Repository

Standard Authentication

Required Fields: 

• Location/Connection URL for Sparx EA, with project name appended
  • Example Format: https://server.com:805/ProjectName
• Username for Sparx EA
• Password for Sparx EA

Optional Fields:

• OSLC Access Code
  • Only required if the project is configured to require an OSLC Access Code.
• Tag Names
  • Names of tags to be made available as fields for integration. Names must be separated by spaces, and names with spaces in them must be surrounded by double quotes.
• Throttling Settings: This field indicates the number of API calls that can be made per minute. See details here.
  • Note: This field should only be set under the guidance of customer care as the ideal value is highly dependent on each customer's unique environment. 
• Connection Security: If checked, insecure connections to this repository will be allowed. See details here.

SSO Authentication

Additionally, Sparx Systems Pro Cloud supports the following SSO implementations:

• Script (HTTP cookies)
• X.509 Certificate

Learn more about how to set up your repository in Planview Hub here. 

Tags

If tags are to be included in integrations, use the Tag Names field in the repository to specify the names of tags to be used. Tag names that have spaces must be surrounded by double quotes, and tag names must be specified by spaces. For example:

Grape "Wine Advisor Rating"

Specifies two tag names.

Tag names are dynamically made into String fields on the artifact schema. If tag names are changed, a schema refresh is triggered, and collection mappings will need to be updated based on changes.

Note: Tags with a specified tagged value type are not supported.

Full Scan

Due to third party API limitations, updates to the following fields may not trigger change detection or cause a synchronization immediately.  To ensure these updates synchronize, a high fidelity full scan must occur or another qualifying change must be made to the artifact:

• Comments
• Relationships (Multi-Links)
• Tags

Learn more about how to configure change detection and full scan intervals in Planview Hub here. 

Special Features Supported

Supported Work Items

Learn about the difference between containers and work items in Planview Hub here.

Supported Containers

Learn more about containment in Planview Hub here.