You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2016/07/13 04:41:20 UTC
[jira] [Updated] (ISIS-1023) Allow actions to be invoked on entity
when rendered within a table.
[ https://issues.apache.org/jira/browse/ISIS-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-1023:
------------------------------
Fix Version/s: (was: 1.15.0)
1.14.0
> Allow actions to be invoked on entity when rendered within a table.
> -------------------------------------------------------------------
>
> Key: ISIS-1023
> URL: https://issues.apache.org/jira/browse/ISIS-1023
> Project: Isis
> Issue Type: New Feature
> Components: Core, Core: Viewer: Wicket
> Affects Versions: viewer-wicket-1.7.0, core-1.7.0
> Reporter: Dan Haywood
> Priority: Minor
> Fix For: 1.14.0
>
>
> Enhance the Wicket viewer (with corresponding metadata annotations) to render an entity's actions as drop-down menu when that entity is rendered as a row of a table.
> There's probably no need to introduce additional annotations; the @ActionLayout(hidden=...) indicates whether an action is hidden in various contexts, one of these being it being hidden (or not) within tables.
> My idea therefore is that, unless every action of an entity is indicated as hidden for a table, that there is an additional column that includes a drop-down and that allows the actions to be invoked (bringing up the dialog).
> Once the action is invoked (like bulk actions) the table should be reloaded (rather than, say, navigate to the object returned by the action).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)