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.]
When the navigation item is saved with special characters, the user is unable to open the form. Upon clicking the item, an error is reported: “Due to either a session timeout or unauthorized access, you do not have permission to access this page.”
When you create a custom navigational link, if special characters are used such as /, \, &, #, %, they break the capability to redirect the user to a form or to an external link. Refrain from adding a special character. They must be omitted so that the form can be rendered.
[Admin: This post is related to the 01.29.18 post about restricting special characters in a text field. To see other related posts, use the Character tag.]
When trying to upload a file type that should be allowed based on the contents of the INCLUDE_EXTENSIONS and EXCLUDE_EXTENSIONS lines, the user gets a message stating that uploading a file of that type is not allowed. Why?
Adding spaces in the extension list will invalidate any other defined value after the first one listed. In the TRIRIGA 3.5.2 and later releases, more variables were added to the TRIRIGAWEB.properties file, for more-precise control over what can be loaded as an attachment to a record, or added to Document Manager. These variables are documented in the TRIRIGA Release Notes, but to give the basic information, these are the two new sets of variables:
Any file extensions can be added here, but the format of the list needs to be properly set. Use only comma-separated values (CSV) without spaces to build the string. If there are any spaces in the list, remove them…
[Admin: To see other related posts, use the “include_extension” search phrase.]
Is it necessary to have a separate Microsoft IIS server for every IBM TRIRIGA application server?
It is not a requirement to have a separate Microsoft IIS server for every IBM TRIRIGA application server. Your IT team should determine if this is something that they want or need to do.
[Admin: To see other related posts, use the IIS tag.]
What HTML tags and attributes that can be used for outgoing mail messages and notifications from IBM TRIRIGA Application Platform?
The following lists cite the HTML tags and attributes that can be used for outgoing mail messages and notifications.
[Admin: To see other related posts, use the HTML tag or Email tag.]
A navigation item whose target is set to “External URL” and whose URL links directly to a folder no longer works. An error such as the following might occur: “An error occurred, please contact your system administrator: [MID-4077624314].”
The Java applet that uploaded documents based on the navigation item target in earlier TRIRIGA versions is deprecated due to security concerns. Most browsers no longer support Java applets. The applet upload function is replaced with an HTML5 upload function.
As a result of these changes, “External URL” navigation items in earlier TRIRIGA versions that successfully uploaded documents via portals to upload documents to a folder might no longer work. The Document Upload widget was redesigned to be used only in the context of either Document Manager or a record, not a portal. Use Document Manager directly to upload documents.
[Admin: This post is related to the 04.07.17 post about “External URL” navigation items that may no longer work, and the 07.10.15 post and 04.10.15 post about the document upload enhancement. To see other related posts, use the Document Manager tag.]
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.]
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.]
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.]
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.]
