Define Team View Subscriptions
- Last UpdatedApr 08, 2024
- 3 minute read
The Team-View Subscriptions window is used to create the subscriptions that define which teams (for example, targets) receive notifications when an attribute change in a (subscribed) Database View is approved in the Controlled Object Revisioning (COR) workflow.
From the Team-View Subscriptions window the following functionality is available:
Note:
If the Shared Service is not available or configured correctly, an error message displays
summarizing the problem. Check that Shared Services is installed and the AVEVA.SharedServices.Client.dll.config
is set-up correctly.
|
Project Teams |
Select a Project Team from the list, the current Team View Subscriptions display on the right hand side of the window. Input a value in the Project Teams field and press Enter to filter the list of Project Teams. The default is all. Project Teams that display in the list with an asterisk suffix contain pending changes (for example, A Database View that has been added or removed) that have not yet been committed to the Shared Services. The asterisk suffix also appears in the title of the window to indicate that pending changes are present. |
|
Subscribed Views |
A list of Subscribed Views displays for the currently selected Project Team. |
|
|
Click to move the currently selected item(s) from the Project Views list to the Subscribed Views list. |
|
|
Click to move the currently selected item(s) from the Subscribed Views list to the Project Views list. |
|
Project Views |
A list of Project Views displays for the currently selected Project Team. Select from the drop-down list to filter the list of Project Views. The default is all. If an item is removed from the Subscribed Views list and does not match the current filter in the Project Views list, it does not display in the Project Views list. |
|
Delete all Subscriptions |
Click to remove all items from the Subscribed Views list. |
Note:
Team View subscriptions are committed to the Shared Service at attribute level. The
procedure of breaking down the view into its individual attributes and committing
them to the Shared Services is an intensive process that can impact User Interface
performance. Committing a number of views to a number of teams as a single process
(for example, making a number of pending changes and then pressing OK or Apply) can
cause a delayed response to the User Interface and the Team-View Subscriptions window
may indicate that it is not responding. If this happens, do not try to close the window,
wait for the User Interface to respond. The suggested best practice is to commit a
small number of views to a single team (for example, add up to four database views
to one team) and then press apply to commit the change. The process can be repeated
to commit further subscriptions.