Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

role: besides menu tree, allow configuring the sub-tree to be used #391

Closed
teosarca opened this issue May 17, 2017 · 1 comment
Closed

Comments

@teosarca
Copy link
Member

Is this a bug or feature request?

feature request

What is the current behavior?

Only the menu tree can be configured

Which are the steps to reproduce?

Edit role

What is the expected or desired behavior?

In Role, have another field for the menu folder which shall be considered as root of our webui menu.

image

@teosarca teosarca added this to the 2017-21 milestone May 17, 2017
metas-ts added a commit to metasfresh/metasfresh that referenced this issue May 18, 2017
[#391](metasfresh/metasfresh-webui-api-legacy#391) role: besides menu tree, allow configuring the sub-tree to be used
[#706](metasfresh/metasfresh-webui-frontend-legacy#706) Manufacturing order - Issue HUs - wrong /quickActions call

me-45
@metas-lc metas-lc self-assigned this May 23, 2017
@metas-lc
Copy link

IT

  • swing and webui: go to Role window and see new field: Root menu node OK
    old field is Menu Tree
  • to to a role and change both. For root menu node set CRM, and the other one some old Menu
  • login with that role on webui => the menu is only with CRM OK
  • login with swing => it's the old menu OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants