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

Display soft-types in hierarchical listing when creating a new Document or EPM Document.

Display soft-types in hierarchical listing when creating a new Document or EPM Document.

Soft-types are defined with hirearchical relationships in the Type and Attribute manager. That hierarchy should be used in the Type dropdown when creating a new Document or EPM Document. That would prevent the user from having to search through a potentially very long flat list of sub-types and instead navigate through an intelegent browsable hierachy of sub-types. If a particular type is not instantiable, then it should be expandable, but not selectable.

8 Comments
Moonstone

This would be great.

Note: We use many sub types of change request, and have multiple nodes that are not instantiable as placeholders.   In general, OIR's and ACL's are applied against these but users cannot create them.  Make sure that the hierarchical display somehow allows for this.  Maybe gray out types that are in the tree but not instantiable so that is still makes sense.  Please contact me for examples if needed.

Amethyst

we've done some customization around this with Global services ...

There's 2 different pickers in 10.   one in list form, one in tree form ...

replacing  one by the other is not a big deal ... but of course it will be great if it could be OOTB with a preference for the choice of the type of picker ...

regards

Gregory

Newbie

Can you provide details on how to replace one with the other?

Newbie

This functionality is currently available through a customization point.  Search in the Help Center for "Configuring a Type Picker".  Under the customization points section, see the parameter "displayHierarchy".  

I see the value of providing this capability out of the box.  I have created a backlog item to provide this in a future release.

Newbie

Good Idea, I've used in past, but 10.0 it doesn't seem to work.  However, a better customization would be allowing the administrator to decide the hierarchy design.  A lot of times the Hierarchy in type manager is designed to match objects with similar attributes (and/or Lfiecycles).  That doesn't neccessarily mean that that is the best hierarchy to use.

Amethyst

Yes ... difference between the WTpart data model ... and the navigation/classification structure ...

like in PartsLink...

Good idea !

sm
Newbie

This is a great idea. For companies with many sub-types, the flat list is not so efficient unless you know the name of the sub-type you want to use. Presenting the hierarchy would be much more intuitive for users to choose sub-types from.

Community Manager
Status changed to: Archived