OpenEdge customer experiences are varied as their industries. Traditional OpenEdge clients exist behind the fire wall. Outside the firewall Web, Hybrid Apps, Native Apps and B2B Apps use Javascript Data Object (JSDO) and Representational State Transfer (REST) APIs to access the business logic and reliable data on the other side of the firewall.

Explore Web Applications

Progress provides the following web UI options for building customer user experiences that interact with the back-end business logic and data.

Additionally, any web UI technology that can work with REST services is supported.

Explore OpenEdge clients

OpenEdge client applications continue to be integral to the success of our customers and partners and include

  • ABL Client – Provides default client user interface in Windows (GUI) or in Linux/Unix (Character) representation of user interface widgets.
  • GUI for .NET - Provides extensions to the OpenEdge GUI client, to support the ability to access Microsoft .NET objects from ABL as if they were native ABL objects.
  • Batch clients - Runs reports and/or performs administrative tasks in the background. This type of client has no user interaction.
  • Open Client – Runs in a client process that is not an AVM. Open Clients can be written in C#, VB.NET, or Java, and they can present a variety of user interfaces to the end-user. They also provide access to ABL business logic to other applications written in the supported languages that do not have a user interface.
  • REST and SOAP Web service clients - Clients written in a variety of languages (ABL, Java, C#, VB.NET, HTML) can access an ABL application’s services if the application has been built to provide Web services. An ABL Web services client runs in its own AVM. Other Web services clients run in client processes that run in a DLL or JVM.
  • WebSpeed client - A WebSpeed client runs in a Web browser and is written in HTML and/or JavaScript. It accesses services by using HTTP or HTTPS to connect to OpenEdge applications.