Component API documentation for developing applications with UX Framework is deployed with your TRIRIGA server. Component documentation can be accessed via the following endpoint:
- The [tririga-hostname:port] and [/context_path] are the specific values you’d normally use to access your IBM TRIRIGA environment.
Once at the component documentation page, you can browse or search the TRIRIGA delivered components that are available on your specific platform version using the left-hand panel. Further down in the list, you can find documentation for the available third-party components delivered with the corresponding version of Google Polymer. (This version varies, based on the TRIRIGA platform version. See the Support Matrix for more information.)
In the right hand panel, the documentation provides information about the selected component, generally with sample usage, styling and an API reference. In some cases, there are also demos available. You can toggle between the Doc and the Demo for a component using the buttons in the top right of the page…
[Admin: Similar content is also found in UX Article 2: Implementing UX. This post is related to the 12.11.15 post about the UX framework.]
I’m looking for any information on what third-party tools can be integrated with TRIRIGA, specifically, ERP systems like CGI’s Momentum and other construction-based tools. I’ve looked at the IBM TRIRIGA Compatibility Matrix, but I’m sure the list isn’t as complete as the work that’s been done.
Here are a couple of links that might point you to the right people. In each post, click “Continue reading” to see the original Facebook discussion. From there, the TRIRIGA group members might offer further info. Good luck!
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…
Where is the information regarding IBM TRIRIGA Application Platform 3.5.2 and IBM TRIRIGA 10.5.2 features, installation, and more?
[Admin: This post is related to the 06.13.16 post about finding 3.5.1 and 10.5.1 information, the 12.11.15 post about finding 3.5.0 and 10.5.0 information, and the 10.01.15 post about finding 3.4.2 and 10.4.2 information. To see other related posts, search “where is the latest“ or “where can you find“.]
Since early 2016, most browser vendors no longer support the Netscape Plugin Application Programming Interface (NPAPI) architecture. Most Java applet plugins for web browsers rely on NPAPI to render Java applets.
Impact to IBM TRIRIGA applications
The end of NPAPI support prevents the Java applet-based TRIRIGA areas — such as the Gantt, Availability, and Stacking sections — from rendering in IBM TRIRIGA applications on certain browsers.
Areas of TRIRIGA impacted by changes in browser support
The following IBM TRIRIGA areas are impacted. Details on each area follow.
- Gantt section
- Availability section
- Availability Legacy section
- Stacking section
- Other Java applet-based TRIRIGA areas…
[Admin: This post is related to the 04.07.16 post about TRIRIGA compatibility with browsers, and the 07.16.15 post about removing NPAPI support from Chrome.]
The TRIRIGA 3.5.1 compatibility matrix says that WebSphere 188.8.131.52 is supported, but also that “Future fix packs for this version are also supported.” If you run the TRIRIGA 3.5.1 installer with the full version of WebSphere 184.108.40.206 in place, the install works. If you try running with the full version of WebSphere 220.127.116.11 in place, however, the following error occurs:
“WebSphere Problem: WebSphere version is too old. The version of WebSphere that was detected is too old. IBM TRIRIGA Application Platform requires WebSphere version 18.104.22.168 or newer.”
This problem was seen when performing the TRIRIGA 3.5.1 install on Windows. It may exist when running the installer on other operating systems, as well.
[Admin: A similar article is also posted in the IBM Support Portal as a technote.]
Why are you having issues with record transitions in Microsoft Internet Explorer IE11? Having ended support for Compatibility View (Mode) in IE11, requests were made to provide this functionality in the TRIRIGA 3.4.x and 3.5.x release branches. This was done with releases 22.214.171.124 and 126.96.36.199, but simply implementing the change may not completely resolve the issue.
During deployment, a variety of page data is cached at the server level, and this cache is not cleared during the upgrade process. This can result in the compatibility changes not being apparent when a user first accesses the application after upgrade.
Clearing the cached content at the server level will eliminate the cached data as a possible cause.
[Admin: This post is related to the 09.29.14 post about clearing up the TRIRIGA application server cache area.]