1 7 8 9 10 11 Previous Next 201 Replies Latest reply on Oct 30, 2007 11:38 AM by 478676 Go to original post
      • 120. Re: APEX 3.1 Enhancements
        Hi , besides what has been mentioned , I would also like :

        - Being able to run 2 versions of htmldb in one database. At least for the duration of the upgrade. Like running 3.0 standalone with one user to make sure that all my applications are running fine before giving access to public

        - Ability to change the internal message like : 'Invalid Login Credential' and the other messages that we cannot translate

        - Have a default web page when the database is down. If the database is shutdown , I get a page not found for all my pages. This could be useful when we are doing upgrades.

        • 121. Re: APEX 3.1 Enhancements
          RE: Database/APEX Downtime and System Message

          We've done this with the 10g (R2) app server for downtime. Should
          work on Apache Server (10g companion cd) too. This will redirect
          all apex traffic to a static web page with an error message.

          Edit the dads.conf file and add the 2 ReWrite lines

          <Location /pls/htmldb1>
          SetHandler pls_handler
          Order allow,deny
          Allow from All
          AllowOverride None
          RewriteEngine on
          RewriteRule ^/(.*) http://llpas1:7779/html/error.html
          PlsqlDatabaseUsername htmldb_public_user
          PlsqlDatabasePassword @BSfjQJ9cgfF7lyKaNCaf9Zw=
          PlsqlDatabaseConnectString nc1sand:1523:lld1 SIDFormat
          PlsqlNLSLanguage American_America.UTF8
          PlsqlDocumentTablename wwv_flow_file_objects$
          PlsqlDocumentPath docs
          PlsqlDocumentProcedure wwv_flow_file_mgr.process_download
          PlsqlDefaultPage htmldb_login
          PlsqlErrorStyle ModPlsqlStyle
          • 122. Re: APEX 3.1 Enhancements
            Thanks David.

            That is really really great !

            I will try this RewriteRule

            • 123. Re: APEX 3.1 Enhancements
              I don't know if this is possible, but I would like to see one workspace able to access many schemas within the database.

              We have a lot of compartmentalized apps and having to have a new workspace for each schema is really annoying.

              • 124. Re: APEX 3.1 Enhancements
                Hi Michelle,

                you can already assign multiple schemas to a workspace!

                Or are you using APEX 2.1 with Oracle XE?

                My APEX Blog: http://inside-apex.blogspot.com
                The ApexLib Framework: http://apexlib.sourceforge.net
                The APEX Builder Plugin: http://sourceforge.net/projects/apexplugin/
                • 125. Re: APEX 3.1 Enhancements
                  Gaétan Francoeur
                  Popup LOV with redirect :-) acting like "drop down list" with redirect. A must...
                  • 126. Re: APEX 3.1 Enhancements
                    No, we are using 2.2.1 on Oracle 9iR2

                    I knew you could assign a schema to different workspaces, but can't find any way to assign a workspace multiple schemas.

                    • 127. Re: APEX 3.1 Enhancements

                      login into the Workspace: INTERNAL with your Admin user.

                      I don't have a 2.2 anymore, but I think it will be named similar. Go to "Manage Workspace to Schema Assignments", there you have the possibility to assign different Schemas to your workspace.

                      • 128. Re: APEX 3.1 Enhancements
                        Oh, My Gosh, that is wonderful!!!!!

                        Thanks so much for your help, this will make my life so much simpler.

                        • 129. Re: APEX 3.1 Enhancements
                          I would suggest a change to the html_PPR_Report_Page() function as described in the following thread:

                          Suggestion: htmldb_html_elements.js htmldb_PPR_Report_Page

                          • 130. Re: APEX 3.1 Enhancements
                            Sometimes there is the business need to hide a complete report region if the report doesn't return any rows.

                            Currently you have to duplicate the report query and the where clause restriction and put it into a "Exists (SQL query return at least one row)" condition on the region to hide the region if nothing is returned.

                            It would be more desirable to have a system variable or a new condition to check if the report query has returned something.

                            Business need:
                            Duplicating the report query increases the maintenance cost and the chances are high that they are not synchronized if the query is changed.
                            From a performance point of view , it's also not desirable to execute the report query twice.

                            My APEX Blog: http://inside-apex.blogspot.com
                            The ApexLib Framework: http://apexlib.sourceforge.net
                            The APEX Builder Plugin: http://sourceforge.net/projects/apexplugin/
                            • 131. Re: APEX 3.1 Enhancements
                              Another enhancement that would be nice :

                              allow export and import of pages and shared components only.

                              We are using standard migration from dev to test to prod.

                              Overtime, in our 100+ pages application, we make changes and want to migrate to test and prod. The problem is that copying all the application to test and prod means having to re-test everything (all the pages).

                              If we could compare the production application vs the dev application, we could only migrate the changes.

                              I know that in 3.0 we can copy pages only but it would be nice if we could bundle x number of pages in an export file.

                              ex: export page 3,6,10,50 and shared components.


                              • 132. Re: APEX 3.1 Enhancements
                                Francis - You can do that in 3.0 using the component export feature.

                                • 133. Re: APEX 3.1 Enhancements
                                  Hi Scott,

                                  Cool ! All that is missing is an Application Compare between databases

                                  Ex: Compare application 99 in dev with application 99 in prod to find out exactly what has been changed.


                                  • 134. Re: APEX 3.1 Enhancements
                                    John Edward Scott
                                    Hi Francis,

                                    Well you can also do that by importing the apps into the same instance, e.g. -

                                    1) Export app 99 from production
                                    2) Import app as another id (say 1099) into dev
                                    3) Use the 'Application Comparison' report to compare app 99 with app 1099.

                                    1 7 8 9 10 11 Previous Next