Skip to main content

Category: Blog

Q&A Forms 2 Apex – A jont success

Oracle Forms to APEX –
WEBINARS – Q&A

Your Questions and Answers about the
Migration from Oracle Forms to APEX

In our Oracle Forms and APEX projects and webinars, we receive numerous questions about the migration from Oracle Forms to APEX. These are questions about the technologies, the migration process, the methodology, the automation, the resources, the effort, the know-how, the organization, and much more. We have compiled the most urgent questions and answers from our recent webinar: ORACLE FORMS TO APEX – A JOINT SUCCESS STORY.

Your questions from the webinar ORACLE FORMS TO APEX –
A JOINT SUCCESS STORY

  • Is there option available for migrating Forms to Apex? Earlier version was having option but in new version not able to see the option


    The integrated APEX function to load Forms Modules into an APEX repository is no longer available. Oracle advice to get in contact with Partner like PITSS which provide solution for this.
  • We know Apex can replace forms, but what about Reports, is there any approach to replace it also?

    Depending of the complexity and usage of the Reports you could consider APEX Regions like Interactive Report or classic Report. In addition you could consider tools like AOP or Jasper Reports which could be smoothly integrated into the APEX App.
  • Is it possible to separate APEX DB from the Data DB?

    Yes – that is possible. The application Database with the APEX repository has not to be in the same database as the application data. You could consume data from different databases via DBLINK or WebServices, which itself could easily created by ORDS Tools.
  • How to use jasper report with apex?

    You could integrate Jasper reports via WebServices into your APEX app.
  • How can APEX be used for “Power Users” who only/mostly work with Keyboards?

    Depending on the way how keyboards is used. You could mimik a lot of Function-Keys and HotKeys with JavaScript, but this should be an exception. Is nowadays a huge amount of user input still necessary (RPA) and isn’t there a good point to improve the overall process?
  • How do I convert Oracle Forms that currently use the functionality of webutil to access client resources and network resources?

    Depending on the kind of resources which are used. Form e.g. “File upload” which is available in APEX, or Office Integration (like APEX Office Edit) which could be extend as a plugin to custom solution via nodeJS is everything solvable.
  • How streamlined is the conversion process. Do we need to move most of the business logic first to the back-end?

    This refactoring of PL/SQL logic will save your invest and is a adviced first step, which could be highly automized.
  • – can be delivered in phases?

    Yes – a staged approach, in which Forms and APEX running side by side is the best way to go.
  • Are there tools to migrate?

    Yes – PITSS Forms2APEX Modeler.
  • How does APEX handle converting complex Forms and Reports with multiple output file formats?

    Primarily the focus of the migration is from Forms to APEX. Even Complex Forms could be handled in APEX with multiple pages and numerous events.
    Migrating Reports to APEX depends on the use cases of those reports. Some of them could be migrated to native APEX, for others a migration to a dedicated report framework like Analytic Publisher, APEX Office Print or Jasper is more appropriate.
  • What is the HA architecture for APEX?

    For an HA architecture of your APEX Application use RAC on the database end. In addition, deploy multiple ORDS instances with a load balancer. See this references:
    https://www.oracle.com/docs/tech/developer-tools/apex-rac-technical-brief.pdf
    https://docs.oracle.com/en/solutions/deploy-ords-ha-oci/index.html
  • How did you approach integrations with local systems that normally are done with WebUtil?

    Some of those functions are covered out of the box like File upload or download. An integration with Office Products like Word, Excel, etc. is available. For others you could deploy a small node.js on client side and communicate via Javascript with your APEX application.
  • What is the percentage of migration from Forms 6i, 11G, 12C to APEX with PITSS?

    The answer really depends on the Application which is considered. Putting the focus on PL/SQL-Code we first improve code quality and maintainability by removing redundancy. All Units with more than 80% Redundancy to any other kind of unit may be a candidate. In a second step we move PL/SQL Code to the database to save the investment of implementation by following APEX best practices. These two steps don’t “migrate” any line of code to APEX but are a huge timesaver.
    From the objects we cover 100% of Blocks to regions, nearly 95% of all items (depending on the type), 100% of canvases to Pages, but on the other hand 0% of key triggers, because we try to find a better solution with the customer. So a percentage in total is not valid to consider.
    In all cases the source of the Forms version is not relevant.
  • How to migrate forms 6i to APEX ?

    In the same way as all other Forms Versions. See question 1.
  • How is the method to determine complexity and resources for a successful migration?

    In the Analysis we measure three different metrics. Complexity of documentation, that is, how long does it take as developer to understand the purpose of that module. Second we measure code complexity based on well defined maintainability metrics. Last but not least we measure layout complexity given by the layout and design of the canvases. All together with the identification of obstacles (code which doesn’t leave an easy solution in APEX) determine the complexity of a module, from which we derive all ressources.
  • What are the benefits of APEX?

    The advantages of APEX are mightyful. The first advantage is cost. There are no licensing costs associated with Oracle APEX. Oracle APEX is a feature of Oracle Database. If you have a license for Oracle Database you already have Oracle APEX. Another advantage of APEX is that there is no client software required, unlike in Forms where every developer needs Form Builder software installed on their computer. To build applications with APEX all you need is a web browser. Once the development environment is configured, your developers only need the URL to access the dev environment . They can start building applications right away. That’s one paint point lesser to getting started. APEX is a comprehensive platform which means you can build UI, manage database objects, create and use restful services and migrate data. All this without leaving the APEX ID. APEX is a complete package with all the tools you would need to build applications. The next benefit of using APEX is UI. Customers are looking to build browser agnostic. Operating system agnostic applications. To take it a step forward they also want their applications to be accessible not just on high resolution devices, but also on devices that fit in your hand. APEX uses a universal theme which guarantees responsiveness. Applications built using APEX, use universal themes out of the box. The universal theme is designed by UX experts on the APEX team, making sure that all the web design standards are met. Developers don’t have to worry about writing explicit CSS to make their applications responsive. APEX also has the pwf feature which builts web applications, are installable on mobile devices and are coming towards auditory Forms customers. The biggest advantage you get with APEX is reusability. All the underlying database programs like packages, functions, procedures can be easily called directly from Oracle APEX. Therefore, you do not need to write extensive database business logic which you are already using in Oracle Forms.
  • How to extract business rules out of Forms?

    With the product Application Engineering from PITSS you have the possibility to evaluate each PL/SQL Unit, if this is a candidate for running inside the database rather in Forms or APEX. The code will get refactored to consider potential context information, like Items, Globals, Parameters and the customer could ensure its own package structure and naming convention. Once configured, this can run for one unit or the entire application.
  • Do we have to rewrite the business logics which are part of the Oracle Forms 10g and written in the form of Procedure, Function and form level triggers?

    No – in general a lot of them could be moved to database packages and then reused in APEX.
  • How to call an external API?

    Depending on the nature of the external API? Everything which is accessible from the browser could be directly integrated into the APEX application. You could use WebServices or JavaScript to access external providers or libraries.
  • Is there a VOD I can watch in case I can’t make it?

    Yes, please get in contact with us
  • Is it convenient migration of complex functional Forms?

    “Convenient” is somehow very individual. For an experienced APEX developer it is convenient, while for a Newbie it is nearly impossible. The most significant answer is: APEX could cover any requirement which is solved with Forms and the migration is calculable without any surprises in technology or budget.
  • How to migrate Oracle Forms to Apex with security? Is Oracle ADF a good alternative or not?

    There are more and easier security solutions available in APEX rather than in Forms. No matter if you talk about Menu-Security, Authentication, Authorization or any other concept, this will be covered in the architectural phase of the Modernization Methodology.
    From our perspective ADF is not a valid option due to less support of Oracle for such a framework.
  • Is a transfer possible?

    Yes, follow Lisa’s talk and get inspired from her point of view. Request Video
  • I need to see examples about Forms code being migrated to an APEX environment.

    This depends on the nature of the code. We believe that the best way is to prove the “usability” of the generated fragments and the overall methodology directly on your application. For this we provide a Workshop
    There is no “fix migration”, that implies that all APEX applications, which are generated with PITSS Forms2APEX Modeler are looking the same! The result highly depends on your code and your choices during the Architectural phase.
  • What should we do with Forms built-ins i.e go_form, form_success, set_object_property, etc… .?

    As you enumerate, that depends on the nature of the Built-In and the place where it’s used, especially in which trigger. In some cases it becomes a single property of an APEX object, sometimes it becomes a one-liner in JavaScript, sometimes it could be ignored, because APEX already does what you want to do, sometimes its a definition of Style, etc.
    This is typically the task between the architectural phase and the implementation phase.
  • What about code that must be replaced with javascript and should be put before and after pl/sql code?

    If this is necessary, you will see each place as a microtask for the developer in the implementation phase.
  • Can the functionality of Forms and APEX be used in parallel?

    Yes. That is the reason why we try to move them to the database, to make them reusable for Forms, APEX and any other client that might use the same functionality. It is best designed to use them in parallel. There are possibilities to call APEX from Forms and the other way around. You can share information from the client side, and share information from the database side. That works side by side very well and allows you a running application during the migration.
  • Is APEX easy to use or complex?

    From our perspective it’s a typical LOW-CODE Framework which is easy to understand. Experts could do more fancy things, but there is a fast learning experience.
  • Can we shift the same Forms on APEX like 10g to 11g?

    No, a migration to APEX is more complex than compiling Forms 10g modules with Forms 11 compiler.
  • Role of Apex in Oracle EBS?

  • How to convert fmb and rdf with triggers in APEX pages?

    The answer depends on whether you consider forms-Trigger or RDF-trigger. Even for Oracle Forms Trigger the answer depends on the purpose of the trigger and at least of the implementation inside the trigger. Take the typical WHEN-VALIDATE-ITEM-TRIGGER in Forms. If it’s just a check if e.g. a date is not in the past, this will be a JS-expression in APEX, if it’s instead a 60+ liner with huge SQL Statements, best will be a database package procedure which will be called on page submit. There are over 90 different triggers only in Forms, in which your PL/SQL code could have one of various scopes (navigation, transaction, UI-Changes, validation, value-changes, etc.) With this you come very fast to more than 500 combinations. PITSS Forms2APEX Modeler allows you to calculate these matrices especially for your application and guide you through possible decisions.
  • How to get buy-in from older Forms developers to switch to APEX?

    It’s been great for our teams. The highly experienced software programmers can now focus on more technically difficult challenges, which they like. Our consultants are happy to build new skills in APEX, to address more minor issues, since it is a low code/ no code platform.
  • What are the Benefits for clients?

    Enhancing the customer experience through awesome usability features, and enhancing security features within the applications, are both benefits of APEX that are exciting for customers. Larry Ellison speaks to these benefits in his Cloudworld 2022 presentation as well from October 2022.
  • How is the upgradability of the auto generated code?

    100%. We don’t integrate proprietary code and follow APEX best practices.
  • How long does such a migration take/ effort? Was it automated?

    The effort and time highly depend on the Forms Application, its consistency and the Team which is responsible for the remaining work in the implementation phase. After an Analysis we could precisely calculate this.
  • What other skills besides Apex skills do I need to migrate Oracle Forms to APEX?

    Generell none beside PL/SQL, which may be obvious. Depending on the needs, you may enhance some business processes, which require Business know how. If you like to do more experienced things, you come to the point where you like to use JavaScript, CSS and perhaps on plugin Development. But it’s not mandatory.
  • What is the best solution to accommodate accessing client-attached devices (scanners, check endorsement devices, etc.) from a browser application like APEX?

    That depends. That depends on which device you are trying to access and whether the browser itself has exposed APS to make it possible. However, APEX also has a plugin framework, so even if some features like accessing a certain client detached device is not implemented out of the box in APEX you can implement the same, using the webbrowser APS and generalize this particular implementation as a plugin. APEX facilitates that. I would also like to mention APEX.world which is a website having plenty of plugins created by the APEX community. If you are trying to configure a specific client device you can go there and check if there’s already a plugin available and import that into your APEX application.
  • Is it possible to reverse engineer 100% functionality?

    Yes, in general we cover 100% of your existing code and parse them successfully.
  • Do you sell migration software or methodology ?

    Yes, both of them.
  • Is APEX scalable and secure as Oracle Forms?

    Toufiq Mohammed: The short answer is yes.
    APEX architecture provides scalability out of the box. As long as you use out of the box components in APEX they are developed keeping security in mind.
    APEX also provides various options like authorization schemes, authentication schemes to help you implement security in your apps.
  • What is the best long term solution for Oracle Form migration?

    You won’t get an answer from Oracle for this. Our personal advice is to consider a modernisation with APEX
  • What is the biggest challenge in migrating complex Forms with many tabs/windows and lots of inter field validation?

    In such a case, the biggest challenge is to decide, which of these validation is necessary on field navigation and could that be solved without page submit. Sometimes users are teached to use the Forms in a way, because Forms don’t allow or the developer decides to implement, no other usage. This has to be reviewed.
  • What is the most blocking point for Oracle Forms developers to learn Oracle APEX?

    We don’t see a really blocking point. Most irritating is the stateless behavior of APEX which sometimes creates some questions.
  • Do APEX applications comply with OWASP Top 10?

    Yes. For each of the ten points in the OWASP document, APEX has ways to implement them. APEX also has an advisor utility built in which can help identify security issues upfront. For more information follow: https://docs.oracle.com/en/database/oracle/apex/22.2/htmdb/running-advisor-to-check-application-integrity.html
  • What is the recommended best practice for architecting an APEX installation/node on a stand-alone server that can query data from multiple Oracle databases?

    Due to the fact that you could either use database links or WebServices, this decision is not depending, where you deploy your APEX application. This has to be decided according to the accessibility and availability of your APEX application.
  • How is it possible to run APEX out of our transactional database where all the data is? I know about using database links with all the limitations but using a data model based on external services (like REST) would make APEX much more flexible. So, should we expect APEX to become more independent from the underlying database like utilizing APEX Restful Data Services and be used more and more as a front end development environment for various backend systems?

    This is definitely one of the possible deployment options of APEX. The solution depends on the requirements of the Application and sometimes it’s really oversized to install a second database for APEX only and consume data from another database via REST which is stored on the same machine.
  • How complicated Forms screen/canvases are migrated? Child/parent blocks? Do you have to redesign the screens?

    In general a modernisation is forced by the possibility to enhance the capabilities of the screens. So a redesign of the screens is a usual step in the modernisation, but it’s not forced. More important is that the underlying data, business rules and validation are captured well.
  • What about the code that exists in the Forms and not on the database, is it transferable? Does APEX support PL/SQL?

    Yes in both cases. First choice is to move as much (and that’s more than you expected) into the database. At the end, you have to adjust code, but APEX work pretty well with PL/SQL.
  • How do you address the data block object in Forms? Did you choose IR and Form or IG?

    You could decide this in the architectural phase. The PITSS Forms2APEX Modeler advises the best option, but you could block per block overwrite to IG, IR, CR or Forms Region.
  • Where do you advise to install APEX in production? Same Oracle database server or application server where Forms is running?

    Both. The APEX repository is part of the database where ORDS will be deployed on the application server.
  • Would you put the links to those learning channels in the chat?

    They are also given in this Q&A
  • If we have about 600 Oracle Forms with various application modules, how do you go about converting them to APEX? Big bang conversion or one application module at a time? Please note that these modules interact with each other and navigation exists between them.

    We advise a staged approach. With our Product we could determine all dependencies and advise the best clustering approach.
  • What is the nature of the generated code? Once converted to Forms how are future upgrades handled (DB and APEX) – does the code make it trickier?

    It’s pure, proprietary free APEX code – as if it were written by the best APEX developers available.
  • Can you go over a typical workflow for remote developers developing APEX apps on their workstations and deploying them to on-prem production servers?

    Please follow the blogpost from Steve Muench from Oracle: https://blogs.oracle.com/apex/post/application-development-lifecycle-technical-paper
  • What APEX version is currently used in the PITSS migration tool?

    We could generate any code from 5.1 until the latest version.
  • What about server sizing? In Forms we can compute the amount of memory for a specified number of users expected. Can we do that with APEX?

    Oracle Forms and Oracle APEX are different architecturally. So compute wise sizing may vary as Oracle APEX uses highly scalable 3 tier architecture. Whereas the memory calculations for a given set of concurrent users should be same for both forms and APEX. For more information consider: https://joelkallman.blogspot.com/2014/03/finallythe-official-sizing-guide-for.html
  • License costs and needed environment for APEX (on premise, cloud, Database version etc. )”

    NA – I assume, this question is dedicated to the specific environment of Savantage.
  • El esfuerzo comparado con la migración de Forms 6i hacia Forms12c, como podemos considerar el esfuerzo para migrar de Forms12c hacia APEX?

    No sé cómo migraron de Forms 6i a 12c. Si ocurrió con PITSS.CON, el esfuerzo no fue tan elevado. En general, sin embargo, una migración de Forms a APEX es más difícil que una actualización dentro de la pila de Forms.
  • In the Savantage case, how many Forms were migrated to APEX and what was the percentage of automatic migration and manual rewriting.

    Not allowed to answer due to NDA.
  • Why not Forms? Why APEX?

    To get rid of the Java-dependency of the client and allow access from tablets and smart devices. In addition to profit from the possibility of responsive design, new UI components and being part of an agile and fast growing Low-Code Framework.
  • I want to learn about your experiences and recommendations, but I’m concerned about the sizing of the server and scalability.

  • What are the benefits for your client and for you as a company?

    Lisa Kazor: Enhancing the customer experience through awesome usability features, and enhancing security features within the applications, are both benefits of APEX that are exciting for customers. Larry Ellison speaks to these benfits in his Cloudworld 2022 presentation as well from October 2022.
  • How was your development team reacting to the decision to go with APEX? Did they fear to lose Forms or are they excited to step into APEX?

    Lisa Kazor: It’s been great for our teams. The highly experienced software programmers can now focus on more technically difficult challenges, which they like. Our consultants are happy to build new skills in APEX, to address more minor issues, since it is a low code/ no code platform.
  • What is the best solution to accommodate accessing client-attached devices (scanners, check endorsement devices, etc.) from a browser application like APEX?

    Toufiq Mohammed: That depends. That depends on which device you are trying to access and whether the browser itself has exposed APS to make it possible. However, APEX also has a plugin framework, so even if some features like accessing a certain client detached device is not implemented out of the box in APEX you can implement the same, using the webbrowser APS and generalize this particular implementation as a plugin. APEX facilitates that. I would also like to mention APEX.world which is a website having plenty of plugins created by the APEX community. If you are trying to configure a specific client device you can go there and check if there’s already a plugin available and import that into your APEX application.
  • How do you develop as a team in Apex?

    Toufiq Mohammed: APEX makes it possible for multiple developers to work on the same application without stepping on each other’s shoes. A page log in APEX provides a feature called page log in. If a developer is working on a page he can log the page so that other developers cannot edit it. Every attribute in APEX has an update production. If I am updating a particular attribute and other developers are also working on the same attributes he gets an error message saying that this is already modified by another user. All these features prevent a developer writing over other developers code.
    APEX also has a team open module which the entire team can track their bugs and milestones in APEX. I also want to suggest you take a look at a technical whitepaper published by my colleagues’ team. This whitepaper contains a detailed explanation of how developers can work as a team in APEX. It explains even the CICD processes that you can ?? with APEX.
    All sources that Toufiq suggested:

    APEX Foundations : apex.oracle.com/go/foundations

    Hands on Labs : apex.oracle.com/hols

    Forums: apex.oracle.com/forum

    Office Hours : apex.oracle.com/officehours

    Youtube : apex.oracle.com/youtube

    Blogs: apex.oracle.com/blog
  • Do we have to rewrite the business logics which are part of the Oracle Forms 10g and written in the form of Procedure, Function and form level triggers?

    Stephan LaRocca: The answer is no and yes. It depends. With our product we have the possibility to evaluate each function and each trigger on its possibility to be moved to the database. That means we have to refactor them in a way that references to blogs, items, parameters and a subset of built-in functionalities could be replaced if we move them to the database. But as I said before, there will definitely be code left that has to be re-written in APEX in either PL/SQL as well or JavaScript, whatever is better in that case. With our assumption and calculation there is roundabout 30-40% which will be moved to the database and can be saved that way.
  • What about the upgradability of the auto generated code?

    Stephan LaRocca: That’s easy to answer: It’s 100%. The auto generated code is exactly the same like you work on a regular base with APEX. We use the regular import functionality to import the code into your generated APEX application. We follow APEX best practice. As the day after, some developers open the APEX page designer there should not be any bite that decides and allows him to identify if that is generated with our product or if it’s handmade. So there is no generated code which has to be updated in a different way. We generate APEX to use their core functionality and it’s in the same new life or you will code your application.
  • Need to know about the whole cycle

    Please follow our description on: hForms2APEX Modeler
  • What are the lessons learned?

    Having the right partner for such a project is the key. The unknown – how developers as well as clients expect and experience the new look and feel in APEX – has gone extremely well.
  • Why Forms to APEX? Is it really necessary?

    Only dying is necessary.
  • Everythings made in Oracle Forms, is it possible to replicate it in APEX?

    With more or less effort, with more or less necessity, yes.
  • Would be interested to know how APEX handles Master-Detail- setup. That is already solved with APEX 5.1

    That is already solved with APEX 5.1
  • Want to see the integration

    There are different ways of integrating Forms and APEX depending on the specific business need. Please contact, if we should design for your specific application.
  • Are there any considerations to migrate from Oracle Forms 6i to APEX, mainly because the application makes intensive use of user_exit calls?

    No. You have to define a new “home” for such C-Routines behind the User-Exits and depending on the target, you could integrate the call into your APEX application.
  • The biggest hesitancy for moving forward is from a production/operations point of view at this time?

    Request – Why?
  • What about Oracle Forms Web? Isn’t it a better solution than APEX?

    No – none of the advantages of APEX could be fulfilled with Oracle Forms Web.
  • We are still using Forms 6i client/server on several applications and slowly migrate to web applications (Java based).

    Lucky guy – should we help to speed up?
  • As it is keeping our Oracle database outdated, we need a fast way to migrate our legacy systems?

    Start with an analysis to calculate your project plan.
  • Is the best solution APEX or a newer version of Forms Web?

    Depends on your need. If you’re in a situation like Lisa, APEX is the best solution.
  • Can you elaborate more on PITSS tool move form to APEX, any licensing or ACM, timeline to convert around 500 Forms?

    In such case please contact: sales@pitss.com
  • Do we have a date from Oracle when they will sunset Oracle Forms platform?

    No – Oracle won’t plan to sunset for Oracle Forms. You will see that release planning of APEX is totally different to Oracle Forms.
  • How can I get virtual work on my pc for training?

    We advise you to choose one of the pre-built Virtual Machines from Oracle.(https://www.oracle.com/downloads/developer-vm/community-downloads.html)
  • Has PITSS looked at providing the ability to convert from other Oracle development tools (OAF/OC4J), etc. to APEX as well?

    A good question. Not by now, but it’s worth it. Do you have a need for this, contact us.
  • Having said that objects that reside locally in Forms will most likely need or be required to be moved to the database for APEX to perform the same as our existing application, do you recommend for the developers to move this code to the database first in preparation to convert to APEX?

    Yes – but this could be automated with our product.
  • Did you have to make changes to a page in terms of functionality that perhaps caused the end user to say they did not recognize the page in comparison to the original form?

    No – if such changes where necessary, they are requested by the user.
  • What are the benefits for your client and for you as a company?

    Lisa Kazor: Enhancing the customer experience through awesome usability features, and enhancing security features within the applications, are both benefits of APEX that are exciting for customers. Larry Ellison speaks to these benfits in his Cloudworld 2022 presentation as well from October 2022.
  • How was your development team reacting to the decision to go with APEX? Did they fear to lose Forms or are they excited to step into APEX?

    Lisa Kazor: It’s been great for our teams. The highly experienced software programmers can now focus on more technically difficult challenges, which they like. Our consultants are happy to build new skills in APEX, to address more minor issues, since it is a low code/ no code platform.
  • What is the best solution to accommodate accessing client-attached devices (scanners, check endorsement devices, etc.) from a browser application like APEX?

    Toufiq Mohammed: That depends. That depends on which device you are trying to access and whether the browser itself has exposed APS to make it possible. However, APEX also has a plugin framework, so even if some features like accessing a certain client detached device is not implemented out of the box in APEX you can implement the same, using the webbrowser APS and generalize this particular implementation as a plugin. APEX facilitates that. I would also like to mention APEX.world which is a website having plenty of plugins created by the APEX community. If you are trying to configure a specific client device you can go there and check if there’s already a plugin available and import that into your APEX application.
  • Do we have to rewrite the business logics which are part of the Oracle Forms 10g and written in the form of Procedure, Function and form level triggers?

    Stephan LaRocca: The answer is no and yes. It depends. With our product we have the possibility to evaluate each function and each trigger on its possibility to be moved to the database. That means we have to refactor them in a way that references to blogs, items, parameters and a subset of built-in functionalities could be replaced if we move them to the database. But as I said before, there will definitely be code left that has to be re-written in APEX in either PL/SQL as well or JavaScript, whatever is better in that case. With our assumption and calculation there is roundabout 30-40% which will be moved to the database and can be saved that way.
  • What about the upgradability of the auto generated code?

    Stephan LaRocca: That’s easy to answer: It’s 100%. The auto generated code is exactly the same like you work on a regular base with APEX. We use the regular import functionality to import the code into your generated APEX application. We follow APEX best practice. As the day after, some developers open the APEX page designer there should not be any bite that decides and allows him to identify if that is generated with our product or if it’s handmade. So there is no generated code which has to be updated in a different way. We generate APEX to use their core functionality and it’s in the same new life or you will code your application.

Your Contact

Uta Daniels Assistant
of Sales Management

udaniels@pitss.com

+49 711/914-012-12











Continue reading

RETROGRADE PROCESS ANALYSIS MADE EASY

RETROGRADE PROCESS
ANALYSIS MADE EASY

SoftProc makes even highly individualized software understandable, because it analyzes and visualizes implemented applications from the program code to the productive process from within the running application. This seamless, digital documentation makes their modernization easier, faster and more cost-effective.

Software modernization is indispensable to remain secure and functional. Especially when individual software can assure a company a unique selling proposition. But it is also necessary in order to be able to meet the requirements of increasing digitization, which include a change in user behavior. Financial and insurance advisors are a classic example of this. For decades, they have been using desktop-oriented software simply because of regulatory requirements. In order to be able to use this on mobile devices when visiting customers, the software had to be modernized. But the company processes themselves are also subject to permanent change. For example, the increasing interconnection of business partners often justifies the need to modernize. In this case, applications have to be modularized, split and converted. Another reason to renew individual software is that the older the software, the higher the maintenance effort. The reason: The knowledge of the code has long since been retired along with the programmer.

Process Mining Looks at Business Processes through Data Glasses

Most of the time, modernization is not about switching to a different software. Especially not when a company’s core competence is supported by custom software. The intention behind it is to optimize business processes and make them more flexible for any future requirements, to be able to adapt them to changing market situations and to expand them to incorporate new technologies. However, to ensure that all previous functions are still available completely and without errors after modernization, and to take into account any dependencies on other systems and the influence of special cases, the processes supported by the system must be fully known and documented. In many companies, this knowledge was lost due to fluctuation in IT or was never really available due to missing or poorly maintained documentation. Process mining tools solve exactly this shortcoming: they visualize business processes through a data-driven view and provide complete transparency about their lived reality. Within process mining there are several sub-disciplines. Compliance compares the originally defined process model with the actual process flow by the user. Prerequisite: The definition is recorded somewhere. Process discovery uses log data to draw conclusions about what the process implemented in the software actually looks like.
wants to merge its locations and harmonize the business processes in the course of a software modernization. During the compliance check, it turns out that clicking on the command ‘Execute order’ sometimes triggers different changes in the data model for the employees from the different locations. So there must be a deviation from the originally defined process. But why is this the case? Which one is the right one and therefore needs to be migrated? The answer can be found with Process Discovery. In contrast to the employee at location A, his colleague at location B also looks after customers from abroad, for whom other conditions apply with regard to delivery time, customs, etc. The same command therefore has two different processes. So behind the same command there are two different data models, which must be available again in exactly the same way after the modernization.

On the Track of the Data Model

In order for process mining tools to be able to perform comprehensive process analyses and visualizations, they must, on the one hand, ‘understand’ the data model underlying the software and, on the other hand, obtain the most accurate possible event stream of the process data in the standard XES format from the software systems to be analyzed. For large standard systems with constant data models such as SAP, Microsoft Dynamics or the Oracle E-Business Suite, there are separate process mining programs that are familiar with the data structure of the standard applications. However, as soon as companies have adapted these standard systems to their requirements, the event stream information required for process mining can no longer be extracted automatically from the application. And thus they face the same problem as users of pure custom software or legacy systems: To get the raw data for process mining, they have to bridge the gap between process and data model themselves.
Currently, there are two ways to do this. The first: Key users and process owners describe the ideal flow of the business processes in extensive interviews. In parallel, the data model is parsed to identify the effects of an input process within the data model. The subsequent analysis of the data model allows an interpretation of the underlying processes, i.e. actions that are caused by changes in the data model and not by direct input. This method is not only very time-consuming. Misunderstandings, misinterpretations or simply unconsciously incomplete information lead to the result being just an assumption and not a fact, which can lead to devastating misinterpretations.
The second – and currently the only software-supported method – was developed by the SoftProc project. Funded by the BMBF, PITSS GmbH and the University of Ulm have developed a software-supported method for retrograde process analysis from a running application. What is special about it is that it recognizes user behavior and, based on knowledge of the table structure, establishes the context between the underlying data models. The context identified in this way now makes it possible to assign an input process to a change in the data model using classic process mining methods – even in custom software.


Modernization

Why and how to modernize legacy applications efficiently

Read more


Sponsorship project

PITSS is awarded a BMBF funding project for digital software documentation

Read more

Illustration: All information automatically collected by SoftProc for a process.
Explanation: All information is output in the common data stream format xes.
Meaning: The totality of all information about all processes can be imported and used in a process mining or process discovery tool 

SoftProc Looks at the User, Not Just the Data

But how exactly does this data stream come about in SoftProc? How are user behavior on the one hand and its effects in the data model on the other hand captured? And how can this data stream be used as a transformation link between a custom software and any process mining tool? In order to identify the software processes, SoftProc observes the user as he executes a business process, for example ‘execute order’, via his user interface. There are two different recording variants. In the case of dedicated recording, the user determines the start and end of the business process to be recorded and thus precisely delimits the functionality that constitutes it. In the end, it’s like an interview – only faster and without forgetting a step that is already being executed automatically, so to speak, without having to think about it.
Silent recording, on the other hand, logs the entire use of the application – from the first time the user logs on to the time the application is closed. Machine learning methods can recognize patterns in this recording. To be more precise: they recognize, for example, whether the user has also executed an order. Even if he did so differently than his colleague due to a ‘special case’. Since here patterns are not searched for in the data models, but in the actions of the user, these in turn are linked in SoftProc without any doubt to the application process and the associated data tables. Therefore, in SoftProc, it is possible to understand why a business process was executed differently, even without interviews.
The ability to link to the data is also one of the reasons why SoftProc is so interesting, especially for custom software. SoftProc is based on an Oracle development platform. Therefore, the nomenclature from the user interface of a software also based on Oracle can be taken over directly to get context information from the program and finally merge it with the data. SoftProc speaks the language of the user, so to speak, and therefore every piece of code that was not captured during recording and thus not yet assigned to a business process can be traced back to the dependency in the user interface. And thus valuable functions, which were once programmed elaborately, but for various reasons were never used and therefore did not cause any change in the associated data tables, can be identified and preserved.

Illustration: Example Forms Flow – User behavior in dedicated recording
Explanation: There are many changes between individual forms.
Meaning: User jumps back and forth a lot between the forms – optimization potential for the process becomes apparent in order to simplify or shorten the process flow. 

Illustration: Process flow – what and how were the elements used.
Explanation: Shape, color, size, values provide information about type, interrelationships and weaknesses.
Meaning: Optimization potentials are shown 

Industry-Independent Solution from the Cloud

For whom is the solution now available from the funding project, which can read in, analyze, understand and map applications, suitable? For the time being, for everyone whose application was programmed in Oracle. It is completely irrelevant to which industry the application was tailored. Then, of course, for those who want or need complete documentation of their custom software. SoftProc should be considered by companies who anticipate that modernizations will be imminent, which will be very time-consuming and extensive, but want the application to be available again to the business and/or production processes as soon as possible.
The tool, which PITSS also offers as a cloud solution, is not only helpful for modernizing individual or legacy applications when the former programmers are no longer available. SoftProc also supports those who have already displaced how much time, effort and perhaps nerves they have invested to overcome hurdles in programming. Even if it is perhaps less rocky and one can go thereby now and then a step faster – the way of a renewed programming is the same as the first time. With SoftProc, however, it can be reliably shortened.

Your Contact

Uta Daniels
Assistant of Sales Management

udaniels@pitss.com
+49 711/914-012-12











Continue reading

PITSS.CON Release 23.3.1 with an outlook

PITSS.CON Release 23.3.1
with an outlook

Just in time for Advent, PITSS delivers
the first gift – PITSS.CON Release 23.3.1.

In this blog article, we take a detailed look at the outstanding functions of the latest PITSS.CON version as well as the PITSS ‘ “development laboratory”, where the seamless work on the in-house product range continues.

Highlights of PITSS.CON Release 23.3.1

  1. Simplified integration through automatic parsing and loading of modules

    With this release, the integration of PITSS.CON is easier than ever before. Automatic parsing and loading of modules enable a seamless connection and speeds up the workflow for developers significantly.
  2. Code refactoring (BL2DB) for the migration from Oracle Forms to Oracle APEX
  3. Another focus is on simplifying the migration from Oracle Forms to Oracle APEX. Enhancements in the area of code invoicing (BL2DB) effectively support developers in making a smooth transition.

  4. New “ProFind” module – process detection and documentation of highest quality
  5. The brand new “ProFind” module sets standards in process documentation. It enables detailed recording of all objects, object components, processes and dependencies down to the smallest detail to ensure optimal preparation for modernization projects.

  6. Supports the latest Oracle Forms version 12.2.1.19
  7. The new PITSS.CON version supports the latest Oracle Forms version 12.2.1.19 to ensure that developers can benefit from the latest features and a smooth integration.

  8. Certification on the Oracle Autonomous Database
  9. Release 23.3.1 brings a certification on the Oracle Autonomous Database with it. This underlines the high quality and security of PITSS.CON in the modern database landscape.

  10. Improvements in the generation of APEX applications
  11. The generation of APEX applications has been further optimized to enable developers to work more efficiently and precisely.

  12. Supports the latest Oracle APEX version 23.2
  13. PITSS.CON remains compatible with the latest technologies. Support of Oracle APEX version 23.2 is a clear signal for the innovative capability of the PITSS product.

  14. Extension in project management for Forms2APEX projects
  15. The project management for Forms2APEX projects has been extended to give developers even more control and overview of their projects.

    As a PITSS.CON customer, you can now arrange your individual PITSS.CON New Release Session with your team and one of our experts. Let us show you the new features and how you can benefit from them with your application.

A look into the future: Visionary developments with PITSS.CON

PITSS.CON’s developments are continuously ongoing and a look into the future promises exciting innovations

  1. Pattern and handwriting recognition of developers

    PITSS product developers continue to work on increasing the level of meaningful generation in APEX. This is to be achieved by recognizing patterns and the handwriting of each developer using pattern recognition.

    Possible hurdles and errors in APEX are to be recognized automatically and provided with context help to ensure a smooth development process.
  2. Further development of ProFind through machine learning and AI
  3. ProFind takes itself to a new level by integrating machine learning and artificial intelligence. It will not only analyze tables, but also recognize concepts and layers (bottom-up) to enable a deep understanding of applications.

  4. APEX Project Eye Integration
  5. The integration of APEX Project Eye (APE) will enable comprehensive visualization and monitoring of APEX projects to further optimize the development process. The perfect complement to the ProFind module.

  6. ProcMAPE – Monitoring, analysis, planning and execution
  7. The strategic goal of ProcMAPE development is the implementation of an automated solution approach for monitoring and analysing ongoing processes as well as the planning and system execution of necessary process and code adaptations. Self-learning (implementing self-learning algorithms), self-adopting (adaptation of software to user behaviour) and software development (continuous software development towards more adaptable systems) are components of this development.


Modernization

Why and how to modernize legacy applications efficiently

Read more


Sponsorship project

PITSS is awarded a BMBF funding project for digital software documentation

Read more

Your Contact

Uta Daniels
Assistant of Sales Management

udaniels@pitss.com
+49 711/914-012-12











Continue reading

Dynamically get the value selected for autocomplete in Oracle APEX

Dynamically get the value selected
for autocomplete in Oracle APEX

Sometimes we would like to return the selected values from autocomplete and continue to use them in another Javascript function or send the value to the server. This is where Oracle APEX Autocomplete comes in handy.

Oracle APEX Autocomplete is a mechanism commonly used in modern websites to provide the user with a list of suggested words that they have typed in a text box. The user can then select an item from the list displayed in the input field. This feature saves the user from having to type an entire word or a series of words. In this article, you will learn how to dynamically retrieve the selected value for autocomplete in Oracle APEX.

Create a Oracle dynamic action

  • Name: getselectedValue
  • Event: select
  • Item(s): choose your autocomplete Page Item
  • Event Scope: static
  • Action: Execute Javascript Code
  • Code: console.log(apex.item(this.triggeringElement.id).getValue())
  • Fire on Initialization : No

Das neue PITSS.CON Release für Oracle Forms 14c

Der leichte Weg für den Upgrade und die Optimierung von Oracle Forms Applikationen

Mehr lesen


Förderprojekt BMBF

PITSS erhält Zuschlag für Förderprojekt des BMBF zur digitalen Softwaredokumentation

Mehr lesen

Your Contact

Uta Daniels
Assistant of Sales Management

udaniels@pitss.com
+49 711/914-012-12











Continue reading