Clarity PPM

Expand all | Collapse all

hide the attributes in create layout of status report object based on the Project Organization Breakdown Structure(OBS).

  • 1.  hide the attributes in create layout of status report object based on the Project Organization Breakdown Structure(OBS).

    Posted 11-17-2017 08:49 AM

    Hi,

     

    Is there any solution to hide the attributes in create layout of status report object based on the Project Organization Breakdown Structure(OBS).

     

    Status Report is Project Sub-Object.

     

    Thanks,

    Satya



  • 2.  Re: hide the attributes in create layout of status report object based on the Project Organization Breakdown Structure(OBS).

    Posted 11-17-2017 09:53 AM

    Not on a CREATE layout I think.

    We can control fields on EDIT layouts if they are on subpages (can control whether the subpage is displayed to the user or not).



  • 3.  Re: hide the attributes in create layout of status report object based on the Project Organization Breakdown Structure(OBS).

    Posted 11-17-2017 09:57 AM

    Thanks David.

     

    But client requirement is to hide in create layout.



  • 4.  Re: hide the attributes in create layout of status report object based on the Project Organization Breakdown Structure(OBS).

    Posted 11-17-2017 10:36 AM

    The only way I know of using different Create pages is with Partitioning, where each partition could use variations of the create page, but I do not think you can use OBS for this.



  • 5.  Re: hide the attributes in create layout of status report object based on the Project Organization Breakdown Structure(OBS).

    Posted 11-18-2017 01:00 PM

    You can restrict through lookup mapping or section hiding though  (the latter I will document when I get a chance)

    See Tech Tip: Lookup mapping - Ability to provide multi dependent lookups without saving OBS linked 

     

    Keep in mind that in blueprints as of 15.3 we can show different attributes based on the blueprint. So maybe see if you can solve the problem using the new UX