Bug 471442 - [Table] Categories should not be restricted to UML attributes
Summary: [Table] Categories should not be restricted to UML attributes
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Table (show other bugs)
Version: 1.1.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks: 481012
  Show dependency tree
 
Reported: 2015-06-30 09:34 EDT by Johan Van Noten CLA
Modified: 2017-09-08 09:54 EDT (History)
1 user (show)

See Also:
vincent.lorenzo: neon+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Johan Van Noten CLA 2015-06-30 09:34:46 EDT 
Currently, only UML attributes can be used (e.g. for a Class, one can select the ownedOperations).

In theory, a category could be any collection of UML elements:
* collected through an OCL expression (e.g. ownedElements->oclIsKindOf(MyType))
* an attribute defined in an applied stereotype

I guess this is true for determining the visible values.

Example:
Suppose I want to see only the classes contained in a specific package.
I can create a table in that package, but have no way to select only the classes. (in depth 0 I can select them manually, but that is not the intension).