Mandatory Project Content
By abhijit.kakhandiki on Oct 23, 2009
Oracle Open World was exciting last week, and Agile PLM 9.3 was very well received. The keynote and other sessions were heavily attended. The PLM demo booth saw pretty good traffic!
I was asked this question by a PPM customer at the PLM Demo Booth. "How do I make sure that a project deliverable does not get deleted by a user?" I explained to the customer that this can be done rather easily, and that has been an existing feature since 9.2.2. The customer's response was "That information right there was worth the cost of attending Openworld!" I thought I would write a quick blog post explaining how this can be done, to the broader audience.
Most of you know that in 9.2.2, we introduced the Content tab for all Activity and Gate type objects, that was designed to hold all supporting project content. This combined the previous Relationships, References and Attachment tabs into a one-stop shop for all project content. (Note: You still have disable the existing Attachment tab. To all PPM customers out there, please use the Content and NOT the Attachment tab for storing project content).
On the content tab, there is a "Mandatory" attribute for each row. This attribute can have "Yes" or "No" values which can be set at the Template level. When a project is created from a template, the mandatory attribute values will get copied to the resulting project. Example if you have a "Business Case" deliverable that must be addressed for every project, you can set it to mandatory in the template. Every project created from this template would then have the "Business Case" deliverable set to mandatory. The effect of doing this, is that normal project team members will not be able to delete this deliverable. If this is a deliverable in the true sense i.e. if it affects a project task via a business rule, then it needs to be executed upon (maybe set to 'Released' status etc.) for that task to be completed. In other words, you are making it compulsory for the deliverable to be executed for every instance of a particular product development process.
You can provide special privileges to Project Administrator type users that will enable them to modify the values of the 'mandatory' attribute i.e. change mandatory deliverables to regular deliverables. Such users will need to have the 'Modify Mandatory Content' privilege mask, which is essentially the Modify privilege with 'Mandatory Content' criteria. Regular project team members will not have this privilege and hence will not be able to delete mandatory deliverables.
Hope this helps. It was great meeting some of you at Openworld! Cheers!