You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue can be considered as an Epic. So it should be break-down into separated issues prior to implementation. For now it will be a basic idea of what is meant to be improved, and why.
It was noted during one of the meeting with a customer that allowing for editing a user's permission on a company, or other actions related to user/company could be displayed as options in the dataView of users in the company manager's dataView. Please check an image of this example:
There would be required to properly set the options to be displayed per record in one dataView, which should have the options already defined per table for each dataView. The options should be defined per row or to display on the top of the table.
For options displaying in each row (which should be allowed to have more than one, and show as a clickable button - with tooltip) when the option is clicked it would take the user straight to either the Application home page, or the first page of this application (depending on the template existing configuration).
The row selected which is associated with an specific user should get this input into the application form. So, for example, one application that has a field for selecting the user and the company (to update the permissions for example) would have that user auto-selected when the application starts. In order to do that - I imagine we could be adding a mechanism to pass some input information to the application by giving an element code and value (text or object) that is valid to auto-fill some fields on load.
The text was updated successfully, but these errors were encountered:
This issue can be considered as an Epic. So it should be break-down into separated issues prior to implementation. For now it will be a basic idea of what is meant to be improved, and why.
It was noted during one of the meeting with a customer that allowing for editing a user's permission on a company, or other actions related to user/company could be displayed as options in the dataView of users in the company manager's dataView. Please check an image of this example:
There would be required to properly set the options to be displayed per record in one dataView, which should have the options already defined per table for each dataView. The options should be defined per row or to display on the top of the table.
For options displaying in each row (which should be allowed to have more than one, and show as a clickable button - with tooltip) when the option is clicked it would take the user straight to either the Application home page, or the first page of this application (depending on the template existing configuration).
The row selected which is associated with an specific user should get this input into the application form. So, for example, one application that has a field for selecting the user and the company (to update the permissions for example) would have that user auto-selected when the application starts. In order to do that - I imagine we could be adding a mechanism to pass some input information to the application by giving an element code and value (text or object) that is valid to auto-fill some fields on load.
The text was updated successfully, but these errors were encountered: