We recently upgraded our customer to TRIRIGA 3.5.2. Thus, we had to upgrade the CAD Integrator to 126.96.36.199. Previously, when we used the Smart Attach, only 2 required fields were present: Current Use Space Class and Default Layout. But now, we have these additional required fields: Room Type, Reserve Calendar, Reserve Display Room Name, and Usage Unit. How can we turn off or disable these extra fields? The customer is not using Reserve yet.
In TRIRIGA, by default, the Reserve tab is not visible. But if the user clicks the Reservable check box in the General tab, then the Reserve tab is visible. So, the key is that the Reservable tab is not visible in the form metadata by default. Hence, CI would not consider those fields as required.
However, I assume that in your configuration, these Reserve fields are required? So, if a user creates a new space, they have to fill out the required Reserve fields before they can create it, right? CI is just attempting to emulate this situation.
[Admin: To see other related posts, use the Integrator tag.]
We imported an Oracle 12c database dump from a TRIRIGA platform running TRIRIGA 188.8.131.52 into another Oracle 12c server. The Oracle Data Pump Import (impdp) completed without error. The plan was to install and upgrade the TRIRIGA platform to 3.5.2. This is something we’ve done multiple times with different releases. So platform upgrades are usually painless.
We went right through the upgrade process dialogs, a successful database server conductivity test, but here’s something we’ve never experienced before. Instead of installing and upgrading the database to the new platform, “Installed by InstallAnywhere 17.0 Premier Build 5158” throws up the following dialog box.
“Upgrade Not Supported. An upgrade from the version of your platform is no longer supported. Please upgrade to 184.108.40.206 first, before upgrading to this platform version. Back or Exit.”
Does anyone have any ideas why we are getting this message?
We found the issue. The schema name was “TR1DATA”, not “TRIDATA”. The terminal font was not showing a clear distinction between “1” and “I”. We’d better take a much closer look next time. Thanks for the assistance from everyone.
How do you run the MS SQL “SetVarcharColsToNumeric_MSSS.sql” and “SetVarcharColsToNumeric_MSSS_Publish_BO.sql” scripts after upgrading to TRIRIGA 220.127.116.11? According to the TRIRIGA 10.5.2 and 3.5.2 release notes:
- “There are two scripts for MS SQL, SetVarcharColsToNumeric_MSSS.sql and SetVarcharColsToNumeric_MSSS_Publish_BO.sql. Run SetVarcharColsToNumeric_MSSS.sql first. When it completes, run SetVarcharColsToNumeric_MSSS_Publish_BO.sql.”
- “Run the script PRIOR to installation of IBM TRIRIGA Application Platform version 3.5.0. NEVER run the script after upgrading to 3.5.0.”
Our application is 10.4 and platform is 18.104.22.168. How can the SQL script be applied to update the system fields with the sub-attribute type of CreatedDateTime to CreatedDateTime (Number) and ModifiedDateTime to ModifiedDateTime (Number)?
After upgrading to TRIRIGA 3.5.1.x or later, some customers are having issues with thumbnail images on reports and/or queries not being displayed correctly.
WebLogic incorrectly parses a JSP by adding white space that corrupts image thumbnails. Meanwhile, WebSphere and Liberty parse the JSP correctly. Moving forward, we resolved an issue where Oracle WebLogic was incorrectly interpreting TRIRIGA code, and injecting extra white space that caused thumbnail images to be displayed as broken images.
I have recently upgraded to TRIRIGA 3.5.2/10.5.2. Currently, no user records are created. So I created one user record, but I can’t see the list of licenses under the “My Profile” tab in the user record. All licenses can be seen from the Tools > List Manager, and are also placed on the server under the \config\ folder. Any help would be appreciated.
See if this technote might help: Why aren’t IBM TRIRIGA employee records bringing the list of licenses available on system?
[Admin: This post is related to the 04.22.16 post about employee records not showing the available licenses.]
After upgrading to TRIRIGA 3.5.2, customers may see similar queries being fired from report runs, and may get system freezes afterward since the database will be extremely busy executing them…
When applying Geography or Organization security, a group with root level \Organizations and a geography set at a low level like \Geography\North America\USA\Nevada\Las Vegas will no longer apply an Org-level security check on queries. The same goes for security groups unrestricted at the Geo-level, but set at a low level of the Org. The security check will be applied on a Geo and/or Org basis based on the root-level security setup for the Geo and/or Org.
As we approach the end of the first quarter, we thought we’d send a reminder about some of our IBM Watson IoT product versions and supported platforms that are currently scheduled for End of Support (EOS) in April 2017:
- 30 April 2017: 5725-F25, IBM TRIRIGA Portfolio Data Manager, 10.2.x
[Admin: This post is related to the 08.26.16 post about End of Support (EOS) plans for TRIRIGA versions.]