Why aren’t the INCLUDE_EXTENSIONS file types uploaded as expected?


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:

  • COMPANY_FILE_UPLOAD_EXCLUDE_EXTENSIONS and COMPANY_FILE_UPLOAD_INCLUDE_EXTENSIONS
  • IMPORT_CONTENT_EXCLUDE_EXTENSIONS and IMPORT_CONTENT_INCLUDE_EXTENSIONS.

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

Continue reading

IV97319: Modifications to lease extension calculating incorrectly


When an “Operating” lease is modified, the new ROU asset balance should be calculated as the amount of change in the liability balance that is added to (or subtracted from) the prior period ROU asset balance immediately preceding the modification. Previously, this was tested on 5/18 for any lease and then still worked appropriately. As of 6/13, this no longer works.

Moving forward, the starting ROU asset value is now calculated correctly when there is an amendment to an “Operating” lease. The changes were made to the following workflows: “triContract – Subflow – Likely Term – Calculate Amend Asset Value” and “triRealEstateContract – Synchronous – triRevise”.

[Admin: To see other related posts, use the ROU tag or Right of Use tag.]

Continue reading

How do you limit the upload file size to IBM TRIRIGA?


This is a common question from many TRIRIGA administrators. We have parameters to limit the file extensions for a while now, but limiting the file size was a missing capability, until…

In TRIRIGA 3.5.2, we introduced a new property in the TRIRIGAWEB.properties file called MAXIMUM_UPLOAD_FILE_SIZE_BYTES that allows administrators to configure the maximum permissible size for file uploads. If no value is set, the default is 20 megabytes. We hope you make good use of this feature after you upgrade to 3.5.2 or higher versions of the platform. I’m sure your storage specialist will owe you one!

Continue reading