IV92858: SESSION_HISTORY_TRACKING property is not removing sessions

When using Connector for Business Applications (CBA), the users are still being tracked in the SESSION_HISTORY table even though in the TRIRIGAWEB.properties file, there is a property SESSION_HISTORY_TRACKING, that when set to WEB_USER, is supposed to remove sessions from that table.

The user that is being used for CBA has a user count that is set to 50. When the user count = 1, everything works the way it is supposed to work. The issue shows itself when the user count = 50. As a result, there is a buildup of records inserted into the database, which causes the database to run out of space. So you have to manually delete the users from SESSION_HISTORY.

Continue reading

Why don’t all resources display when creating a reservation?

When you create a reservation, for example, a Location Reservation, some of the resources do not display on the Find Available Times tab of the reservation.

By default, only 50 rows display when the Find Available Times tab of the Availability section of a reservation is rendered. If there are too many results, a warning about exceeding the row size is displayed. Your administrator can change the maximum number of rows that display by changing the AVAILABILITY_SECTION_ROW_LIMIT property in TRIRIGAWEB.properties. As noted above, the default value is set to 50 rows. If set to 0, -1, or other invalid value, the default number will be used.

Warning: If the property is set too high, performance issues might occur when rendering. Large values might cause memory issues. It is recommended that you update the backing reserve queries to reduce results or design filters that keep the number of record results under this value. Any value above the max value of 500 will be set to 500.

Continue reading

IV90015: Large export to Excel causes out-of-memory crash

A large export to Microsoft Excel may cause an out-of-memory crash on the JVM or server, or cause a zero-byte or seemingly-corrupted Excel (XLSX) file. When analyzing the heap dump file, you will see the following classes taking the most of the JVM heap dump space:

  • (A) “com.tririga.architecture.web.process.useresponse.ExportExcell$2”, loaded by “<system class loader>”
  • (B) “org.apache.poi.xssf.usermodel.XSSFRichTextString”, loaded by “<system class loader>”

Continue reading

Where can you find information about document permissions?

Document permissions overview

In general, a user may access a Document record when at least one of the following is true:

  • Rule 1. By being the author of the document record. The user who creates a document record is given access to the document implicitly.
  • Rule 2. By being granted access on the Permissions tab of the document record.
  • Rule 3. By being an admin user.

Bypassing explicit document permissions for users with group access to a smart record

In some cases, however, non-admin users who have not been given explicit access via the Permissions tab may need to access document records from a smart section. In order to facilitate this functionality, we have added a new web property called HONOR_DOCUMENT_PERMISSIONS_MODEL_FOR_DOWNLOAD to TRIRIGA Platform version or later, or later, 3.5.2 or later.

  • When this property is set to TRUE, the permissions model will be enforced as described by Rules 1 – 3 above.
  • When this property is set to FALSE, Rule 2 will be bypassed when the document is accessed from a Smart Section context. In other words, users who have access to open document records through a smart section will also be granted view and download permissions even if they are not the author and were not given explicit access on the document’s Permissions tab.
  • DISCLAIMER: This change is system-wide and will affect the accessibility of Document records that are viewable from ANY smart section of ANY smart record that is accessible to ANY user.

Continue reading

IV89144: CLEAN_TIMEOUT property not working as expected in 3.5.1

With the CLEAN_TIMEOUT property set to 10 minutes, 10 minutes is too low of a setting and not recommended. Typically, it is set to a value to prevent the Cleanup Agent from running too long.

How that property comes into play with the Cleanup Agent is that it runs each cleanup task in order. The cleanup process contains several tasks: cleaning up BO records, workflow instance history, doc tables, etc. Once a task is complete, it looks at the current running time, compares it to the property, and decides whether or not to continue with the next task. With that said, it doesn’t even look like it’s honoring the property at all, based on your logs, because it should have ended at this line:

2016-09-01 22:28:58,117 INFO [com.tririga.platform.dataconnect.JobControlManager](PlatformMaintenanceScheduler) DataConnect Tables Clean up completed at Thu Sep 01 22:28:58 CDT 2016 deleted 0.

Continue reading

How do you set the Cleanup Agent to clean data “x” days or older?

How can we change the Cleanup Agent to only clean up data older than “x” days? I saw the CLEANUP_AGENT_SCHEDULED_EVENT_COMPLETE_DAYS property, but this seems to be only scheduled events, rather than all data.

[Admin: This post is related to the 02.24.16 post about executing the Cleanup Agent, including deleting records that are only minutes old.]

Continue reading