1 *******************************************************************
2 ******* Explanation about menu.json *******
3 *******************************************************************
5 The menu.json defines the menu to show for each type of "roles":
8 -----------------------------
15 The JSON is separated to roles, and for each role we define "states",
16 what menu to show the user for each state of the component:
19 -----------------------------
20 NOT_CERTIFIED_CHECKOUT
22 READY_FOR_CERTIFICATION
23 CERTIFICATION_IN_PROGRESS
26 For each state we can define the user that will see this menu, the available parameters are:
29 -----------------------------
34 For designer, if the component state is checkout and the component was created by other user, the NOT_OWNER will be used.
38 "NOT_CERTIFIED_CHECKOUT":{
40 {"text":"Edit" ,"action":"goToEntity"},
41 {"text":"Check in","action":"changeLifecycleState", "url":"lifecycleState/CHECKIN", "confirmationModal": "lifecycleState/CHECKIN"},
42 {"text":"Submit for Testing","action":"changeLifecycleState", "url":"lifecycleState/certificationRequest", "emailModal": "lifecycleState/CERTIFICATIONREQUEST"},
43 {"text":"View" ,"action":"openViewerModal"}
46 {"text":"View" ,"action":"openViewerModal"}
51 Definition of the menu item:
52 -----------------------------
53 text - The text to show
54 action - Function that will be called when pressing on the menu item
55 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.
56 confirmationModal - Open confirmation modal (user should select "OK" or "Cancel"), and continue with the action.
57 emailModal - Open email modal (user should fill email details), and continue with the action.
58 blockedForTypes - This item will not be shown for specific components types.