cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Extend the WTPart Views to more flexibility

Extend the WTPart Views to more flexibility

Extend the WTPart Views for other scenarios. At the moment the scenario E-BOM to M-BOM is very well supported. But other scenarios like creating a view for the Product-Management to attach some data-sheets, certifications, etc. are not very well supported. Since these documents are being created later in the process, a product manager should be able to create a new view to attach these documents and release the view independently. 

  • Create Views from each state. The user doesn't need to have revise permission and also the LC template doesn't need have set the revise transition
  • Extend the OIR to setup the LC Template etc. for each view
  • Preference (for each view) if the BOM should be copied or not
  • Preference (for each view) if the documents should be copied or not
  • Define attributes for each view

 Having configurable links doesn't work well, since no collection e.g. revise, save as, etc. are possible and also setting attributes only for a role aren't implementable.

Finally, the solution should be like an independent WTPart subtype, but have the same master attributes and number.