How long can a password be in IBM TRIRIGA?


How long can a password be in IBM TRIRIGA?

There is no maximum password length imposed by the out-of-the-box TRIRIGA system. The encrypted password length is 500 characters. However, that encrypted length translates to about 125 characters.

[Admin: To see other related posts, use the Password tag.]

Continue reading

Advertisements

How do you change CI Organization Mapping from Org Name to Org ID?


We have multiple organizations with the same name. We would like to change the CAD Integrator > Batch Associate > Organization Mapping to display the Organization ID instead of the Organization Name. How can I change the list from showing Organization Name to show Organization ID?

You will need to change both the Organization Mapping and the query to call only the Organization ID. After that, clear all caches in Admin Console and do a Full Sync in the CAD drawing. Following these steps, we changed the Organization Mapping from showing Name to showing ID and changing it back. It does not appear to have any negative impact, but there has been no detailed regression testing…

[Admin: To see other related posts, use the CAD tag or Integrator tag.]

Continue reading

Can you run the IBM TRIRIGA script after applying the 3.5.x fix pack?


Can I still run the TRIRIGA “SetVarCharColsToNumeric” script after I have applied the 3.5.x fix pack?

Yes. You can apply the script regardless of the TRIRIGA platform version. But it MUST be applied BEFORE upgrading the application.

[Admin: This post is related to the 04.28.17 post about running the MS SQL “SetVarcharColsToNumeric” scripts. To see other related posts, use the Scripts tag.]

Continue reading

Why is there a “Windows error 2 while loading the Java VM”?


When you try to run one of TRIRIGA’s Application Platform or CAD Integrator installers, most often on a Windows 10 or similar machine, the following InstallAnywhere-based “LaunchAnywhere” error may occur:

“Windows error 2 occured while loading the Java VM.”

This is an issue, not with running the TRIRIGA installers on a Windows 10 machines, but with Flexera InstallAnywhere found within TRIRIGA installers having difficulty parsing the version as it is listed in Java 8 Update 60 and higher. The specific problem being encountered is described here.

Determine if the installer that is running is using Java 8. If so, to determine if the version of Java 8 you are running is update 60 or higher, perform the following… If the version of Java 8 you are running is update 60 or higher, run the TRIRIGA platform or CAD Integrator/Publisher installer using the following command…

[Admin: To see other related posts, use the InstallAnywhere tag.]

Continue reading

Why are there HTTP 413 errors (“Entity too large” in IIS) in IE10?


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.]

Continue reading

What is the purpose and impact of the “Localizable” field property?


I’m seeing issues within report results, where if the user profile language is in US English, the results are of one type, but if the user profile language is in German, it is showing some other data. The record while checked is the same for both cases. While opening and checking the record, the ID and name of the record varies from what it showed as a result in the report. While investigating, what we observed is that these fields are marked as “Localizable” in Data Modeler. What is the use and impact of the “Localizable” field property? Any suggestions?

Here is a PDF link to the 3.5.3 Globalization (Localization) user guide. Also, perhaps this technote on localized database storage will help provide some insight.

[Admin: The same question is also posted in the main Application Platform forum. To see other related posts, use the Localization tag or Language tag.]

Continue reading

Why do queries that are expected to display data show nothing?


When running queries against records within the application, expected record results are not displayed. Why do queries that are expected to display data show nothing at all?

Within the application, we have a variety of different settings that can restrict a user’s access to record data. The user’s Security Group can restrict access to records at the module and BO level, but each use case is slightly different. 

Within every user-facing record, on the System tab, there are fields for System Organization, System Location and System Geography. These values operate in conjunction with similar fields on the Security Group and the User’s People record to allow and restrict access to records. 

The key is that as soon as the user is given a defined Organization, Location, and Geography, the fields on the System tab of their People record are populated. Once that happens, each record they create will be seeded with that information as well. So far, all is well and good, but those users who lack similar settings are now unable to see those newly created records, unless their System fields are the same as or located at a higher point in the hierarchy.

Another area to consider is the Security Group settings for Organization and Geography. If a user has no values set on their People record, the application can still restrict access by using the Security Group values. This can cause a problem as the Organization and Geography Security is defaulted to null in the as-shipped application. This essentially gives the security code no starting point for determining access and will not display records.

To recap, if the record data does not align with the data in the user’s People record, or the data in the user’s Security Group, the record will not be displayed. As mentioned, there are a couple of things to look for. As an Admin user, compare the user’s record data with the record that should be displayed, and correct any misaligned data. Also, in the Security Group, set the Organization and Geography to the root of each hierarchy by default. For additional details, please review the following TRIRIGA wiki article: Security Overview.

Continue reading