We are currently using TRIRIGA 10.5.1/18.104.22.168. One of our user requests is to try and reduce the PDF size for an exported drawing from the Graphics tab. Of course, one way might be to hide a few of the layers before exporting. Apart from this, is there any other way to compress the file that is exported from the Graphics tab?
What would be the purpose of reducing the file size? (1) If you were expecting the export to run faster, that would not be possible except by turning off layers. TRIRIGA will process all the displayed graphic entities when generating the PDF. (2) If you want a smaller file size to make storage and transfer easy, then you can try using any third-party tool on the PDF file export after the fact. Note that I have no idea how compressible the graphic export is right now.
[Admin: To see other related posts, search “PDF Drawing“.]
We can’t export the graphic floor map to PDF from TRIRIGA. The system is “hanging” and not exporting. This is only happening with some drawings and only occurs when using Layer 0 from the Xref file ( xrefdwg | 0 ). If all other layers are off and a layer zero from any Xref is displayed on the graphics section, even if empty, the export will fail to complete.
The export graphic was throwing a malformed XML exception. The root cause was that there was a “1 = 1” element that got pulled in from the layout of an attached Xref onto layer 0 on that Xref. It turns out that, for any text element that contains any equals sign, the process of sending the SVG from the client to server using a Dojo API to post via a hidden input element, resulted in extra double quotes getting sent, and causing the SVG XML to be malformed.
We resolved this by pre-processing the SVG sent to the server to remove these extra double quotes, before sending it to the SVG converter. Moving forward, the export graphic will now successfully export a graphics section that includes text that contains any equals sign. Text that contains both double quotes and equals in it, will get the double quotes removed for technical reasons.
[Admin: To see other related posts, use the Xref tag or SVG tag.]
Here are several lists of reports delivered with the as-shipped TRIRIGA solution:
I’m trying to update a record using Data Integrator. But currently, I have no good results with this. The record is just added, not updated. I would appreciate it if you could show me an example of updating the value of an existing record for an employee’s email address below. I might not have understood the publish name, or the unique key of TRIRIGA.
- (1) triIdTX: 1000004: This is the system generated number at record creation. I assume it’s used as the unique key. (I am not sure if it is the publish name or not.)
- (2) triLastName: Aaaaaaaa: This is the value with the same value when creating a record.
- (3) triFirstName: Bbbbbbbb: This is the value with the same value when creating a record.
- (4) triEmailTX: email@example.com: It was not set when creating a record. And I want to set this value as an update value.
Also, let’s suppose that some values are already set to other fields of triPeople, but are not specified in Data Integrator.
You are correct that it’s adding a record because you’re not using the Publish Name. Take a look at the documentation in Application Building for the IBM TRIRIGA Application Platform 3: Data Management (3.4.x PDF p.35 | 3.5.2 PDF p.31). I confirmed the publish name in our latest release is the same as documented: Last Name + ‘, ‘ + First Name + ‘ – ‘ + ID.
[Admin: To see other related posts, use the Data Integrator tag.]
In Space Assessment, when creating a new assessment, I want to be able to save the floor plan on <triplat-graphic> as a PDF. Is it possible to do so?
There is no TRIRIGA UX feature to export a floor plan to PDF at the moment. One possible way of doing this is to create a page containing only the floor plan and use the browser (for example, Chrome) to export the page to PDF…
I am trying to pull the documents associated to a TRIRIGA record using a custom interface (web app). The objective is to convert the document to PDF format using OpenOffice, and have it downloaded to the user local machine when the end-user clicks on a particular document from the web app. This functionality worked well in TRIRIGA 22.214.171.124. When we migrated to 3.5.0, we found issues retrieving the documents. Unlike in earlier platforms where the docs are stored in the network share, in the new platform, the docs are stored in the database.
In the code side, we defined a TRIRIGA client object using TRIRIGA client factory (by providing app URL, username, and password). Then, a content object is created (com.tririga.ws.dto.content.Content), and the document ID (spec_id of the respective document, collected using JSON) is set as the record_id. After this, we invoked the download() method of the TRIRIGA client by passing the content. The result is assigned to a response object (com.tririga.ws.dto.content.Response). With the not-null response object, we are doing the conversion.
Where is the change needed to make this work in the new platform? In the TRIRIGA side or external code side?
Based on customer feedback, the PDF format of the Best Practices for IBM TRIRIGA 3.5.x System Performance is replaced with this more easily navigable wiki format. For PDF documents on earlier versions of TRIRIGA, go to the Versions tab on this page.
Best Practices for IBM TRIRIGA System Performance
Use these System Performance best practices to improve the performance of applications based on the IBM TRIRIGA Application Platform. While these guidelines provide optimal performance in the lab test environment, your environment might require different settings. The settings in this wiki can be used as a guideline or as a starting point, and then monitored and tuned to your specific environment.
TRIRIGA has a long and successful history in the world marketplace. Over the years, TRIRIGA has incorporated many new features, grown in complexity, and integrated with other complex software systems. Small, medium, and large organizations implement TRIRIGA in increasingly complex ways. For many customers, TRIRIGA is now a global, enterprise-wide implementation that is in use by thousands of users.
The larger and more complex the deployment of TRIRIGA is, the more challenging it is for you to keep TRIRIGA performing well for your users. Because some of the greatest challenges are faced by those who deploy these products across large, global enterprises, this document has a special focus on improving performance in advanced enterprise configurations…
[Admin: This post is related to the 04.08.15 post about performance monitoring tools, the 11.06.14 post about the Performance section of the wiki, and the 08.26.14 post about resolving issues.]