IV95312: Incoming Mail Agent does not properly process Apple emails


When emails are sent to TRIRIGA using Apple’s Mail client, they are not always being interpreted properly on the TRIRIGA end. Some problems include:

  • When a rich-text email is sent using Apple’s Mail client and has an attachment, the attachment isn’t seen if the email history is present as part of the email. If the email history is removed, the attachment is seen.
  • When a plain text email is sent using Apple’s Mail client and a PNG or JPG attachment is present, the attachment isn’t seen, but the email body has a marker that makes it look like an embedded image should be present (but isn’t).
  • When a plain text email is sent using Apple’s Mail client and text exists in the email before the attachment, the text that exists in the email before the attachment isn’t seen. Any text that exists after the attachment is seen.

Apple mail formats the attachments and forwards differently than other mail clients. Moving forward, an issue that cause attachments to be missing and email bodies to lose content when the mail client puts attachments inline, has been resolved.

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

Continue reading

IV95201: Need to enable tracking of execution history for all reports


Out-of-memory errors can occur as a result of a report running, but we cannot identify which report. So we need a way to identify the report that is running, who ran it, and how long it is running, so analysis can be provided.

In the TRIRIGA 3.5.1 release, a new flag was added to reports to enable them to be tracked over time. This tracking includes who ran the report, when it was run, and the total duration the report took to complete. By default, this is disabled. However, it may be a good idea to enable full tracking across all reports in the system to help trace performance issues, and usage over time…

[Admin: This post is related to the 04.19.17 post about tracking the report runtime history, and the 10.31.16 post about using the report run history to track performance.]

Continue reading

Is there a way to track the report runtime history in TRIRIGA?


Is it possible to determine query and report usage by username, date, and time? Can that history be retained in the application for a user-configurable period of time? If I want to track usage of any or all reports within TRIRIGA, is there a method to do so?

Yes. With the TRIRIGA 3.5.2 release, a “Track History” check box has been added to all reports that allows for a case-by-case tracking model to be used for report usage. Selecting that option will cause tracking in the “History” tab to take place. Clearing the option will cause the tracking to stop, but existing log data will be retained for a configurable period (days). This variable is found in the TRIRIGAWEB.properties file:

REP_HISTORY_AGE_CLEANUP 365

[Admin: This post is related to the 10.31.16 post about using the report run history to track performance.]

Continue reading

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

IV90499: Uploading with the same name has different versioning


It was noticed that, in 3.4.1.x, when uploading a document through the Notes & Document tab, the document will get uploaded fine. When a second record is brought up and you go to Notes & Documents, and upload a document with the same name that was previously used, the file name will be uploaded and given a [1]. If you go to the Related Documents tab, you will see two line items in the Related Documents section.

In 3.4.2.5, when you upload the same file twice, you see one line in the Related Documents and the revision changed from 0.0 to 0.1. Both uploads show in the History tab of the record. Why is the versioning different?

Continue reading

How do you use the Report Run History to track performance?


In the TRIRIGA 3.5 platform release, a new feature was added allowing you to track the performance and monitor who runs queries and reports in Report Builder. A flag can be set on the report definition that will track who has run the report, and the time it took to retrieve the information from the database.

To enable report run history, open the report in the Report Manager and click “Track History” on the General tab. Note that enabling this tracking causes just a slight overhead, but it should still be used with caution. Once enabled, you will need to let your users use the system for a while, so that some data can be saved. Once a few days goes by, you can then start to analyze what is happening in your system…

  • Which reports have run the longest overall?
  • Of the reports that have run, which have the average longest runtime?
  • For the users in the system, who runs the most reports?
  • Of the users in the system, who have run the longest reports?

Continue reading