1 *******************************************************************
2 ******* Explanation about menu.json *******
3 *******************************************************************
5 The menu.json defines the menu to show for each type of "roles":
8 -----------------------------
17 The JSON is separated to roles, and for each role we define "states",
18 what menu to show the user for each state of the component:
21 -----------------------------
22 NOT_CERTIFIED_CHECKOUT
24 READY_FOR_CERTIFICATION
25 CERTIFICATION_IN_PROGRESS
28 For each state we can define the user that will see this menu, the available parameters are:
31 -----------------------------
36 For designer, if the component state is checkout and the component was created by other user, the NOT_OWNER will be used.
40 "NOT_CERTIFIED_CHECKOUT":{
42 {"text":"Edit" ,"action":"goToEntity"},
43 {"text":"Check in","action":"changeLifecycleState", "url":"lifecycleState/CHECKIN", "confirmationModal": "lifecycleState/CHECKIN"},
44 {"text":"Submit for Testing","action":"changeLifecycleState", "url":"lifecycleState/certificationRequest", "emailModal": "lifecycleState/CERTIFICATIONREQUEST"},
45 {"text":"View" ,"action":"openViewerModal"}
48 {"text":"View" ,"action":"openViewerModal"}
53 Definition of the menu item:
54 -----------------------------
55 text - The text to show
56 action - Function that will be called when pressing on the menu item
57 url - Data added to menu item, in case the function need to use it, example: for function "changeLifecycleState", I need to pass also the url "lifecycleState/CHECKOUT" that I want the state to change to.
58 confirmationModal - Open confirmation modal (user should select "OK" or "Cancel"), and continue with the action.
59 emailModal - Open email modal (user should fill email details), and continue with the action.
60 blockedForTypes - This item will not be shown for specific components types.