What are the Oracle Database settings for 10.5.2 and 3.5.2?

I wanted to see if anyone has set up the following settings in an Oracle Database for TRIRIGA 10.5.2 and 3.5.2:

  • 1. NLS_LENGTH_SEMANTICS: Should this be set to CHAR? In our current production environment, it’s set to BYTE, but the TRIRIGA support documentation says that this can lead to data loss, so they recommend using CHAR.
  • 2. NLS_CHARACTERSET: This is set to WE8ISO8859P1 in our current production environment, but the support document says that it must be UTF-8 or UTF-16.
  • 3. Block size: This is set to 8k, but the documentation recommends using 16k.

For (1) and (2), if you never want to store multibyte characters, then what you have is fine. But if you do, then you must use what the support documentation suggests.  Once you have your database created, it is difficult and time-consuming to change it, and it needs to be done outside of TRIRIGA. As for (3), I would encourage you to use 16k, since it will allow you better throughput and paging, unless you have a strong reason why you need to stay at 8k.

[Admin: This post is related to the 04.04.16 post about database character settings. NLS refers to National Language Support parameters in Oracle. To see other related posts, use the Multibyte tag, MBCS tag, or NLS tag.]

Continue reading

How do you set up a Group object to leverage query sections?

In the IBM TRIRIGA 3.5.3 and 10.5.3 release, the Group object was redesigned to leverage query sections, instead of a single large smart section. The query sections improve the performance and usability of the Members tab by paginating the results, and providing filtering capabilities. These application changes are a part of the IBM TRIRIGA 10.5.3 application upgrade object migration (OM) package, but can be applied to systems running older application versions.

To help anyone who would like to apply the Group enhancements to an environment not running 10.5.3, the Group_Query_Enhancement_10.5.3.zip can be downloaded from this wiki. This is an unsupported object migration (OM) package that includes the Group form, queries, and workflows that were created to enhance the application. This OM package can be imported into an environment running on the 3.5.3 platform release.

Note: This enhancement requires the 3.5.3 platform release for the “Add” and “Delete” functions to work within the query section. There are new custom tasks that are called by workflows that handle the adding and removing of group member records, when users or groups are selected. Before applying this OM to a production system, the OM package should be tested in a test or development environment first.

[Admin: This post is related to the 03.07.16 post about best practices for managing your security groups. To see other related posts, use the Security tag.]

Continue reading

UX: How do you use pagination in triplat-query and triplat-ds?

I’m trying to use the pagination feature of triplat-query, but I can’t access the items in each page. I followed the code from the documentation and see the page number in my currentPage variable. Is there anything else I need in the triplat-ds in order to use it? The {{people}} is displaying all people in this case.

<triplat-ds id=”peopleDs” name=”people” data=”{{people}}”>


<triplat-query-page id=”peopleDsPage” size=”50″ current-page=”{{currentPage}}” total-pages=”[[totalPages]]”>

<triplat-query-filter name=”firstName” operator=”contains” value=”{{searchValue}}” ignore-if-blank>

<triplat-query-sort name=”firstName”></triplat-query-sort>



// go to the next page

// go to the previous page

Continue reading