Compare commits

..

No commits in common. "35d71e91fe29ee4a63a9f6c1a4bb69ec903e0015" and "e9f98ffe3224bb06d7714efe7ce66ebad7773b23" have entirely different histories.

3 changed files with 0 additions and 56 deletions

View File

@ -1,16 +0,0 @@
# Sample Dynamic Menu
This repository is for configuration of the sample dynamic menu web app.
There are two parts to the dynamic menu:
* The menu items with actions, stored in a menu tree.
* Entitlements (a.k.a. authorisations) to those menu items by fictitous persons and organisations.
## Menu items
If you have edit access you can change the menu items. See [menu](menu/) README
## Entitlements
If you have edit access you can change the entitlements to menu items. See [entitlements](entitlements/) README

View File

@ -1,16 +0,0 @@
# Entitlements
The entitlements are stored in files which
are processed by the server based controller, which returns
the list of entitled menus to the web browser which then
displays them according to its style.
## Self Serve
If you edit the [sample/allow_selfserve_etal.txt](sample/allow_selfserve_etal.txt) file, you
can see the changes in the web side after update / refresh immeditaley.
The changes you can do are:
* add a new function id
* remove a function id

View File

@ -1,24 +0,0 @@
# Menu items
The menu definitions are stored in files which
are processed by the server based controller, which returns
the list of entitled menus to the web browser which then
displays them according to its style.
## Self Serve
If you edit the [menu_selfserve.json](menu_selfserve.json) file, you
can see the changes in the web side after update / refresh immeditaley.
If you do change the file start slowly such as changing:
* label
* intent (try a different web location)
It is easy to corrupt the JSON file with wrong format, so
caution is advised.
If you feel confident, you can add a new item, and when
doing so please select a function id that already exists
because otherwise the menu item is unlikely to appear due to
the entitlement check.