Skip to main content
Planview Customer Success Center

Planview AdaptiveWork






Planview AdaptiveWork (formerly Clarizen) is a PPM tool that enables project managers and delivery teams to collaborate, share ideas, and execute on what is important. Connect disconnected teams to maximize project outcomes, and engage your workforce across the organization. 



Connector Setup Details

This section describes the basic steps needed to prepare your AdaptiveWork instance for use with Viz. 

Minimal User Permissions & Viz User

We recommend that you create a new user within your external tool, to be used only for Viz. This is the user information you will enter when setting up your tool connection within Planview Viz. By creating a new user, you will ensure that the correct permissions are granted.

In general, your user account should have sufficient permissions to read artifacts in your tool. 

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

Connecting to the AdaptiveWork Repository

Standard Authentication

Required Fields:



API Key Authentication (Recommended)

Required Fields:




Supported Artifacts

Supported Work Items

Supported Work Item Type

Applicable Repository Versions

Unique URL?


Any supported repository version:



Any supported repository version:


Supported Containers

Containers that can be modeled as Flow Items

Applicable Repository Versions

Unique URL?


Any supported repository version:


Containers used to define which artifacts are included in an Artifact Set



N/A (entire tool serves as a container)

Any supported repository version:




Supported Field Types

Planview Viz supports configuring rule-based modeling (i.e., conditional modeling) using the field types shown below.

Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not function properly.

Field Type

How is field type referenced in the repository?

Sample Repository Fields Supported

Particular Repository Fields NOT Supported

1checkicon.png String





1checkicon.png Single-select

Pick List




1checkicon.png Multi-select

Multi-Select Pick List

Custom Multi-Select


1checkicon.png Boolean