Microsoft SharePoint is a popular tool for sharing information and enhancing collaboration. Often, organizations use SharePoint’s custom development capabilities to create highly-tailored line-of-business applications to streamline collaboration across teams.
This section describes the basic steps needed to prepare your SharePoint instance for use with Viz.
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.'
See Microsoft SharePoint User Guide to learn how to create a new user in Microsoft SharePoint.
Standard Authentication
Required Fields:
SharePoint Azure Active Directory OAuth2 via Certificate
Note: Access to SharePoint via Azure AD authentication is only supported via certificate support. Shared secret is not supported.
See the section below for steps on configuring this authentication method.
Required Fields:
URL
App Registration
The first step in using the Azure AD authenticator is to set up an app registration for Planview Viz — to generate authentication tokens and control access. See the section below for setting up app registration.
After setting up the app registration, you must grant 'Sites.FullControl.All' and 'SharePoint' permissions.
Note: Due to a restriction that is dictated by Azure Active Directory, the app registration must be granted access to ALL SharePoint sites within a Tenant and cannot be restricted. Please note that this may conflict with your organization's security policies.
To learn more, refer to Microsoft documentation here.
This authentication method only works with SharePoint online and Azure Active directory.
See the steps below to set up the Azure Active Directory authentication method:
Generate a new JWT token
Supported Work Item Type |
Applicable Repository Versions |
Unique URL? |
---|---|---|
All list content types. For example:
Note: Documentation Types and Items in a library list are not currently supported. |
Any supported repository version: |
Yes |
Containers that can be modeled as Flow Items |
Applicable Repository Versions |
Unique URL? |
---|---|---|
N/A |
|
|
Containers used to define which artifacts are included in an Artifact Set |
|
|
Lists |
Any supported repository version: |
N/A |
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.
Standard Field Type |
How is field type referenced in the repository? |
Sample Repository Fields Supported |
Particular Repository Fields NOT Supported |
---|---|---|---|
String |
Single line of text Multiple lines of text |
Title Address Subject |
|
Single Select |
Choice (one choice) |
Content type Task Status |
|
Multi Select |
Choice (multiple choices) |
|
|
Boolean |
Yes/No Checkbox |
Auto Update |
|