Skip to Main Content
Feature Request FR-3642
Product Area Application Builder
Status CLOSED

3 Voters

Read only dashboard developer

michael.weinberger 2 Public · Feb 21 2024

Idea Summary
There should be a new type of Workspace user: dashboard developer
This would be in addition to an Administrator, developer or user

Use Case
A citizen developer wants to build read only dashboard application. For this he would need developer rights to create an application and access to the sql workshop to see the data model and maybe use a query builder to create views or code a simple function. He should be able to create rest data sources.

He must not be able to update/delete data or drop any table/procedure/etc…

Preferred Solution (Optional)
A dashboard developer should be restricted in the Sql Workshop (read only for all but views and functions) and in the App Builder (no page processing, dynamic actions of plsql type or interactive grid regions)

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is unlikely to make its way into APEX.

Comments

Comments

  • jayson hanes Admin OP 1.5 years ago

    I'm not sure how feasible this actually would be.. but interesting..

  • michael.weinberger 2 OP 1.5 years ago

    Since Apex platform is build with Apex it might be possible to block dangerous parts (pages, processes, etc..) of the platform simply by setting an Authorization Scheme.

  • andrea.hanes APEX Team OP 1.5 years ago

    Seems like the safest path would be a content management app with access to only the allowed tables, views, columns and such.  With some trickery, you could handle this all at runtime.  Or, set up a separate app altogether with only access to a separate schema in the same workspace against the same app data as the source system and limit down as much builder access as possible.  This might be a support nightmare TBH.

  • michael.weinberger 2 OP 1.5 years ago

    Since I do not want to limit the access to any tables but prevent the developer from dropping a table, the saftest path would be a seperate database schema with select / execute only on the tableowner tables and packages. 
    But I do wonder now about the handling in the application builder - how do I select tables in a schema that is not included in the workspace (although they are accessible from the schema included in the workspace).

    Is it possible in Apex to build a report based on a synonym (without typing the sql)?