The solution is very robust; I rate it a seven out of ten. I recommend it to others. I advise them to have enough training for application development.
I would not recommend Oracle Forms if you want to do development with this product for a new system because it's so old. It's more for maintaining all the systems. Considering this, I would rate it at three on a scale from one to ten.
My advice to people who are considering Oracle Forms as a solution is that they should look at the other Oracle products that are available. Forms is not for everyone. So they may want to consider J Developer or Oracle Application Express. Then after they survey all of these options then they can decide what they actually require for their company. Each of the products has its individual benefits and advantages — but also disadvantages as well. If you are working in a large organization, I think they should go for Oracle Forms because it is a very stable and very reliable application. But on the backend, it also requires a lot of resources and infrastructure. That requirement may make Forms less desireable for smaller organizations. On a scale from one to ten where one is the worst and ten is the best, I would rate this product above average as a seven or eight. To make it a nine or ten, the main features I would like to see is the change from making the output only available as a Java applet in 11G and even in 12G. That should be updated now. The output should be directly available and compatible with any internet browser and it should be available without any Java runtime environment like any other website or any other application without installing anything additional. It should come like that now. That is the main complaint from the end-users who I interact with. When you install a new PC and bring on a new user, they have to do a lot of work for the individual client to configure Java and other things. It seems like an unnecessary requirement.
We use the on-premises deployment model. My advice for others considering implementation is that you have to do some programming for mobile to ensure your forms will be following good practice and your code will be usable. I'd rate the solution nine out of ten.
Overall, I would rate it ten out of ten.
The solution is very robust; I rate it a seven out of ten. I recommend it to others. I advise them to have enough training for application development.
I would not recommend Oracle Forms if you want to do development with this product for a new system because it's so old. It's more for maintaining all the systems. Considering this, I would rate it at three on a scale from one to ten.
I would recommend people who want to use Oracle Forms to use Oracle APEX instead. I rate Oracle Forms an eight out of ten.
My advice to people who are considering Oracle Forms as a solution is that they should look at the other Oracle products that are available. Forms is not for everyone. So they may want to consider J Developer or Oracle Application Express. Then after they survey all of these options then they can decide what they actually require for their company. Each of the products has its individual benefits and advantages — but also disadvantages as well. If you are working in a large organization, I think they should go for Oracle Forms because it is a very stable and very reliable application. But on the backend, it also requires a lot of resources and infrastructure. That requirement may make Forms less desireable for smaller organizations. On a scale from one to ten where one is the worst and ten is the best, I would rate this product above average as a seven or eight. To make it a nine or ten, the main features I would like to see is the change from making the output only available as a Java applet in 11G and even in 12G. That should be updated now. The output should be directly available and compatible with any internet browser and it should be available without any Java runtime environment like any other website or any other application without installing anything additional. It should come like that now. That is the main complaint from the end-users who I interact with. When you install a new PC and bring on a new user, they have to do a lot of work for the individual client to configure Java and other things. It seems like an unnecessary requirement.
We use the on-premises deployment model. My advice for others considering implementation is that you have to do some programming for mobile to ensure your forms will be following good practice and your code will be usable. I'd rate the solution nine out of ten.