If you attempt to revise a project from the Schedule tab, where the Gantt chart is visible, your session is expired and you receive an invalid session error. The issue was observed in Internet Explorer and Chrome, but not in Firefox.
An analysis from a Fiddler trace shows that when revising the project in Chrome, this POST to GanttDataUpload.jsp seems to kill the session. In Firefox, for whatever reason, this POST doesn’t occur, and the state transition is successful. To confirm that this is the scenario you are experiencing, use the following technote to run a Fiddler trace and check for the same GanttDataUpload.jsp call: IBM TRIRIGA using Fiddler for tracing web browser traffic.
As a temporary fix, use Firefox. When the record is in a read-only state, no Save action should be called on the Gantt. Moving forward, we resolved the session-kill issue when the user performs a Revise action on a project in the Schedule tab.
[Admin: This post is related to the 08.18.15 post about using Fiddler to trace TRIRIGA web traffic. To see other related posts, use the Gantt tag or Fiddler tag.]
When trying to edit the mapping of a locator field within Data Modeler, the spyglass next to the field does not pop up the mapping window.
[Admin: A similar article is also posted in the IBM Support Portal as a technote. To see other related posts, use the Firefox tag.]
The GIS section height could be expanded since there is a lot of white space at the bottom of the screen.
The issue is that about a quarter of an inch of white space was appearing at the bottom of the GIS map. This fix drastically reduces the amount of white space at the bottom of the map. In doing this, this fix also needed to specially handle a scroll bar that was appearing on Firefox due to the reduced white space. A scroll bar is only needed on the map when the Show Options tab or Show Table tab are being shown. We now programmatically set the scroll bar to either “auto” or “hidden” when those tabs are toggled.
When using Firefox and creating a new record that requires a popup window, the system will disconnect the user’s session… You will receive the following error:
“Sign In Required: Sorry, your session has either timed out or is no longer active. For security reasons, you have been redirected to this page. Please sign in again to continue.”
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…
While trying to edit workflow switches in TRIRIGA 3.5.2, the expression editor does not save correctly when using DateFromDateTime(). After entering my input… And after clicking off and then back onto the same switch… I have tried this in Chrome (Mac), Firefox (Mac), and IE11 (Windows), all with the same result. Is there a fix for this?
My temporary workaround will be to use a calc helper, or some additional date (DA) fields, with the function mapped, and then use the values from the record. This is my current suggestion for anybody else who comes across this issue.
This was reported as an APAR IV91759 and is targeted to the 18.104.22.168 Fix Pack. You can contact Support, and request the 22.214.171.124 LA01 that contains the fix.