@Hussain_Fakhruddin wrote:
Database based roles should have limit on what “columns” should be returned. This would make life really easy in terms of not having to write post / pre script validations on which roles could access what data.
Database roles need to have more conditional script as more advance filters than just column level. Many a times a related filter needs to match. Its very inconvenient to write post scripts for each roles and make more queries. I feel if a validation script could be included as part of role it would be really great. This way, not just DB permission, but a custom access could be given at the ROLE level based on business requirement.
A more precise Google / FB auth using Native SDK tokens ( not kind of shadow user ).
User management is at single level only. It cannot be matched with Org/Department level or APP level. A lot of code needs to be written if we were to have multiple orgs under same instance. Most large API platforms have this. ( Usergrid, Apigee etc ).
HTTPS certificate management via the admin panel itself is very important for out of the box solution.
API documentation UI needs a lot of improvement. It just doesn’t fit in most of the laptop screens. Good we have large screens but definitely can be improved.
Cache ON/OFF switch on Admin panel.
Service Package groups - Would be great to have groups of packages. This way all the services could be grouped together.
Advance code editor. Current one is really not helpful if we want to do the changes right there. Although its improved from previous editor, I think there is more room for improvement.
Global files like Global lookup keys. Would be nice to have some small static files which could be referred as config files for the business logic.
Template Roles. Currently there is no way to restrict who can access which template ID. For example, any user having access to email can use any template to make a call. I might be wrong, but I never found any template based assignment for roles.
Thoughts ?
Posts: 2
Participants: 2