Progress Rollbase Release Notes Date: May, 2014 -------------------------------- Copyright (c) 2014 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved. ====================== Release 2.2.2 Hotfix ====================== This Hotfix resolves the following 2.2 known issues: 1. There is an issue with the update_2.2.0.sql script when running on the OpenEdge database. To correct it, edit the script as follows: DROP TABLE IF EXISTS RB_HELP to be DROP TABLE RB_HELP; *[FIXED in 2.2.2]* 13. Objects added to an existing application created using the Quick Create wizard may cause previous object definitions to be shown as dependent versus core objects. As a work around when viewing the overall Application definition, move the objects as appropriate using the 'Attach Object' functionality of the core and dependent objects view. Meanwhile, this will be addressed in the next release. *[FIXED n 2.2.2]* In addition, these customer reported issues have been resolved in this Hotfix: Fixed in 2.2.2 Hotfix: ====================== Case# 00275008 - There is currently no way to access the original file name of a document associated with an Object. The current logic will result in FileUpload.toString() to obtain the value which returns the actual storage name.The {!file#html} and {!file} tokens do not return the name of an uploaded file in a trigger, but the temporary/internal filename. Case# 00273502 - In record creation popup, fields: First Name, last Name, Profession and Location are mandatory fields and for which respective error messages should be displayed if not filled. Last Name field, when left blank and record is saved, it does not show the required error message. Case# 00273502 - In record edit page, if for a field, the record is already selected, the option of creating a new record is missing even when the existing record is deleted. After removing the selected record on field, saving and then re-editing the same record, the record creation option (+ button is available). Case# 00270486 - Activity Trail Report not working Case# 00271749 - "File Upload" field is visible on the public Web if its object is viewable by the Portal Visitor role Case# 00275211 - "Treat empty spreadsheet cells as NULL values for updated records" also empties non mapped fields ====================== Release 2.2.1 Hotfix ====================== This Hotfix resolves the following 2.2 known issue: 2. There are three options for deployment of Rollbase Mobile app – Web App, iOS App and Android app. All these three options have been documented in Rollbase mobile documentation. However for this release, only native deployments are available (iOS and Android). The option to deploy Rollbase mobile as a Web application is not available for the current release. [FIXED] The "Deploy" button is now available. ===================== Release 2.2 ===================== --------------------------- ENHANCEMENTS in Release 2.2 --------------------------- 1. Improved User Experience -- The Getting Started page makes it easier to dive right in. The Quick Create wizard guides users to rapid success in making new apps. The user has more streamlined access to launching tasks, videos, and other materials. The layout of Rollbase screens is more readable, and buttons are clearly distinguished. Existing Rollbase users need to update their Rollbase application from the Application Directory to expose the new home page. 2. New Metadata APIs -- Rollbase now offers AJAX, REST, and SOAP methods for creating, modifying, accessing, and deleting applications and their components. 3. More Rollbase Mobile Capabilities -- There are now two styles of mobile apps. The features available for development of mobile apps depend on the developer's license. Mobile-Web - The former "Mobile Edition" is now "Mobile-Web". It is enabled per-application. Specified application views are exposed to users, but you cannot change the look and feel of the mobile app. User login to a known URL with a mobile device redirects to the corresponding Mobile-Web application. Rollbase Mobile – This style supports multiple mobile apps per Rollbase application. Apps are created through the Mobile App Builder's drag-n-drop tools. Rollbase Mobile separates data access from business logic, so you can add functionality beyond the Rollbase application. These apps can be deployed as both native and browser-based apps. 4. Documentation Enhancements -- Rollbase's online documentation is now organized by categories that lead the reader through the development process. The Reference section also presents the API by categories. Access to this online documentation is located at http://documentation.progress.com/output/Rollbase. ---------------------- CHANGES in Release 2.2 ---------------------- Some changes in Rollbase behavior might require changes to existing applications: 1. Change to JSON Date Format -- The getDataField, selectQuery, and selectValue REST methods now return dates in the correct JSON format. A new parameter, useLegacyDateFormat, has been added to these methods to control the data format. This URL parameter is optional and only applies to JSON output of DATE fields. When set to false or not specified, dates are returned in the normal JSON format, such as: "Wed Mar 05 17:52:38 IST 2014". When set to true, dates are returned in a format like this example: new Date("Wed Mar 05 2014 17:52:38 (IST)"). 2. Change to Portal CSS -- Rollbase includes a new Pacific portal CSS. New portals created in the 2.2 release use this CSS by default. You can update earlier applications by adding the body tag "class=pacific-bootstrap" to a portal's Header and Footer: Header HTML section. 3. Fix to Triggers might Change Application Behavior -- The resolution of PSC00279507 enables the checkCondition parameter of the rbf_runTrigger method. If your applications depend on the former behavior(where the condition was not tested), you might need to change the logic that invokes this method. -------------------- FIXED in Release 2.2 -------------------- Case# 00269062 - Fusion Chart not working on a portal with the "Record Creator" role Case# 00269062 - Fusion Chart not working on a portal when filtering by CURR_VISITOR Case# 00270107 - LOOP_BEGIN and rbf_getPage() do not work with the Record Creator role Case# 00269881 - An encrypted field cannot be blanked once it has a value Case# 00266417 - User in any role able to change Administrator password and other details Case# 00267157 - Custom password validation does not work when resetting password Case# 00264618 - Relationships not deleted when the Recycle Bin delete records Case# 00266766 Case# 00264584 - "Record Creator" role does not work with the Ajax API Case# 00264994 - Email Address case sensitivity for Forgot Password page Case# 00264584 - AJAX API should not be used by anonymous HTTP client Case# 00264584 - The Portal Visitor role has by default too much permission Case# 00262720 - PDF Template mention "Evaluation" on the Public Cloud Case# 00263181 - rbf_updateRecord() is changing the locationId even when it is not part of the list of fields to be updated Case# 00261704 - Cannot deploy application Case# 00263403 - Administration Setting Case# 00263187 - Support Menu Option Case# 00262271 - Proper usage of DataObjectHandler.getByQuery Case# 00262941 - Workflow actions can be performed on records a user does not have access to Case# 00263086 - Merging two records does not preserve the relationships of their respective related records Case# 00262205 - Audit trail from a record updated through a portal sometimes have no user Case# 00262046 - Update field trigger not working when a record gets created through a SOAP call Case# 00261782 - Some users cannot log out of Rollbase Hosted Cloud Case# 00262571 Case# 00261127 - When an email template is evaluated by an email trigger, the 00269935 {!name#link} token gets translated to https://www.rollbase.com/workflow/m/main.jsp instead of https://www.rollbase.com/prod3/m/main.jsp If the trigger is immediate it does not happen. Case# 00261707 - Triggers on COMMLOG object not working when email is sent 00262864 --------------------------- KNOWN ISSUES in Release 2.2 --------------------------- 1. There is an issue with the update_2.2.0.sql script when running on the OpenEdge database. To correct it, edit the script as follows: DROP TABLE IF EXISTS RB_HELP to be DROP TABLE RB_HELP; 2. There are three options for deployment of Rollbase Mobile app – Web App, iOS App and Android app. All these three options have been documented in Rollbase mobile documentation. However for this release, only native deployments are available (iOS and Android). The option to deploy Rollbase mobile as a Web application is not available for the current release. [FIXED - May 2014] 3. Cannot use the Mozilla browser to develop mobile applications using the Rollbase Mobile App Builder because the login to session-enable app from Mozilla is prevented. Instead, use IE, Chrome, or Safari browsers. 4. Cannot use Refresh button in Test window to view latest data: the Refresh operation in Mobile Emulator does not update data from Rollbase. Instead, refresh the browser and re-login. 5. When opening a mobile app in a new tab, it opens the Mobile App Builder home page instead of an actual application's designer 6. When performing a backup of a Rollbase project, it does not backup Rollbase Mobile App Builder specific content. So, manually backup your Mobile projects from the Mobile App Builder. 7. The footer bar hangs somewhere in the middle of the screen, after the on-screen keyboard appears and disappears again when entering an input field. 8. Because of an issue with our use of JQM 1.3.2, a Popup cannot be closed when a YouTube component has been added 9. Data transfer using scp hangs part way through the process. This can result in an .ipa build never completing. If so, try again or use a local Mac machine. Meanwhile, we are currently working the issue with Apple. 10. When using an OpenEdge service or DataDirect Cloud object, you cannot update, delete, or use any filter operations against an object's data in the Rollbase Mobile App Builder. So, you must replicate the same objects in the Rollbase environment. 11. When you create, update, or delete a record and use triggers to validate the record data in After Create or Before/After Update/Delete, a failure is not reported back to the Mobile App if the validation fails. 12. For this release, avoid using the Quick Create Wizard if you plan to use mobile functionality. Mobile applications derived from an application created with the Quick Create Wizard may report an error when retrieving the application catalog. 13. Objects added to an existing application created using the Quick Create wizard may cause previous object definitions to be shown as dependent versus core objects. As a work around when viewing the overall Application definition, move the objects as appropriate using the 'Attach Object' functionality of the core and dependent objects view. Meanwhile, this will be addressed in the next release. 14. Quick Create wizard error messages might be truncated. For example, the error message, "object name is required" might appear as just "object name is ". 15. Misleading UI Shows 1:M for Hierarchical relation when using the Quick Create App Wizard: By definition Rollbase creates a Hierarchical relationship within the object. But when using the Quick Create App wizard to create an application, an icon depicting a hierarchical relationship is not seen in the relationship screen, instead it shows a one-to-many relationship icon. 16. New create Mobile Application option: The "Create Application" dialog includes a new option: "a New Mobile application" . This option allows you to create an application definition and launch the new Rollbase Mobile App builder quickly. However, the resulting mobile application will not be associated with any Rollbase object data unless you explicitly add objects to the application using the Rollbase interface. To create a mobile app that is associated with an existing Rollbase application, do not use this option. Instead, navigate to the "Applications Setup >Applications" page and click the name of the application for which you want to create a mobile app. Scroll down to the "Mobile Apps" section and click "New Mobile App". ========================= Release 2.1 (12/2013) ========================= -------------------- FIXED in Release 2.1 -------------------- - Fixed an issue where a "no protocol: ../m/"; error was displayed when trying to run a document template. --------------------------- KNOWN ISSUES in Release 2.1 --------------------------- 1. When installing Rollbase Private Cloud, a database will be installed even if the 'Create Database' option is turned off on the DB Configuration screen. 2. When installing Rollbase Private Cloud, if the specified locations for the Database directory and the Work directory are different, the Database directory will not be created automatically. In this case you need to manually create the desired directory in which to store Rollbase Database and then run the cdb.sh file which is located in the %ROLLBASE_HOME%\db\install directory. 3. On the Linux platform, when the 'Restore Default' button that is associated with a Rollbase Default Destination field is clicked, an incorrect value is populated. 4. On the Linux platform, the ROLLBASE_HOME environment variable needs to be set manually by users before starting the Rollbase Tomcat server. 5. When installing Rollbase Private Cloud, the 'Port already in use' validation message is not shown if a port for the OpenEdge database is specified on which OpenEdge is already running. 6. When installing Rollbase Private Cloud on the Linux platform, if a Database Name other than the default "rbdb" is specified, you need to start the database manually before starting the Tomcat server. To manually start the database, execute the /startdb.sh script. 7. If you are migrating a Microsoft SQL Server database used with Rollbase 2.0.0.x to Rollbase 2.1, note that there is a syntax error in the migration script "update_2_1_0.sql". The line containing the script error is: ALTER TABLE RB_HOSTED_FILE MODIFY CONTENT_TYPE NVARCHAR(50); This should be written using two lines as follows: ALTER TABLE RB_HOSTED_FILE ALTER COLUMN CONTENT_TYPE NVARCHAR(50); 8. The 'Prompt for Individual user credentials to access target OpenEdge Services' option that is available under Object Definition for an Object created using OpenEdge Services is not functional and should not be checked. The following topics describe changes to Rollbase behavior that might effect your applications: • Change to JSON Date Format on page 9 • Change to Portal CSS on page 10 • Trigger Fix Can Change Application Behavior on page 10 Change to JSON Date Format The getDataField, selectQuery, and selectValue REST methods have been fixed to return dates in the correct JSON format. A new useLegacyDateFormat parameter has been added to getDataField, selectQuery, and selectValue to control the data format, as follows: useLegacyDateFormat This optional URL parameter only applies to JSON output and, specifically, to DATE fields. If useLegacyDateFormat=False, or is not specified, dates will be returned in the normal JSON format, such as: "Wed Mar 05 17:52:38 IST 2014". If useLegacyDateFormat=True, dates will be returned in a format similar to the following example: new Date("Wed Mar 05 2014 17:53:33 (IST)"). The following example shows results in normal and legacy formats: • Normal: { "objName": "CUSTOMER", "createdAt": "Wed Mar 05 17:52:38 IST 2014” } Rollbase: Release 2.2:Version 2.2 9 • Legacy: { "objName": "CUSTOMER", "createdAt": new Date("Wed Mar 05 2014 17:53:33 (IST)") } If you have been using these methods to obtain JSON output and your application is expecting the date format Rollbase used to return, you might need to add the useLegacyDateFormat parameter and set it to true. Change to Portal CSS Rollbase includes a new Pacific portal CSS. New portals created after the 2.2 release will use this CSS by default. To apply the Pacific CSS to an existing portal, follow these steps: 1. Navigate to Setup > Applications Setup. 2. Click Portals. 3. In the list of portals, click the portal name. 4. From the More Actions drop-down menu, select Header and Footer 5. In the Header HTML section, add the following to the body tag: class=pacific-bootstrap Trigger Fix Can Change Application Behavior In the past, the checkCondition parameter of the rbf_runTrigger method was ignored. This was logged as issue PSC00279507 and has been fixed. If the value of checkCondition is true, Rollbase will now test the condition when the trigger runs. If you have applications depending on the former behavior, where the condition was never tested, you might need to change the logic that invokes this method. ========================= Release 2.0.0.4 (11/2013) ========================= For installation instructions on using the Rollbase 2.0.0.4 installer, see the accompanying file, "InstallationNotes.txt". -------------------------------- ENHANCEMENTS in Release 2.0.0.4 -------------------------------- 1. Exposed support for a JavaScript engine optimization setting to significantly improve performance of formulas, triggers and all server-side JavaScript. To enable this, all Private Cloud customers will want to add the following flag to the shared.properties file on each server Rollbase is deployed on: JSOptimizationLevel=-1 2. Enabled white-label header and footer option for any application in Hosted Cloud and Private Cloud -------------------------------- FIXES in Release 2.0.0.4 -------------------------------- 1. Fixed issue whereby REST API login method may return a null pointer exception if an invalid password is supplied 2. Fixed issue with some Norwegian characters not being handled properly in imports 3. Fixed open issues with Rollbase database update scripts for OpenEdge and Microsoft SQL Server 4. Fixed "Unknown data type" issue when moving a tenant from a Microsoft SQL Server database to MySQL 5. Fixed attribute format issue that could cause application XML generation to fail 6. Fixed issue whereby hierarchical relationships may not resolve in Validation triggers 7. Fixed issue whereby 90 day evaluation accounts in Rollbase Hosted Cloud may appear to have 91 days 8. Updated the "Powered by Progress" logo displayed in portals 9. Fixed issue whereby some portal page links sent via email may not resolve correctly 10. Fixed issue whereby JSON syntax generated by REST API logout method may not be correct ========================= Release 2.0.0.3 (11/2013) ========================= -------------------------------- ENHANCEMENTS in Release 2.0.0.3 -------------------------------- 1. [Private Cloud] Added new shared.property called "PacificUIDisabled" to allow Private Cloud customers to turn off all Progress Pacific branding for white-label deployments. When set to 'true', the Pacific UI header and footer is disabled in favor of the old/standard Rollbase brandable header and footer. 2. [Private Cloud] Added name and version number of JDBC driver to database Create and Edit pages in System Console 3. Increased allowed picklist integration code length from 10 to 512 characters 4. Added "CSV" as a new supported "Output Type" in Batch Jobs of the type "Generate Report" -------------------------------- FIXES in Release 2.0.0.3 -------------------------------- 1. Fixed issue whereby REST API logout method does not honor the JSON response type 2. Fixed issue whereby non-ASCII characters are not displayed properly in the Pacific header 3. Restored expected behavior for custom login pages used by Hosted ISV customers 4. Fixed issue whereby Rollbase Hosted Cloud is not able to save specific Triggers or Templates 5. Fixed alignment issues with the Page Editor in Chrome 6. Restored expected behavior for Rollbase users to modify personal settings and password from within the Rollbase user interface 7. Restored expected behavior for Rollbase Administrators to reset passwords for users from within the Rollbase user interface 8. Fixed issue whereby some translation keys were missing in language resource files 9. [Private Cloud] Fixed issue whereby a thread could be forced into a deadlock state when performing database connection cleanups ========================= Release 2.0.0.2 (10/2013) ========================= -------------------------------- FIXES in Release 2.0.0.2 -------------------------------- 1. Fixed an issue whereby logging out of Rollbase Hosted Cloud from within the the Pacific Console may takes an excessive amount of time. 2. Fixed a problem that caused a "no protocol: ../m/" error when rendering HTML documents as PDF. 3. Fixed an API validation issue when a comma is used as decimal separator and the decimal part of the field value is too large. 4. [Hosted Cloud] Fixed a Login error when using a bookmark to get to access a Rollbase application. Now following a bookmark directly accesses the Login page and directs the user to the bookmarked page after login as expected. 5. Fixed a problem whereby a Rollbase tenant could get loaded onto two or more PROD servers without the "span multiple servers" setting enabled, resulting in cache synchronization problems that lead to the appearance of lost metadata. 6. Fixed an issue where Rollbase popup windows might pulsate when they are resized to a point where horizontal or vertical scroll bars need to appear. 7. [Hosted Cloud] Increased trigger timeouts to address timeout errors such as "System Error:Triggers are running too long, process is aborted to protect system resources." 8. Fixed issue whereby scheduled batch jobs may not execute on schedule as expected. 9. Fixed issue whereby the "Dedicated Server" field on the Customer object in the Master system was not available in Mass Update pages 10. Fixed issue whereby the Calendar selector for entering dates in May or March of any year did not work correctly. 11. [Private Cloud] Fixed issue whereby the 'Free Rollbase Evaluation' banner may appear twice in a Private Cloud installation. 12. Fixed issue whereby server-side API rbv_api.createRecord() and rbv_api.updateRecord() methods require field values for required fields that already have existing values. ========================= Release 2.0.0.1 (10/2013) ========================= -------------------------------- FIXES in Release 2.0.0.1 -------------------------------- 1. Fixed issue whereby REST API update and update2 methods may not function as expected ====================== Release 2.00 (10/2013) ====================== -------------------------------- ENHANCEMENTS in Release 2.0.0.0 -------------------------------- 1. Added new server-side API utility methods rbv_api.jsonToString() and rbv_api.stringToJson() methods for converting to and from JSON 2. [Private Cloud] Added a new configuration setting to shared.properties for max length of Query API called "MaxQueryLength" 3. [Hosted Cloud] Integrated Rollbase Hosted Cloud into the Progress Pacific platform framework with Pacific Dashboard and centralized login page using ProgressID as the authentication service. 4. Added new server-side API utility method rbv_api.evalXpath() to parse an XML string and evaluate it as an XPath expression. 5. Added ability to use Related Fields in View filter criteria 6. Added capability for Time fields to accept ISC-formatted strings "HH:mm:ss" as an alternative to the user-defined format 7. Added a "View" link to the Actions column of Views. This link only appears when the Record Name field is not included in the View to ensure users have a way to navigate to each record. -------------------------------- FIXES in Release 2.0.0.0 -------------------------------- 1. Fixed issue whereby Triggers with a specified delay time may not be executed as expected 2. Fixed issue whereby the rbv_api.sendJSONRequest method for DELETE does not work as excpected 3. Fixed issue whereby the rbv_api.selectCustomerNumber does not return the correct value 4. Fixed issue whereby related fields in Mass Update pages are not editable 5. Fixed issue whereby the REST API login method does not properly return a JSON response when requested to do so 6. [Private Cloud] Fixed issue whereby filtering views and reports on multi-select picklist fields is not working when running Rollbase on Microsoft SQL Server databases 7. Fixed issue whereby rbv_api.getFieldValue() may return NULL instead of 0 8. Fixed issue whereby REST APU selectQuery() method with XML output format provides no empty nodes for NULL values. 9. [Hosted Cloud] Changed CSV output for REST query API to use date/time values in UTC rather than server time zone 10. [Hosted Cloud] Fixed issue whereby users may not be logged in when viewing the Application Directory even if they do have a valid session. ----------------------------- New Features and Enhancements ----------------------------- * User Experience enhancements include: - Single sign-on with your Progress ID to the Pacific Console - New user interface design - A new Community for users which migrates all Rollbase forums from GetSatisfaction to the new Rollbase Community * Connection Pooling changes get faster database access within your application using Bone Connection Pooling (BoneCP). This is now the default setting and the JDBC URL does not require a BoneCP prefix. Legacy connection pooling is still available as an attribute to the Database element * A Rollbase Private Cloud(RPC) installer bundles the installation of Rollbase and OpenEdge Enterprise RDBMS with JRE and Tomcat to save users from having to download and install components separately * The Oracle & SQL Servr versions support ConnectionRetry and useTxtRecovery parameters within the JDBC URL. * Private Cloud distributions of Rollbase include branded DataDirect drivers. * These Rollbase DataDirect drivers also support BoneCP.