In general, we ensure that appropriate users are notified of changes to various documents as follows: a)Put documents / drawingsof interest in certain folders. b) Set up subscriptions on events in those folders to various user Groups c) Manage which users are in which groups.
This of course reqiures a lot of adminstration, but so far has been managable, and is far, far better than having zillions of individual subscriptions.
For step (a) above, ensuring what folder various objects go into, we'd like to get a bit better at this by somehow using OIR's with branching. note: We use manual numbering for all documents / drawings, with prefixes that we can key on.
Question: With manual numbering, is there a way to use the constraints in OIR's to branchthespecified folder (essentially a case statement) based on some part of the Number?
thanks in advance
Insted of subscription rules,you can try with notification rules.You can create notification rule from policy administration at organization level so that by default it will be automatically applies to all products and library.
Using this Notification method from Policy Administration, is there any way to provide a more meaningful output, something more like a subscription email? Is there a way to control time of delivery? (ie. at a scheduled time vs. immediate)
I have the same request.
Our users needs to say when someone creates a new version view or modify some attribute.
This is possible by using subscriptions, but that way you have to create a subscription for every contest.
In which way you can do same thing with same level of granularity like using policy administration?
Windchill does allow you to subscribe to many items as once. For instance, you can select multiple folders (at the same level) then pick Subscribe from the Actions menu. The sad part is there is no way to edit the list of subscribed objects later. You can see the list of subscribed objects, but you cannot edit it. Sad. I was hoping to make a team subscription and just update it when ever new folders are created, but I would have to delete the subscription and recreate it every time.
This looks like 10 minutes of work for PTC R&D. Just need std edit functions added to this table.