Roles Documentation

Each one of us plays a different role in day to day life for example a cop performs his duties in a day with special permissions, and as a responsible parent in an another role once he heads back, amplelogic low code platform is inspired by real life giving each user a role in your business process and set of permissions associated with that role differing with applications. The entire application will be a Roles based application. Whatever permission will be provided to a Role, the users mapped in that role will be able to get access of those permitted features only.

Great, let us start creating your first role, very simple and easy.

Creation of Role :-

By clicking on Role sub tab present in App Admin tab the user will be redirected to the Role Creation Page.


Role Permissions :-
  • By clicking on Add button one popup will appear for adding the Role details.
  • Define the Role properties such as Name and Description.
    This Role creation page will have three tabs namely
    Accessible Pages
    Form Template Permissions
    Admin Page Permissions

Accessible Pages :-

If we check the pages for any roles, that means those pages of the application will appear for the mapped users in run time. For one role multiple pages can be checked, all those pages will be visible to the user in run time.

Form Templet Permissions :-
Add :-

If Add option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the add option in that Form page & by clicking on that the user will be redirected to the first state of the workflow (designed workflow against the form).

Design Time


Run Time


Edit :-

If Edit option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the Edit Icon against the records of that form & by clicking on that icon the user(s) will be able to go inside the record.

Design Time


Run Time


Upper Hierarchy Records :-

If Upper Hierarchy Records option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get Upper Hierarchy Records option in the record search page of that form.

Significance

The records which has been created by the same and above department users, that will get displayed in the search result. The department hierarchy will be picked from the Organization Hierarchy as defined in admin level.

Example :If X user is mapped in Front End-DEV-M department and if user X searches for Upper Hierarchy Records then all the records raised from Back End-DEV-M, QA-M, QC-M, DEV-M, Melange departments will get displayed. Rest of the department records will not get displayed.


Design Time


Run Time


Acted By Records :-

If Acted by Records option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get Acted by Records option in the record search page of that form. If the user searched for Acted by Records, then the record(s) on which they have performed any action will get displayed.

Design Time


Run Time


View All Records :-

If Acted by Records option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get Acted by Records option in the record search page of that form. If the user searched for Acted by Records, then the record(s) on which they have performed any action will get displayed.

Design Time


Run Time


Note : In one Role if we give View All Records permission then “View Department Records” or “View Department Hierarchy Records” permission can’t be given to the same role.

View Department Records :-

If View Department Records option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get View Department Records option in the record search page of that form. If the user search for View Department Records, then the record(s) which has been initiated from the user’s department that will be get displayed. If the user is mapped in multiple departments then all the mapped department records will appear.

Design Time


Run Time


Note : In one Role if we give View Department Records permission then “View Department Hierarchy Records” permission can’t be given to the same role.

View Department Hierarchy Records :-

If View Department Hierarchy Records option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get View Department Hierarchy Records option in the record search page of that form. If the user search for View Department Hierarchy Records, then the record(s) which has been initiated from the user’s department and the below mapped departments that will get displayed.

Design Time


Run Time


Note : In one Role if we give View Department Hierarchy Records permission then “View Department Records” or “View All Records” permission can’t be given to the same role.

View Organizational Hierarchy Records :-

If View Organizational Hierarchy Records option is enabled in Form template permission for a role, it will ask the designer to select a department, in run time if the user searches for View Organizational Hierarchy Records then the records, initiated from that selected department that will be displayed.

Design Time


Run Time


View Subordinate Records :-

If View Subordinate Records option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get View Subordinate Records option in the record search page of that form. If the user searched for View Subordinate Records, then the record(s) on which they have been initiated by their subordinates those will get displayed. It will pick the subordinates as per the mapping done in Supervisor field of Employee screen (admin level).

Design Time


Run Time


Note : In design time if we select the View Subordinate Records for one role then for that role we can’t select View All Records, View Department Records, View Department Hierarchy Records or View Organization Hierarchy Records.

View Division Records :-

If View Division Records option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get View Division Records option in the record search page of that form. If the user searched for View Division Records, then the record(s) which has been initiated from the Division, he/she belongs to will get displayed.

Example : If user X belongs to the QA-M department and tries to search for View Division records then all the records which has been initiated by the departments under Melange Division will get displayed. Refer the below Organizational Hierarchy

Note : Melange should be marked as Division in Organizational Hierarchy level. If the user is mapped under two divisions then then the records of all those two division will get displayed


Design Time


Run Time


View Audit Trail :-

If View Audit Trail option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the View History icon against the record of that form, by clicking on which the liner flow diagram of a record will get displayed.

Design Time


Run Time


View Report :-

If View Report option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the View Report icon against the record(s) of that form, by clicking on which the form report of that particular record will be displayed.

Note : The form report will be displayed only if a Form Report is built for that form & that report should be mapped with the form in form Edit option.

Design Time


Run Time


Print Report :-

If Print Report option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the Print Report icon at the top right corner in the form report. By clicking on the Print option the user will be able to take the print of the report directly from the connected printer(s).

Design Time


Run Time


Export :-

If Export option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the Export to PDF & Export to Excel icons at the bottom left corner of the search page. By clicking of those the user will be able to export the search results in desired PDF or Excel format.

Note : To get those icons in run time the user needs to enable flash in browser settings.

Design Time


Run Time


Import :-

This functionality is used to create bulk records in one form. If Import option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the Import button under Additional tab. By clicking on the Import button, the user will be redirected to the Import page of that form. In that screen Transition (Dropdown) field and Generate Excel, Back buttons will get displayed. After clicking on Import icon, the user will be redirected to the first state of the flow. Whatever activities are present in the first state that will be displayed in the Transition dropdown. After selecting the Transition if the user clicks on Generate Excel then the excel will appear with the field names (as column names) along with Submit & Clear buttons.

Design Time


Run Time



Shhow Revision :-

This functionality is user to show the user the Revision of any attachment where the Revision Format is mentioned.

Design Time


Enable Change Request :-

If Enable Change Request option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the Enable Change Request icon at the top right corner inside a record that too in a particular state wherein Change Request Permission has been given. For further reference on how to give the change request permission in state level please go through the Change Request option in Workflow design level.

Design Time


Activate/In Activate Records :-

If Activate/In Activate Records option is enabled in design time that means that role users will get one option to inactivate or activate any record, that too in a particular state, where the Activation/Inactivation of records permission has been configured in workflow design time.

Design Time


Download PDF :-

If Download PDF option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the Download PDF icon at the top right corner in the form report. By clicking on that icon, the user will be able to save the form report in PDF format.

Design Time


Run Time


Unlock Record :-

This functionality is used to unlock any record which is being accessed by some other person. If Unlock Record option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the Unlock Record option under the Additional Tab. By clicking on that all the locked records will get displayed and against that the Unlock icon will appear. By clicking on the Unlock Icon the record will get unlocked.

Design Time


Run Time



Clone Records :-

This functionality is used to clone any existing record. If Clone Record option is enabled in Form template permission for a role, then the user(s) whoever is mapped in that role, will be able to get the Clone Record icon against the record of that form, by clicking on which one popup will appear asking whether we want to clone the record or not.

Design Time


Run Time


Delegate Records :-

This functionality is used to Delegate one record from assigned user to some other user. The assigned user (assigned for any action on a record) will get an option to delegate the role to any other user present in the same role. The delegate option will appear for the role users for whom the Delegate Record option is enabled. By clicking on the Delegate Record option, the users present in the mapped roles will appear for selection. The user can select any other user and delegate the record to he selected user. One user can’t delegate the record to themselves.

Design Time


Run Time



Offline Storage :-

Through this functionality the user will be able to save the entered details in the record locally and can retrieve it. If we enable this Offline Storage option in any role then the role users will be able to get the offline storage icon for that form at the top right corner of the record. Once after storing that value offline if the user comes out from the record then after if they get inside that record the user will get one more icon namely “Retrieve Offline”, clicking on which the stored data will get retrieved to the respective fields.

Note : This data is stored in browser cache, so if the cache is cleared then the user wouldn’t be able to retrieve the stored data.

Design Time


Run Time



Record Audit :-

Through this functionality the user will be able to see the entire audit (history) of any record. If we enable record audit option to any of the role then the role users will get one Record Audit sub tab under Additional main tab. After selecting any record if the user clicks on record audit then the entire history of that record will get displayed. The designer can decide for which role and for which form the audit option should be given.

Note : This data will be stored in browser cache, so if the cache is cleared then the user wouldn’t be able to retrieve the stored data.

Design Time


Run Time


After enabling the options if the user clicks on Submit button, System shall give a confirmation message displaying “Role details saved successfully”

Admin Page Permissions :-

In this permissions page the Designer can give the permissions of Admin Pages of Applications. Therein there will be several sections Master Data, Forms, Workflows, Pages, Roles, Form Reports, Reports, Modeling, Parser, Templates, Auth. Matrix, Employee Hierarchy, Export Audit. For all these options the permissions can be given to a role, depending upon these given permissions the role user will get the access of those sections.


Manage Users & Groups in Role :-

If the user clicks on the newly created role and then click on the Manage Users and Groups button. System shall navigate the user to the Roles page where user can map Users or groups to that role.


Edit Role :-

Similarly, User can edit any existing role by clicking on the Edit button.

User can track the audit details of the Role using the Audit trail functionality.

System shall display the audit details as shown below.