- Readable APEX User - ADAM
- Often some new Developers or people who are not developing for an application should have an opportunity to look into the APEX code. It would be nice to have a setting to make them only readable. Also sometimes for customers or users on a productive environment it should be very helpful.
- APEX Application lockable - ADVQ
- It's not the same as the first point but points into a same direction. Having an Application which can't be changed for anyone it would be helpful to use a developement environment on a production and also have the possibility to have a look into different areas, without changing anything.
- Page flow Diagramm in APEX - AF7O
- Knowing how a page can be reached, or where can i go from a special page it would be really helpful to get a simple graph structure with a page flow diagram.
- Read only Condition – read only type option - AA4A
- Having not only a flat text for an input field when switching it to read only would be really great. Even that this option is closed for input it's an interesting point for me.
- Source Control - AGUE
- Often discussed feature but never the less interesting.
- Reusable regions as a shared component - AA8T
- Reuse a region on some pages without using the global page. Perhaps getting the possibility to define a global page per Page Group or for a set of pages would be great.
- Defining named Dynamic Action for different reuse - AD1B
- It would be really cool to define some Dynamic actions like named love and reuse them. Perhaps with some parameters or even without would be really cool.
- Tabs using URL Targets => Tabs can be opened with right click - AD1A
- Nothing to say? Even if they are not always the best choice it would be really good to have links which can be used with right-click in new tabs.
- Buttonlabels based on application language - AG02
- Developing in english language, but creating an application for a german (or none english) customer, it would be really helpful, to get the default names for messages or Button labels, based on the application language and not on the developer language setting.
Showing posts with label Lock. Show all posts
Showing posts with label Lock. Show all posts
Wednesday, January 29, 2014
some interesting features to vote for on apex.oracle.com/vote
Yesterday we had an APEX Meeting with nearly 50 people. My presentiation was focusing on the feature request board at apex.oracle.com/vote. In the presentation i mentioned some points which are very interesting and should be voted by more people. So here is a small list of features where everyone who is using APEX should take a look on
Tuesday, December 25, 2012
Wishing new features in APEX future Releases
Wishing new features in the next APEX releases can be affected by everyone in this official Feature Request Application. Now is the right time, because the last APEX Patch 4.2.1 is not far away and the next release will be a bigger one.
Here are some of my most desired features (beside the State of direction for APEX 5.0)
- Authorisation accepts parameter (Feature ABPY)
At the moment it's not possible in an APEX Authorisation Scheme to forward any information from the calling element. Further more it would be nice to have some variables, which could be referenced in the authorisation. Now you have to use the condition area to use specific parameters. If there is already some kind of condition (often already functional conditions are existing), the technical authorisation and the functional condition is mixed up. - Read Only condition - read only type option (AA4A)In the last projects, often we got the questions, why the read only text area or select-lists are displayed differently in standard read only mode. With this feature it would be possible to display the input element like the original one with only shown greyed out.
- Defining one named Dynamic Action for different use (AD1B)Often the same effect (Dynamic Action) should be used on different objects and even different pages to effect like the same way. In this case it would be nice to define named Dynamic Actions and only call these actions which are predefined in the shared objects.
- Tabs using URL Targets => Tabs can be opened with right click (AD1A)
It's only a small feature, but often when i use application in nower days, i'm disapointed, when i can't open a link in a new browser tab. In standard APEX at the moment it's not possible. - Able to lock whole application (ADVQ)
In many cases we have different people who are starting new APEX projects or customers who want to look into the development areas. These people should not be able to change anything but should be able to reach every attribute in the application builder. - Integrate with Subversion (ABAF)
Working with big APEX Applications, it would be nice to have an easy access to every APEX component by using subversion.
Subscribe to:
Posts (Atom)