This content has been marked as final. Show 268 replies
User roles in an application to make managing the components available to users easier and more flexible.
The steps would be:
1. Create authorization schemes of type role
2. Associate the schemes with components just like we do now
3. Create a role within the application
4. Assign role type authorization schemes to roles
5. A role could be assigned to a user session using an API during authentication or at any point during the session
The user would then have access to the components through the role. A substitution string would be available for the current role to use in the page template, report queries etc. A new role could be created or updated without any change to the authorization schemes.
I have been able to reproduce bug 13040672, but unfortunately not found a solution for it or identified the cause of it. It looks like a memory corruption in PL/SQL which I haven't been able to reproduce in a simplified test case for the PL/SQL dev team.
Still looking into it, but I don't think it's an APEX issue, more of a DB problem.
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
I am coming from oracle forms too.
I would like to see
- Dynamic LOV support in tabular form. Right now, I have to code it manually. APEX 4 can do it in a normal screen, but not tabular form.
bump up the 100 items per page limitation
- Multiple tabular forms on a single page
- Multiple Interactive reports on a single page
- HTML5 chart instead of Flash. I want to access my APEX apps on ipad =)
- We have APP_PAGE_ID variable already. I would like to see something like APP_BUTTON_NAME. I have a function in button condition to determine whether we show/hide a button. The function takes page id and button name as parameters. Hence, it would be nice that we have APP_BUTTON_NAME instead of hard coding the name for every button condition function.
That is all for now, APEX comes a long way from HTMLDB to APEX 4.1. You guys did a marvelous job
I think many users will love this. Currently, when a user session expires (8 hours, by default), it will automatically return to the log-in page. Some users may have such experience as the following:
When he has finished entering a form with a lot of data, he clicks the "Submit" button to submit the form. If his session has already expired, whatever he has entered will be lost. In addition, he may think that it is an error of the system.
Therefore, it will be nice if there is a message indicating that the session has expired when it returns to the log-in page.