Several TRIRIGA users are receiving HTTP 413 errors (“Entity too large” from IIS) under Internet Explorer 10 (IE10). The problem may be caused by a very large page that is exceeding the size of the browser’s cache…
In an effort to fix this issue, the uploadReadAheadSize (IIS) was increased from the default of 48K up to 128K, and the responseBufferLimit (webconfig) from the default of 4M to 16M. We also attempted to clear the browser cache. None of these changes resolved the problem. Finally, we identified a very large page that was exceeding the size of the browser’s cache limitation.
To resolve the problem, increase the size of the browser cache. For Internet Explorer 10, navigate to Settings > Internet Options, select Settings in the “Browsing History” section, then select the “Caches and Databases” tab. The default value might be 10 MB. After increasing it to 25 MB, there were no further problems.
[Admin: To see other related posts, use the Internet Explorer tag or Browser tag.]
We are using IdP-initiated SAML, and we access TRIRIGA via a link that looks something like this: http://idpprovider/applications/Tririga. Can we pass this link in FRONT_END_SERVER in TRIRIGAWEB.properties so that users can click on the link that they get in a work task email, and they can be redirected to TRIRIGA?
SAML does not support basic authentication for non-browser clients. This is a SAML limitation. See the following APAR IV88274 link.
[Admin: For convenience, here are the meanings of the acronyms: Identity Provider (IdP), Security Assertion Markup Language (SAML).]
[Admin: This post is related to the 08.18.16 post about lack of support for non-browser clients. To see other related posts, use the SAML tag.]
In the Chrome browser, when not enclosing string values in single quotes in a query that uses an “In” or “Not In” user filter, the user gets an error message. The user cannot close the error message and has to close Chrome.
[Admin: To see other related posts, use the Filter tag.]
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.]
We are currently using TRIRIGA 10.5.1/126.96.36.199. In IE11, when a record is selected to print, the printer gives a blank page. Whereas before printing, selecting Print Preview shows the page correctly. This behavior was not observed with Google Chrome, where everything gets printed without any issues.
After further investigation, it looks like a Microsoft Windows Update broke this print functionality, and they have since reverted the change that broke it. If you are on the absolute latest IE11 patch, the Print Preview should be working again. Take a look at this blog link. Microsoft has released KB4032782 to address the issue.
[Admin: This post is related to the 11.07.16 post about the font in the Print Preview and printed hardcopy being too small. To see other related posts, use the Print tag or Print Preview tag.]