Feeding your TRIRIGA information needs

Tag Archives: JSON

Is there any way we can specify the sequence of resource attributes to appear in the JSON-formatted Get query output? We are looking for a pre-defined set of ordered resource attributes to appear in the OSLC Get query output.

You should be able to use the oslc.orderBy parameter to define the ordering of results. If you are talking about the default ordering without that parameter, then I think the query definition of the query capability should define the ordering.

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 3.3.1.2. 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?

When you run a query expecting JSON results, via the integration object external URL functionality, the modified names of the roles are not being reflected. That is, the original name is displayed in the result query. This happens for localized users only. Meanwhile, US English (US_en) users observe the proper changes when refreshing the query results…

I am new to the TRIRIGA UX Framework. I am learning Google Polymer through some online tutorials in which they are using Bower to manage packages. But I couldn’t find any tutorial on how we can use Bower in the UX Framework.

Is there any way to use Bower in the UX Framework? Or can we directly code without using Bower? I tried to push the bower.json file using the Sync command, but didn’t know how to use it. What I understood is that we can only push (or use) HTML files in the UX Framework. It will be very helpful if someone can clear these doubts.

I am working on creating scripts for the TRIRIGA application. I am using HPE LoadRunner for this purpose. As the TRIRIGA application uses GWT-RPC calls, we have some encrypted content being communicated between the TRIRIGA server and browser. We did use the web debuggers and tools, but this content is encrypted.

Do we have the option in TRIRIGA to enable it to use the JSON or any other readable format, rather than GWT-RPC, by default? It will enable us to capture the decrypted content and change the data for replay of our scripts as we need.

[Admin: This post is related to the 03.11.15 post about sharing a correlation file for LoadRunner.]

In a smart building, it is imperative to monitor the smooth functioning of facilities operations. One of the critical parameters to monitor is the temperature of the facility. IBM TRIRIGA is an integrated workplace management system (IWMS) which increases the operational, financial, and environmental performance of facilities.

With real-time sensor data, the monitoring of critical parameters, like temperature, also becomes real-time. Any deviation from the standard process, like a temperature increase, should trigger a work order. IBM TRIRIGA can be used to raise that work order. This recipe guides you on how to address such deviations using the IBM Watson Internet of Things (IoT) Platform on IBM Bluemix, and the IBM TRIRIGA platform.

The URL (https://quickstart.internetofthings.ibmcloud.com/iotsensor/) simulates the device ID which becomes an Input to the Watson IoT Node Red App. Once the device ID is put in the Node Red input node, a JSON message is sent over MQTT to the Watson IoT. Based on the temperature threshold (>45 degrees) that invokes the TRIRIGA REST API, the TRIRIGA OSLC receives the REST parameters with the JSON payload to create the work order (work task) in TRIRIGA…

The unescaped values from user input needed to be removed from the JSON array. Cross site scripting attacks in “My Reports” have been mitigated. Entering script code in a new report’s Name, ID, Header, or Tag name will no longer cause the scripts to execute after accessing the report within the TRIRIGA application.