You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Andi Huber (Jira)" <ji...@apache.org> on 2022/04/29 09:00:00 UTC

[jira] [Updated] (ISIS-1023) [Wish] Invoke actions on entity in table collection (rows)

     [ https://issues.apache.org/jira/browse/ISIS-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andi Huber updated ISIS-1023:
-----------------------------
    Summary: [Wish] Invoke actions on entity in table collection (rows)  (was: [Wish] invoke actions on entity in table collection)

> [Wish] Invoke actions on entity in table collection (rows)
> ----------------------------------------------------------
>
>                 Key: ISIS-1023
>                 URL: https://issues.apache.org/jira/browse/ISIS-1023
>             Project: Isis
>          Issue Type: Wish
>          Components: Isis Viewer Wicket
>    Affects Versions: viewer-wicket-1.7.0, core-1.7.0
>            Reporter: Daniel Keir Haywood
>            Priority: Major
>
> 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
(v8.20.7#820007)