Bug 471442

Summary:	[Table] Categories should not be restricted to UML attributes
Product:	[Modeling] Papyrus	Reporter:	Johan Van Noten <johan>
Component:	Table	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	vincent.lorenzo
Version:	1.1.0	Keywords:	plan
Target Milestone:	---	Flags:	vincent.lorenzo: neon+
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:
Bug Blocks:	481012

Description Johan Van Noten

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).