Hi all,
My company is integrating APEX with Oracle EBS. There will be multiple developers with the same access privileges in the same workspace. I am looking to find a way to lock development at the application level (as opposed to page) so only specific developers can edit an application and its components at a time, and all other users only have read-only access. I've researched a few different ways to do this, and can't find a sufficient solution. What I've found:
- pages in an application can be individually locked for one developer. this is inefficient for large applications with many pages, parameter dependencies, and shared components that other developers can still touch
- at the application definition, the application status can be 'restricted' to specific users defined in an LOV. only these users will have their pre-existing workspace privileges on the application, all others cannot interact with the application in any way. this lets me limit what developers can touch it, but makes the application NOT be read-only for all other users
All documentation I've seen suggests the first method, and that when developers are locking pages for themselves but there are shared components or other dependencies, they should just be extra careful. This doesn't seem like a very practical solution for my company or cases when there are large applications or a large number of developers.
Any insight, or something I've overlooked? Thanks!