Progress ObjectStore ®
Progress OpenEdge ®
F E AT U R E H I G H L I G H T S
Progress Orbacus ®
Progress Orbix ®
Progress Savvion ®
Progress Sonic ®
BUILD DYNAMIC, BUSINESS PROCESS-CENTRIC APPLICATIONS FOR SECURE DEPLOYMENT ACROSS ANY PLATFORM, ANY MOBILE DEVICE, AND ANY CLOUD Are your customers and end users demanding applications that can adapt to their changing needs, such as support for mobile devices, constantly evolving business processes, and deployment in the Cloud? At Progress Software, we have always prided ourselves in our ability to simplify the job of creating and operating the world’s best business applications. In order to survive and thrive in today’s world of quickly evolving markets and technologies, you must be able to respond quickly while coping with strict budgets and tight timeframes. If you can deliver rapidly customized applications with minimum disruption to business and IT systems, you will be successful. With OpenEdge 11, you can develop dynamic solutions that incorporate business process and integration capabilities securely across multiple platforms and devices. Whether you deploy on-premise, on a mobile device, or in the Cloud, OpenEdge 11 offers a single integrated development platform that is 40% more
K EY F E ATU R E S OpenEdge 11 enables our customers and partners to deliver Responsive Business Applications through new enhancements that offer: >> Mobile Development & Deployment >> Multi-Tenancy >> Increased Productivity >> Improved Operational Excellence >> Enhanced Integration & Workflow >> Increased Security & Compliance >> Improved Personalization >> Greater User Interface Flexibility
productive and provides a 30% cost savings versus the competition. With OpenEdge, we help you growâ€”faster! OpenEdge 11 delivers new enhancements and benefits for enabling our customers and partners to deliver Responsive Business Applications: >
Mobile Development & Deployment
Integration & Workflow
Security & Compliance
User Interface Flexibility
MOBILE DEVELOPMENT & DEPLOYMENT OpenEdge Mobile provides the ability to quickly and easily extend existing OpenEdge applications to support multiple mobile devices on various
platforms or to build new mobile apps for new business areas or new markets. Having an easy mobile app development environment tightly integrated with the familiar OpenEdge environment makes it quick and easy to develop and deploy mobile apps. Mobile apps have the power to make operations more efficient and businesses more competitive. With OpenEdge 11.2, application developers can take advantage of a new Mobile application builder and visual designer that enables Progress Developer Studio for OpenEdge to produce feature-rich Mobile applications for the iOS and Android platforms. With a â€œwrite once, deploy anywhereâ€? approach, OpenEdge 11.2 removes the need to learn device-specific languages or development environments, while enabling the creation of full-featured applications that can access all of the most important device capabilities, such as the camera, GPS, and microphone. The REST adapter, also introduced in OpenEdge 11.2, provides the Mobile clientâ€™s access to the OpenEdge AppServer, while ProDataSet and Temp-table support are built in using JSDO data-binding and form-based Business Entity support.
MULTI-TENANCY A multi-tenant database is one which provides database support to a number of separate and distinct groups of users, also referred to as tenants. Multi-tenant applications have taken an increasing foothold in the database marketplace, largely due to the emergence of SaaS as a deployment strategy. For the SaaS application provider, a multi-tenant deployment strategy provides many benefits, especially when a Shared Tenancy approach is used. Management of the deployment can take place either at the overall application or database level, or based on tenant and user. Operational complexity is greatly reduced due to the number of shared resources and because only one instance of the application and database is involved. With OpenEdge 11, developing and deploying multi-tenant applications is transformed by using an approach that is unique in the industry, reducing and even eliminating the challenges typically presented when implementing a Shared Tenancy application. This is due to two major factors: Tenant support is implemented in the database layer, and Database utilities and tools are also tenant-aware.
The significant advantage of the first point is that the application no longer has to manage tenancy—simplifying the code and making tenancy completely transparent. For the second point, the operational aspects of the database are also capable of acting in a mode that is either tenant-specific or database-specific. This streamlines key functions such as index maintenance, data dump and load, object moves, and other database functions. DATABASE MULTI-TENANCY 1. Multi-tenant Database Tables A key addition to the OpenEdge database is built-in support for multiple tenants within a single database. Many database vendors are promoting multi-tenancy as a new capability for SaaS and Cloud. But with OpenEdge, the unique difference is that instead of the client managing access to tenant data, the database takes care of everything. This means that minimal changes are required for application code; in fact, tenants run the exact same r-code, and utilize the exact same schema definition, as users of a non-multi-tenant instance of the same application! Furthermore, each tenant’s data is stored in database partitions that are physically separate from those of other tenants, enhancing data access and making database maintenance easier and more efficient. 2. Web-based Multi-tenant Tooling as an extension of OpenEdge Explorer and OpenEdge Management OpenEdge 11 includes the Web-based Database Administration Console as an extension of OpenEdge Explorer and OpenEdge Management. This new interface for managing tenants—including tenant users, tenant storage, and tenant security—features a brand new look and feel. A template-based approach provides for increased productivity, and the tool can also generate ABL code that developers can re-purpose in scripts or ABL applications. 3. ABL APIs for multi-tenancy An extensive set of ABL APIs for multi-tenancy allows application developers to integrate tenant management into their own applications, for example to provide the capability for tenants to provision themselves, or to build multi-tenant management tools that are more customized to your development and deployment needs. www.progress.com
4. SQL DDL support for multi-tenancy SQL has been enhanced to multi-tenancy, allowing application tenants to enjoy equivalent functionality with both ABL and SQL. *New database multi-tenancy functionality for OpenEdge 11.1 includes: 5. Multi-tenant Governor for users per tenant With OpenEdge 11.1, it is possible to limit the number of users (-n) that an individual tenant is able to connect to a multi-tenant database. 6. Multi-tenant Governor for record locks per tenant This governor, available starting in OpenEdge 11.1, limits the number of record locks (-L) available to a particular tenant at one time. 7. Enhanced multi-tenant tooling in the OpenEdge Explorer Data Administration Console OpenEdge 11.1 introduces several new capabilities to OpenEdge Explorerâ€™s Data Administration Console, making it easier to manage tenants. Included are the ability to rename tenants, tenant groups, and/or tenant domains; the ability to dump and load tenant data; and an improved user interface for filtering and batching large datasets. Tenant partition management is also made much easier with the addition of drag-and-drop support. In addition, OpenEdge Explorer includes the ability to manage the new multi-tenant governors. 8. SQL support for Tenant Groups OpenEdge 11.1 includes functionality that enables SQL to work with tenant groups in terms of data definition, data management, and data access. 9. Super-tenant SQL access to LOB data Starting with OpenEdge 11.1, the super-tenant is able to access tenant LOB data.
PRODUCTIVITY OpenEdge 11 continues to focus on improving productivity so you can spend more time working in ways that will add value to your business. From Progress Developer Studio for OpenEdge and ABL to the DataServers
and user interface, critical productivity enhancements have been made to help you keep up with rapidly changing customer and business demands. OpenEdge 11 is more flexible than ever, offering support for new platforms and programming models, and providing new development options. In direct response to customer requests, changes have been made to improve the usability of the system, the ability to troubleshoot, and the ability to manage and extend your .Net interface. And OpenEdge 11 provides even greater support for SaaS and Cloud application development with increased user interface flexibility that delivers a dynamic web experience that is rich, engaging, and interactive. PROGRESS DEVELOPER STUDIO FOR OPENEDGE (FORMERLY KNOWN AS OPENEDGE ARCHITECT) 1. Usability enhancements OpenEdge 11 includes several usability enhancements to Developer Studio for OpenEdge based upon customer requests and research into customer issues. Included are improvements to the ProBindingSource designer, the handling of preprocessors, and the Build and Compile functions. 2. Support for WebSpeed programming models The evolution of Developer Studio for OpenEdge as a comprehensive development environment for OpenEdge applications continues with the addition of support for WebSpeed programming models; included are CGI Wrappers and Embedded SpeedScript. 3. Remote server development for AppServer and WebSpeed One of the hallmarks of the OpenEdge platform is how it facilitates multi-tiered application design and development. In OpenEdge 11, Developer Studio for OpenEdge adds support for building AppServer and WebSpeed application components. Debugger support for AppServer and WebSpeed is included. 4. Remote Debugger and other Debugger enhancements OpenEdge 11 allows the Debugger to connect to an already-running AVM (local or remote) and debug the executable with full capabilities. In addition, the Debugger has been enhanced to support breakpoints in â€œincludeâ€?
files, the ability to step into code on a remote AVM from a local debug session, and the ability to debug without the need for debug listing files. Security of a debug session over a remote connection has also improved. *New Progress Developer Studio for OpenEdge functionality for OpenEdge 11.1 includes: 5. Debug listing support Beginning in OpenEdge 11.1, while debugging an application it will be possible to go directly to the source code line number rather than the debug listing line number given by the Debugger. 6. Ability to open files from the commend line or by double-clicking With OpenEdge 11.1 application developers can open a file within Progress Developer Studio from the command line or by double-clicking on the ABL file. 7. Certification of Eclipse 3.7.1. 8. Update DB Navigatorâ€™s JDBC drivers to Version 5.0 DataDirect JDBC drivers *New Progress Developer Studio for OpenEdge functionality for OpenEdge 11.2 includes: 9. ABL Scratch Editor. The new Scratch Editor in Progress Developer Studio provides the ability to write and execute ABL code without having to save it as a project. Features in the Scratch Editor include content assist, color-coding, and syntax-checking.
10. AppBuilder Integration.
OpenEdge 11.2 provides improved integration of Progress Developr Studio and the AppBuilder by significantly improving usability and providing more screen real estate to ABL developers wanting to develop and maintain ABL-based applications. Included is integration of the AppBuilder design window and tools along with enhancements to Progress Developer Studioâ€™s text editor which make it easier to work with AppBuilder-generated code. Now itâ€™s easier than ever to build and maintain ABL-based applications in the Eclipse environment. ABL (ADVANCED BUSINESS LANGUAGE) 1. Unified r-code for portability between 32-bit and 64-bit systems OpenEdge 11 features complete r-code compatibility between 32-bit and 64-bit platforms, providing for more efficient development and deployment.
2. Object-oriented language extensions (interface inheritance and dynamic properties) Interface Inheritance allows a developer to create class interfaces that inherit from existing interfaces. OpenEdge 11 also introduces the ability of OOABL interfaces to extend .NET interfaces. Dynamic Properties allow a developer to set and get an ABL class property dynamically. 3. Improved ProDataSet to XML support With OpenEdge 11, additional XML documents that conform to the structure of a ProDataSet can be read into a ProDataSet. 4. Logging of temp-table information The OpenEdge Logging Infrastructure has been enhanced so that application developers can trace the creation and deletion of temp-tables in their applications. This logging capability strengthens the ability to troubleshoot applications that utilize temp-tables and ProDataSets as their primary data structures. 5. Virtual System Tables for temp-tables This ABL enhancement allows clients to gather information about the temp-tables used by the application via Virtual System Tables (VSTs). These tables give the application access to database activity and status information, enabling an application to understand, debug, and tune the use of temp-tables within their application at runtime. 6. Improved support for large objects OpenEdge 11 removes several large-object restrictions that have existed in previous releases. The BUFFER objectâ€™s SAVE-ROW-CHANGES( ) and BUFFER-COMPARE( ) methods, and the BUFFER-COMPARE statement, now allow CLOB fields to be compared. Additionally, when used on records that contain LOB fields, the CURRENT-CHANGED( ) function now can detect when a LOB field has been altered. The ABL also supports the comparing of LOB fields. One benefit of this change is that programs using GUI for .NET may now include LOBs in updateable grids.
7. ProBindingSource improvements Prior to OpenEdge 11, for a grid control that supports a hierarchy of tables (thereby allowing you to bind to a ProDataSet), you had to rely upon the grid to do any sorting of the child tables. In OpenEdge 11 the application can now change the Data-Relation’s WHERE-STRING attribute if the corresponding ProDataSet is bound to a .NET BindingSource. 8. Allow input- blocking statements anywhere OpenEdge 11 removes all restrictions on where an input-blocking statement can occur, providing more flexibility when using user-defined functions, OOABL non-void methods, and elsewhere. 9. ABL performance enhancements Analyzing and improving the performance of ABL is an ongoing task for OpenEdge. In OpenEdge 11 some of the key performance benefits include faster deletion of tables in Type II storage, as well as others. For example, in OpenEdge 11, the AVM delays the instantiation of temp-tables, ProDataSets and their associated indexes until the object is used in the program. This change improves procedure-and class-instantiation performance. Additionally, ABL “FOR EACH” blocks include a new TABLE-SCAN option, which improves performance when a program is reading all of the records stored in a Type II storage area. *New ABL functionality for OpenEdge 11.1 includes: 10. Encoded password support A frequent regulatory requirement, in OpenEdge 11.1 administrators are provided with a single means of creating, storing, and using encoded passwords in an OpenEdge application. 11. LIKE phrase for method and function parameters Beginning with OpenEdge 11.1, the LIKE phrase is supported in Method and Function parameter syntax.
*New ABL functionality for OpenEdge 11.2 includes: 12. Session-level support for Structured Error Handling. Prior to OpenEdge 11.2, Structured Error Handling worked only at the routine level (procedures, functions, methods, and “ON” triggers). OpenEdge 11.2 introduces a new statement and new startup parameter that allow an ABL programmer to utilize the UNDO/THROW ERROR directive within all blocks in a source file. 13. Sub-second capability for the PAUSE statement. Previously, the PAUSE statement had a minimum value of one second. In OpenEdge 11.2 the PAUSE statement can now be use with sub-second timing. 14. “DefaultScrolling” startup option. A new -defaultscrolling startup option causes DEFINE QUERY statements to default to SCROLLING, guaranteeing the possibility of pre-fetching when resolving an ABL query over a network. 15. Offset and fetch for SQL query result sets. When processing the result set from a SQL query, instead of having to load the entire result set to process it, OpenEdge 11.2 allows an application query to define an offset within the result set and fetch a limited number of rows at the offset. This direct access to only a piece of the result set can lead to faster query execution and may better suit the needs of applications where an entire result set is unnecessary. DATASERVER 1. MS SQL Server DataServer CLOB support OpenEdge 11 adds support for the OpenEdge CLOB datatype to the DataServer for MS SQL Server, allowing a CLOB field in OpenEdge to be migrated and pulled against MS SQL Server. *New DataServer functionality for OpenEdge 11.1 includes: 2. Update to Version 7.0 of Progress DataDirect Connect and Connect64 for ODBC drivers OpenEdge 11.1 embeds Progress DataDirect’s 32-bit and 64-bit Version 7.0 drivers for ODBC DataServers.
USER INTERFACE 1. Improvements to ProBindingSource at design time and support for recursive relations Usability issues with ProBindingSource are addressed in OpenEdge 11, including the removal of multiple modal dialogs for schema selection. ProBindingSource also can now define recursive relationships amongst tables, which was previously possible only by coding the ABL directly. 2. JSON Parser OpenEdge 11 introduces a package of built-in ABL objects to represent JSON. These objects can be created by parsing JSON, and JSON can be created by serializing these objects. This will allow applications to work directly with JSON using ABL rather than having to parse the DOM structure themselves, a capability that particularly benefits programs that take advantage of AJAX and Web UI programming. 3. .NET Open Client changes The .NET Open Client adds an additional way of supporting NULL data values by supporting nullable value types, which are essentially structures that can represent the normal range of values for its underlying type, plus an additional null value. DIAGNOSTICS *New Diagnistics functionality for OpenEdge 11.2 includes: 1. PROVERSION enhancement. The PROVERSION statement can now report Service Pack, patch level, and build number information in addition to the main version of the installed product. 2. ProInventory included with the OpenEdge product distribution. Beginning with OpenEdge 11.2, installations of OpenEdge will automatically include the ProInventory diagnostic utility. ProInventory is often used by Progress Customer Support to obtain comprehensive system information from customers.
PLATFORM SUPPORT 64-bit SQL drivers for Linux Integrating 64-bit SQL drivers for 64-bit Linux platforms completes the work to provide 32-bit SQL drivers for 32-bit platforms and 64-bit SQL drivers for 64-bit platforms, across the board. *New Platform support for OpenEdge 11.2 includes: OpenEdge 11.2 introduces support for Eclipse 3.7. It is also certified for Microsoft Windows 8 and Microsoft Windows Server 2012.
OPERATIONAL EXCELLENCE OpenEdge 11 continues to focus on supporting the development of high-performance and ultra-reliable applications to support the needs of 24x7 business operations with ever-increasing numbers of users. Across the boardâ€”the AppServer, the database, the DataServers, and moreâ€”critical performance enhancements have been made to ensure that your application matches aggressive business demands. Diagnostic and monitoring tools have been improved and enhanced to provide a more proactive environment for troubleshooting issues. Additionally, special considerations have been made to facilitate deployments to the Cloud where performance and reliability are paramount. APPSERVER 1. Improved AppServer error handling Improvements to AppServer error handling provide better information regarding the type of error that has resulted and where it has occurred. Included is better handling of the error condition when an AppServer connection has been refused as well as the error when there are no ports available to allocate to an agent. 2. Diagnostics to determine which AppServer code is running Further improvements to AppServer diagnostics include the ability to determine which specific r-code is running, allowing verification of whether the agent is actually hung or is just running for a very long time.
3. Network compression for state-free AppServer mode, Java OpenClient, and .NET OpenClient Message compression improves application performance on a network. In OpenEdge 11, AppServer messages are compressed when operating in state-free mode and communicating with any client. This completes compression work for all modes of the AppServer. In addition, the Java and .NET OpenClient include compression as well. *New AppServer functionality for OpenEdge 11.1 includes: 4. TCP Keepalive properties for the .NET OpenClient In OpenEdge 11.1 the .NET OpenClient supports runtime properties that allow direct control of the TCP socketâ€™s Keepalive messages, allowing applications to adapt to the needs of the network that the application is operating within. *New AppServer functionality for OpenEdge 11.2 includes: 5. REST Adapter The OpenEdge 11.2 REST Adapter leverages the power of XML to give your application the ability to integrate with any other application, written in any language and on any platform. This provides access to the AppServer by any client built outside of OpenEdge and opens up your application to a world of unlimited connectivity, to any app on any platform. 6. Improved AppServer Performance OpenEdge 11.2 improves AppServer performance for single-run and singleton persistent procedures. Operations that previously required multiple round trips from the client to the AppServer are now accomplished with just one round trip.Single-run procedures apply to the frequent case where an application needs to run a persistent procedure just one time. The Single Run combines the three separate calls for Create, Run, and Delete of the procedure into a single call that executes them all together, resulting in just one round-trip where previously three were necessary. For Singleton procedures, the persistent procedure is instantiated only if it is not already running from a previous invocation, and remains instantiated after each run.
OPENEDGE MANAGEMENT Support for remote jobs Administrators can now use OpenEdge Management as a central console to manage jobs on remote systems in addition to the local system. The ability to manage scripts that reside on remote machines is also included. DATASERVER MS SQL Server DataServer dynamic query join optimization When using a large array of table join conditions with MS SQL Server DataServer, OpenEdge 11 shows performance improvements by reducing the number of round trips to the foreign database server and/or by pushing as much of the processing as possible to the MS SQL Server database. DATABASE *New Database functionality for OpenEdge 11.1 includes: 1. Improved performance of Index Rebuild The performance of index rebuild operations is significantly enhanced in OpenEdge 11.1 with the addition of new parameters to use when starting an idxbuild. While the exact benefits will depend on the particular database and index configuration, DBAs can expect performance improvements of three times faster, or even more. 2. New startup parameters to tune network performance In OpenEdge 11.1, five new startup parameters have been introduced that can be used to tune network performance when using prefetch queries. Especially beneficial to large databases, the new parameters affect when and how data is sent across the network when executing a prefetch query. 3. New startup parameters to reduce contention when updating the LRU (least recently used) chain This enhancement to OpenEdge 11.1 provides a way to set a skip value that governs the number of times that a buffer will be accessed before it is moved to the end of the LRU chain. When this LRU skip value is set properly it reduces contention on the LRU latch, improving concurrency and performance.
*New Database functionality for OpenEdge 11.2 includes: 4. Support for enabling JTA (Java Transaction API) along with OpenEdge Replication With OpenEdge 11.2 you are able to incorporate disaster recovery into your distributed transaction solution by running OpenEdge Replication and JTA at the same time on the same database.
INTEGRATION AND WORKFLOW To remain competitive, it is vital companies have the agility to meet ever-changing customer and market demands. This level of agility requires flexible business applications—both in terms of process and integration. The days of making code changes every time a business process is defined or refined, or whenever a customer has unique requirements, are gone. Companies need the ability to support the fast pace of business by quickly and efficiently incorporating those new processes and capabilities into their new and existing applications. And those applications need to be adaptable enough to integrate easily with other applications—now and in the future. OpenEdge 11 delivers additional integration flexibility as well as Business Process Management (BPM)—a new feature set integrated into the OpenEdge development environment. Progress customers and partners now have a simple way to modernize existing applications with OpenEdge BPM in addition to building new and add-on business process applications. With BPM, OpenEdge developers can add process workflow into their OpenEdge applications in a natural and intuitive manner—while also reducing development costs and delivering greater business value to their customers. INTEGRATION Sonic 8.0 support for Sonic adapter The Sonic adapter for OpenEdge supports the Version 8.0 release from Sonic.
WORKFLOW OpenEdge BPM From the eclipse-based Progress Developer Studio for OpenEdge development environment, developers can: >>
Define how process steps execute OpenEdge business logic via the OpenEdge Application Server through a purposed managed adapter, and an intuitive “drag and drop” of ABL procedure code onto the workflow design canvas
Pass native OpenEdge data types from process step to process step through an enhanced dataslot capability
Have access to a new set of process-related ABL APIs to carry out a variety of standard BPM functions, such as obtain the task information for a user to display in the application User Interface, inform the BPM processing engine that a process step is now completed, and so on
Simplify the use of existing WebSpeed Forms in business process flows
*New OpenEdge BPM functionality for OpenEdge 11.1 includes: 1. Character extent support in the ABL API In OpenEdge 11.1, it is possible to set and retrieve a List dataslot value using an ABL Progress.BPM.DataSlot or DataSlotTemplate. 2. Get*Tasks method to support advanced filtering Beginning with OpenEdge 11.1, a new method is available in the UserSession object to support advanced filtering of the Task objects that are obtained.
SECURITY & COMPLIANCE OpenEdge 11 reinforces our commitment to our customers’ needs for security, privacy and compliance. In this era of increased regulatory requirements, data must be secure and private in order to protect intellectual property, maximize business success, and prevent liability. The stakes are even higher in a SaaS or Cloud environment, where security and compliance www.progress.com
are vital for customer trust and market success. Customers adopting SaaSand Cloud-based applications expect the same assurances of data security and compliance that they have long expected from applications that run on-premises in their own data centers. OpenEdge 11 includes enhancements that improve and simplify identity management. And essential updates and support for new encryption methods significantly improve performance and ensure you keep pace with current industry regulations. SECURITY 1. Improved identity management OpenEdge 11 introduces the following improvements to identity management: >>
A simplified process for creating and using user credentials for both client-server and Application Server OpenEdge applications
A single programming model for configuring any combination of runtime security features at production time, requiring few, if any, changes to the application code
Support for multiple tenants with one or more domains per tenant.
Support for the configuration per-tenant of user authentication methods that meet the tenantâ€™s specific security requirements
A simplified way for using SQL Server together with ABL in the same OpenEdge application without having to rely on the security standards of the _user table accounts
2. RC4 for ENCRYPT( ) and DECRYPT( ) Supporting RC4 encryption for the ENCRYPT( ) and DECRYPT( ) functions significantly enhances the performance of these functions. 3. SHA-256 and SHA-512 An upgrade to SHA-256 and SHA-512 hashing algorithms is essential to keep current with recommendations by security organizations, standards councils, and government authorities.
4. More SSL certificate support Upgrading to version 220.127.116.11 allows OpenEdge to take advantage of AES data encryption ciphers and x509 version 3 extensions support available in the newer release. *New security functionality for OpenEdge 11.1 includes: 5. ABL-based username/password authentication with Client-Principal This OpenEdge 11.1 feature aids user authentication by allowing application developers to use a single code path regardless of how and where the physical authentication actually takes place. OpenEdge Management support for this capability is also included.
PERSONALIZATION Improved personalization options within OpenEdge 11 increase the productivity associated with installing, uninstalling and upgrading your OpenEdge application. Users can take advantage of new personalizatiion options for simplifying and accelerating the install process as well as automating the upgrade process. 1. Install “Finish” button To streamline the installation process, a new option has been provided on each dialog that allows the user to finish the data collection phase of an installation. The user will still be able to navigate through each dialog if desired, but they will be brought directly to the summary screen when they choose to finish data collection. The summary screen will display all of the user’s selections and for all skipped dialogs the default values will be used. 2. Option to uninstall WebClient When installing the WebClient, the install program now determines whether previous installations of WebClient already exist and provides a list to the user so that any or all may be uninstalled. The uninstall will complete prior to beginning the new install.
3. Option to suppress WebClient dialog-box when upgrading This feature provides an optional override of the dialog-box presented to the user by the WebClient when it detects that an application has changed and needs to be upgraded. User confirmation of the upgrade is bypassed and the upgrade begins automatically.
USER INTERFACE FLEXIBILITY Today, the market demand is high for web applications that have many of the qualities and characteristics of desktop applications but are delivered over the web. OpenEdge 11 now offers greater user interface flexibility with support for Enhanced Rich Internet Applications (RIAs). RIAs combine the flexibility, responsiveness, and ease of use of desktop applications with the broad reach of the web. RIAs provide a dynamic web experience that is rich and engaging, as well as interactive. RIA technologies provide a variety of development, deployment, and runtime options for SaaSbased applications. Due to the flexibility of the platform, OpenEdge already supports many different RIA technologies. Since no RIA technology has taken the lead, OpenEdge 11 will provide support for many additional options, more specifically: JSON parser support in the ABL, updated Infragistics controls (GUI for .NET), and architect support for custom project types (Ajax/ WebSpeed). USER INTERFACE 1. Updated Infragistics controls OpenEdge 11 includes an update to the current release of the Infragistics Net Advantage WinForm Controls, providing enhanced functionality as well as bug fixes. 2. Allow the use of .NET objects for non-GUI In OpenEdge 11, .NET objects that are not related to UI can now be used. Also, ABL access to .NET objects is now allowed in non-user-interface executables. This means that AppServer agents, WebSpeed agents, batch jobs, and the character client can now work with .NET objects.
Progress Software Corporation (NASDAQ: PRGS) is a global software company that simplifies the development, deployment and management of business applications on-premise or on any Cloud, on any platform and on any device with minimal IT complexity and low total cost of ownership. WORLDWIDE HEADQUARTERS
Progress Software Corporation, 14 Oak Park, Bedford, MA 01730 USA Tel: +1 781 280-4000 Fax: +1 781 280-4095 On the Web at: www.progress.com Find us on
For regional international office locations and contact information, please go to www.progress.com/worldwide Progress and OpenEdge are trademarks or registered trademarks of Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and other countries. Any other marks contained herein may be trademarks of their respective owners. Specifications subject to change without notice. ÂŠ 2013 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved. Rev. 01/13 | 130121-0091
Published on Apr 4, 2013