The Subscription user interface is very inconsistent depending on your entry point, the type of container or the type of object. All these factors make Subscriptions difficult to create and manage because the capabilities and features are not consistent for every type of subscription.
Provide Common, Standard Interface and Capabilities for all Subscriptions
Allow Subscription author to always select additional team members/user as recipients
User search and selection must support look-ahead typing
Allow Subscription author to define additional recipients as mandatory or optional (recipient approves acceptance of the subscription)
Allow Subscription author to select Roles as recipients, not just individual users
Subscription recipient should have a way to accept of reject "assigned" subscriptions
Action Items only support single click Subscribe/Unsubscribe actions (no additional criteria can be specified, making this the simplest and weakest subscription type)
Allow selection of multiple objects as input to Subscribe action
Support Subscribe action in RMB and Toolbar for multiple objects
Support Subscribe action from Windchill Search results table.
Support search definition as basis of object(s) definition for Subscription
Allow modification of existing Subscriptions to include updated items
In many cases, Subscriptions cannot be edited or updated with new information or reference items.
Users are forced to remove the subscription and create a new one.