Having an issue with editable queries and SQL queries in 3.5.2


I’m having two issues which I think are related. The environment is running Windows with SQL Server 2016.

  • 1. In editable queries, I have a locator field, and I pick from the locator query. But after I click OK, my session times out, and it doesn’t save the changes. This affects all browsers: Safari, Chrome, IE.
  • 2. In the Admin panel, if I have comments in my SQL query, the query now fails. For example… “SQL SCRIPT IS NOT VALID SELECT STATEMENT, PLEASE REVISE.”

What I noticed is that I get the same error in the error log when using the locator field in an editable query. Something seems to be failing related to SQL queries. Can anyone reproduce this issue? This is a critical failure in our upgrade tests and I will most likely submit a PMR for a patch.

Continue reading

Advertisements

What is the IBM TRIRIGA compatibility with Apple iPads?


I’m not sure if the supported OS list includes iOS officially. With the advent of iPad Pro devices, the line between iPhone-like devices and computers gets further blurred. After all, an iPad Pro begins to feel a lot like a MacBook Air. There is support for Safari on a computer as well, and generally the move is to become device-agnostic.

But I need to put forth some guidance about iPad Pro devices and TRIRIGA. My initial observation is that some basic functions don’t work correctly, perhaps HTML5 related? For example, rendering the portal. The page starts loading correctly, then the screen jiggers a bit and seems to stabilize, but scroll bars never appear and the user cannot move up or down. I’ve tested in both Safari and Chrome.

Official support of IBM TRIRIGA on iPad is limited to the IBM TRIRIGA UX Framework and Perceptive Applications. Traditional TRIRIGA, portal, and non-UX applications are only supported on Windows and Mac OS X operating systems when running Safari, Chrome, Edge, Firefox, or IE11. Although a lot of non-UX TRIRIGA will load on an iPad, you will run into some limitations as you have noted above…

Continue reading

UX: Is there a way to deploy apps to mobile devices without a URL?


Without opening up a web browser and directing to a URL, is there an elegant way to deploy the TRIRIGA UX solution as a mobile application for the client?

Mobile devices generally support creating an “app” on your home screen that is really just a URL. So when you open the app, it launches the installed browser to the URL specified. For example, go to a website on Safari in iOS, then tap the bottom center icon (box with an up arrow) and select Add to Home Screen. A mobile device management (MDM) solution should be able to deploy apps backed by URLs globally.

Continue reading

Where is the latest on IBM TRIRIGA compatibility with browsers?


As of 04.07.16, here are the TRIRIGA “Desktop Client Compatibility” requirements for the following desktop browsers. See the wiki page for the latest requirements.

Third Party Browser Supported Version Notes
Microsoft Internet Explorer 11 See the same note below.
Microsoft Edge 20 See the same note below.
Mozilla Firefox ESR 38.4 See the same note below.
Apple Safari 9.0.1 See the same note below.
Google Chrome 47 See the same note below.
These versions are the minimum versions that are supported for each browser. IBM TRIRIGA will support future versions of a vendor’s browsers if the vendor does not remove, or explicitly or inadvertently disable, functionality that IBM TRIRIGA products rely on. Although future versions are supported, any issue that is introduced as a result of a browser upgrade might require an IBM TRIRIGA Platform fix pack or IBM TRIRIGA Platform upgrade to be fully supported.

Edge and Chrome do not support the NPAPI plugin, which prevents Applets from loading. This prevents the Gantt, Availability, and Stacking sections from rendering in IBM TRIRIGA applications.

[Unlike classic IBM TRIRIGA applications,] Perceptive Applications require the support of modern web specifications to function optimally. Only evergreen browsers (Chrome, Firefox, Edge, and Safari) are supported when using Perceptive Applications or creating custom Views in UX Framework. Internet Explorer 11 [IE11] is not supported.

[Admin: This post is related to the 11.14.14 post about the latest compatibility matrix (updated 12.11.15).]

Continue reading

Microsoft will work on security fixes for Internet Explorer 11 only


Microsoft has stopped work on any non-security bugs in Internet Explorer. To quote: “[Microsoft is] not presently working on feature bugs in Internet Explorer outside of security-related issues”​.

If an issue is encountered with Internet Explorer when using TRIRIGA 3.4.2+, please try to replicate the issue on Chrome, Firefox or Safari. If the issue can be replicated on one of those browsers, we will be able to investigate it further. If the issue is only on Internet Explorer, we suggest migrating to a different browser. Also note, Internet Explorer 10 has reached its end of life, so no support will be given on this browser for any TRIRIGA Platform version.

Continue reading

Why upgrade to TRIRIGA Platform 3.4.2 and Application 10.4.2?


The current release of TRIRIGA includes Platform 3.4.2 and Application 10.4.2. This is a powerful release for a number of reasons… Here are some of the key values:

  • We removed several Java applets minimizing the need for client configurations.
  • We removed some Adobe vector graphics tooling that was in conflict with Microsoft security. Recent MS security patches were causing workflow builder to stop functioning correctly.
  • We improved application security in the TRIRIGA platform in line with currently known security vulnerabilities — always a challenge in today’s technology.
  • We added HTML5 functionality that supports a broad range of browsers (IE, Firefox, Chrome, Safari) instead of just IE9.
  • We expanded the capabilities of straight line lease (in the 10.4.2 applications).
  • We addressed a number of APARs (defects) identified in 3.4.1 and earlier releases…

[Admin: This post is related to the 06.18.15 post about TRIRIGA upgrades.]

Continue reading