This release includes the option of provisioning a self-managed Build Farm on your infrastructure, to build Client Apps without relying on hosted Build Farm.

For more information, see:

In previous releases of RHMAP, deploying a Cloud App into Environment required a Cloud App source-to-image (S2I) build that creates a new Docker-formatted container image. In this release, RHMAP reuses the Docker-formatted container image created in the previous Environment when reuse is appropriate, that is, when both the commit hashes and Node.JS runtime versions are identical. This provides more consistency and better performance for Cloud App deployments.

This release includes features to improve MongoDB resiliency.

This release includes a new deployment option for Cloud Apps and MBaaS services, Node.js version 6.9.1. You might want to use this version of Node.js for performance and security improvements.

A new version of FHC, the RHMAP command line interface, is available, including many resolved issues. Install or update FHC using the following command:

npm install -g fh-fhc

For more information about FHC, see the Local Development Guide and the FHC Package details.

If you perform a fresh installation of RHMAP 4.5, all pods include health checks. If you upgrade from RHMAP 4.4 all pods, except the MongoDB replica set pods, include health checks. If you require health checks for the MongoDB replica set pods, enter the following commands:

$ oc rsh <mongodb-pod-name>
$ mongo admin -u admin -p ${MONGODB_ADMIN_PASSWORD}
$ rs.reconfig(rs.config(), {force: true});

To learn more about health checks, see the OpenShift Developer Guide.

RHMAP now supports OpenShift Container Platform 3.6 and uses Red Hat Enterprise Linux 7.4 to improve security.

When you create a push notification, it is delivered by push notification networks, such as FCM and APNS. Sometimes, the RHMAP status of the notification remains at 'Pending', despite being accepted by the push notification network.

If you delete a WFM workflow, work orders associated with that workflow show incorrect template data. To work around this issue, create new work orders, and note that you cannot delete the incorrect work orders.

If you click submit on a draft or review form, sometimes a check box selection error is displayed, despite the correct selection of check boxes.

To work around this issue:

To develop apps for iOS with Swift using XCode 8.3 or later, you must upgrade the iOS Swift SDK to build an app using RHMAP. To download the latest SDK, see fh-ios-swift-sdk.

If you use the Build Farm to build Cordova apps and use the following plugins, then you must update them as follows:

Very large files or repos may cause your browser to become unresponsive when accessing the Studio editor.

The lists for Projects and Environments in the Studio are not sorted based on creation time. There is no workaround for this issue at the moment. Studio allows you to sort items, for example, you can view a list of Projects sorted by last update. However, only the current page is sorted, if you click the next page, the sorting is lost. There is no workaround for this issue at the moment.

When deploying a Cloud App using the Studio, the progress bar sometimes hangs on In progress even after the App has been successfully deployed

The progress log bar on deploy screen is still in an In progress rather than Success state. The deployment history table entry for this deploy is marked as Complete/Success, but the progress bar does not reflect this. When this issue occurs, the App is actually deployed and it is safe for you to ignore the progress bar and continue normally.

If you created an app using the WFM template from RHMAP 3.14 or 4.2, you can no longer build that app using the Build Farm. To work around this issue, remove the 'hooks' directory from the app directory.

WFM includes a demo portal app that allows you create and edit workflows and workorders. However, if you create a workflow or workorder and immediately edit it after creation, your edits might not be saved. To workaround this issue, always navigate to an old workorder or workflow after creating a new workorder or workflow, before attempting to edit or delete the workflow or workorder you just created.

RHMAP includes a feature that allows you to create a form that triggers an email after each submission. One of the email options is to include the app name, however the emails sent from RHMAP do not include the app name. There is no known workaround for this issue at this time.

If you perform an action that applies to all environments, but one or more environments is associated with an MBaaS that is currently unavailable, you may see messages that are unhelpful. For example, if you delete a form for a project that is associated with an environment MBaaS that is unstable might result in a 401 error. To work around this problem, ensure all MBaaS instances are available.

On the Environment Variables screen in the Studio, you can push any environment variables to your OpenShift 3 Cloud App. However, if you do this and Cloud Apps deploy to Openshift 3, the FH_REDIS_HOST and FH_REDIS_PORT environment variables in the Cloud App DeploymentConfig will be removed. If you don’t intend to use the fh.cache API, or you don’t intend to push any custom environment variables from the Studio, this issue does not affect you.

If you encounter this issue, the fh.cache API in the Cloud App will not work.

To workaround this issue:

If you have already pushed environment variables to the Cloud App, and the FH_REDIS_HOST and FH_REDIS_PORT env vars have been removed, it is possible to determine what the values should be:

If you are using OpenShift 3.3 and upgrade from RHMAP 4.4 to 4.5, you encounter a known OpenShift issue relating to ConfigMaps. Environment variable values are not read from ConfigMaps, and the issue is described in https://bugzilla.redhat.com/show_bug.cgi?id=1475264. RHMAP functionality is not affected.

The Data Browser Export button is incorrectly presented to user as being disabled. However, clicking the button will export data.

If you set up SMTP for cloud app alerts as described in https://access.redhat.com/documentation/en-us/red_hat_mobile_application_platform/4.2/html/mbaas_administration_and_installation_guide/setting-up-smtp-for-cloud-app-alerts and your OCP cluster is behind a HTTP proxy, the mails will fail. To workaround this issue, add a firewall rule to allow outbound traffic to the IP address and the port specified in the SMTP_SERVER and SMTP_PORT environment variables in the millicore deployment configuration of the RHMAP Core project.

You cannot edit a Jenkinsfile using the Studio editor. To work around this issue, edit the file in your cloned git repo and push the changes.

If you are using the Sync Framework, note that there is a known issue with iOS apps that use webkit-sqlite for storage. After the app is running for longer than a few minutes, you might encounter storage failures. Use indexDB for storage instead.

The self-managed Build Farm supports Node.js 4.4 client code by default. As a result, the Ionic template will fail if you try to build a client app. Also, any Node 6 specific code in your client app may also fail. There is no workaround available, however this issue will be addressed in a future release.

If you want to build your existing Cordova apps using the self-managed Build Farm, update the app to be compatible with Cordova 7. For example, to make apps based on SAML, Forms and Raincatcher (Technology Preview) templates, upgrade the following plugins in the config.xml file:

If you try to export BSON data as described in Storing Data, the export fails. To workaround this issue, export data as JSON or CSV.