Validating Subscriptions

Validating Subscriptions

When you create a subscription, the system ensures that it conforms to the prerequisites listed in Subscription Prerequisites. After a subscription is created, however, the configuration of the viewpoints and the users may change, which could result in an invalid subscription. When you navigate to the subscription panel, all existing subscriptions for a viewpoint are validated to verify that they meet the rules of a subscription. If a subscription is invalid, you can take action to resolve the issue.

Resolving Validation Errors

The examples below illustrate common subscription validation errors and the actions to resolve them.

If the source and target viewpoints do not have a node type in common or if a node type converter is not set up between the source and the target viewpoints, the system displays the following error:

To resolve this, create a node type converter to convert the source node type to the target node type, see Working with Node Type Converters.

If the subscription assignee does not have at least Participant(Read) permission to the source viewpoint and Participant(Write) permission to the target viewpoint, the system displays the following error:

To resolve this, ensure that the subscription assignee has at least Participant(Read) permission to the source viewpoint and Participant(Write) permission to the applications in the target viewpoint, see Assigning Application Permissions and Assigning View Permissions.

If the source or target viewpoint is no longer active, the system displays the following error:

To resolve inactive viewpoint errors, change the status of the archived viewpoint back to Active. See Understanding the Lifecycle of Data Objects and the Data Chain.