OpenEdge World Tour 2026: Now on Demand Across Asia Pacific

OpenEdge DDM is specifically designed to target individual fields (columns) in a table. Masking an entire table as a single object or filtering data by row is not supported natively, but both can be achieved through workarounds. To mask an entire table, you must configure masking for each column within the table. You can write an OpenEdge Advanced Business Language (ABL) script using the IDataAdminService API and loop through the target table's columns to apply masks to multiple columns in the same table.

For row-level filtering, you can use application-level logic in ABL, such as embedding WHERE-clause filtering into data services or Progress Application Server (PAS) for OpenEdge back-end code before sending data to the client. We can provide a demo to explain these workarounds. The Progress Professional Services team can also help with DDM implementation.

Yes, enabling FIPS mode in the OpenEdge platform may introduce some performance overhead, but in most real-world cases it is small to moderate and depends on how much cryptography your workload uses.

It is recommended that you test your use cases to validate the impact of enabling FIPS mode. Refer to this document: https://docs.progress.com/bundle/openedge-frequently-asked-questions/page/FIPS-mode-FAQ.html

The Progress Professional Services team can help with FIPS mode implementation.

The OpenEdge team is actively aligning its security roadmap with emerging post-quantum cryptography (PQC) standards, including hybrid key encapsulation mechanisms (KEM) for TLS. Support for hybrid post-quantum TLS is being evaluated in line with industry standardization efforts. As hybrid post-quantum TLS standards mature and gain broad industry adoption, the team will incorporate support through its underlying platforms, facilitating enterprise-grade stability, compatibility, and security. Regarding supported Java versions, you can check the officially supported Java versions for your specific OpenEdge release by reviewing the Progress OpenEdge Compatibility Guide: https://community.progress.com/s/article/000021264

Java 27 is not a Long-Term Support (LTS) release and has not yet been released. Progress certifies only LTS versions of the Java Development Kit (JDK) to maintain system stability and avoid backward-compatibility disruptions.

OpenEdge 12.8 is certified for the older LTS version, Java 17, however certification for Java 21 is currently on the roadmap: https://community.progress.com/s/article/Are-there-any-plans-to-support-Java-21-and-25-for-OpenEdge-12-8

Yes. OpenEdge 12.8 and 13 can integrate with Azure Identity (Microsoft Entra ID / Azure AD), but not as a native ‘plug‑and‑play’ identity provider. Integration is achieved through PAS for OpenEdge (PASOE) and/or the OpenEdge Authentication Gateway (OEAG), depending on the application architecture. Helpful resources:

• https://community.progress.com/s/article/does-pasoe-support-authentication-and-authorization-with-azure-ad
• https://docs.progress.com/bundle/pas-for-openedge-management/page/About-Active-Directory-user-accounts.html
• https://docs.progress.com/bundle/openedge-authentication-gateway-128/page/Learn-about-OpenEdge-Authentication-Gateway.html

OpenEdge 13.0 introduces user-defined generics as a key feature that significantly enhances compile-time safety for developers. It provides these compile-time safety benefits:

• Improved compile-time type checking: the type system can validate type correctness during compilation rather than at runtime
• Reduced duplicate class definitions: developers can write more reusable code with proper type constraints
• Lower technical debt in large ABL codebases: promotes better code organization and maintainability

Learn more: https://www.progress.com/blogs/openedge-13.0-what-this-innovation-release-really-delivers

Additional type-safety improvements:

While not exclusively compile-time features, OpenEdge 13.0 includes other enhancements that support safer code development:

• Scientific notation support with existing data types (INTEGER, INT64, DECIMAL) while maintaining existing limits such as the 50-digit DECIMAL precision.
• Enhanced ABL cryptography functions with stricter error handling that prevents weak algorithms from being used, making it easier to detect and correct insecure configurations at the code level

These features work together to help developers catch potential issues earlier in the development cycle, reducing runtime errors and improving overall code quality and security.

You would use the official Progress OpenEdge MCP Server instead of writing a custom MCP implementation inside a PAS for OpenEdge Web Handler because the dedicated server acts as a ready-made architectural bridge, security gateway, and protocol translator. Building it yourself forces your ABL business logic layer to handle complex AI orchestration tasks it was not designed for. Read more: https://docs.progress.com/bundle/openedge-mcp-server/page/OpenEdge-MCP-Server-in-the-AI-ecosystem.html

The OpenEdge MCP Server removes that barrier by securely transforming your existing APIs into AI-ready operations in hours, not months. Learn more: https://www.progress.com/openedge/mcp-server

To improve security and overall performance, the PAS for OpenEdge and database images on Docker Hub now use the latest Red Hat Universal Base Images (UBI 9) minimal operating system instead of CentOS Linux 7.5. This change enables you to run OpenEdge applications on the latest operating system platform supported by Red Hat.

For more information on Docker images, see Contents of a PAS for OpenEdge Docker image.

.NET 8 is now certified to work with OpenEdge 13.0 for both ABL applications and .NET Open Client applications. This certification ensures that ABL and .NET Open Client applications that upgrade to .NET 8 can take advantage of .NET 8 features and remain on a supported version of .NET.

OpenEdge 12 retired the Classic AppServer (CAS) completely. For PAS for OpenEdgem it's not just a new version of the application server—it is a replacement technology with a different architecture and licensing model.

Because CAS was fully deprecated starting with the OpenEdge 12 series, organizations were required to move from CAS to PAS for OpenEdge, which is why an additional cost was required.

However, OpenEdge 13 continues with the same PAS for OpenEdge-based architecture. There is no new required server replacement comparable to the CAS-to-PAS for OpenEdge migration. If you already licensed PAS for OpenEdge in OpenEdge 12, you can continue using that model. If you do not have PAS for OpenEdge and want to use it in OpenEdge 13, you still need to purchase it.

Yes, the Progress Agentic RAG solution is a separate, licensed product. It is not included in the OpenEdge platform and is delivered primarily as a subscription-based SaaS offering.

Please refer to the following URL for pricing information: https://www.progress.com/agentic-rag/pricing

We can suggest the appropriate license edition once we understand your use case and requirements. Please feel free to contact us for further discussion at progress-api-marketing@progress.com.

Progress does not publish a specific percentage, but like most enterprise software vendors, it uses AI as a developer productivity assistant—not as an autonomous code author. AI assists developers in OpenEdge development, however it does not replace them. All production code in the OpenEdge platform is still designed, reviewed, and validated by experienced engineers.