Notification of version change in Project

I’m surprised Subscriptions didn’t have a way of doing that!

Another method you could try would be a Data Monitor. You could do something like a daily Data Monitor, where each day, it reports any versions that were created the previous day. Reporting items in a Project is a bit tricky because depending on how you’re using ProjectLink, you may have items shared to the Project, but also items directly created in the Project. This would be 2 different cases to report on. 

I think there is more to this than just a subscription, it would depend a lot on your implementation of how your suppliers access your info.is it 1 project per supplier vs 1 project for all suppliers, even down to folder access controls. 

Then once access is sorted then how communication is handled, are you using the OOTB routing? is there collaboration happening with approvals etc. This is great for “But we never knew that the latest doc was available!” 

When an object is revised in PDM it becomes a new object, this doesn't automatically get added to the project (there may be a preference for this but I doubt it) and you would typically need to remove the old share and create a new share with the new object. 

A catch all subscription may just end up being detected as spam. 

joe_morton, BryanK, Thanks for your comments. From your comments and doing some more experimenting, I have three options now:

1. Customization using a Data Monitor.
2. Make a subtype of a change object (problem report, change request, change notice) with its own workflow. The user would create the change object and add the files that have changed to the change object. The workflow would then send an email to the vendor to let them know files have changed. The vendor would then go to the change object to see what files have changed. The workflow would just send the email and then put the change object in completed state and that would be it.
3. Subscriptions work well for alerting users when new items have been added to a project, so instead of updating shared objects, we could just remove the share and reshare them as new.

Hi ​@mstarosto,

I would suggest implementing a listener that triggers whenever a new version is created within a project container. 
The listener can then send an email notification based on your requirements.