Webinar: Thursday, September 14, 2017, 12:00 PM – 1:00 PM Eastern Time
Join ValuD’s Lease Accounting expert team in their Sept 14th webcast for “Best Practices of Implementing TRIRIGA for FASB Compliance” and get prepared to meet your FASB compliance deadline. Register here.
[Admin: The same announcement is also posted in the LinkedIn group. To see other related posts, use the ValuD tag or FASB tag.]
Starting in TRIRIGA 3.5.3, consider converting the TRIRIGA as-shipped objects that you renamed and modified back to the TRIRIGA objects from which they originated.
The purpose of the new conversion process is to enable the objects to use the new TRIRIGA object revisioning capabilities while preserving your object modifications. When you make future modifications to the objects, the modifications are saved in object revisions. Ultimately, the object revisioning and object labeling capabilities and tools aid in the future upgrade of your TRIRIGA applications.
Resources
[Admin: This post is related to the 09.24.15 post about the best practices for configuring and upgrading TRIRIGA applications. To see other related posts, use the Best Practices tag or Object Label tag.]
IBM TRIRIGA Support works on addressing problems through a problem ticketing system where each issue is logged as an IBM Service Request (SR) or Problem Management Report (PMR). We manage problems reported via this process.
IBM TRIRIGA Support provides a support landing page titled “IBM TRIRIGA Information and Support Resources” which has a lot of very helpful information. This page has a Support Resources Home section that provides numerous links to some great resources, including a link to our IBM Service Request system, where you can open a Service Request (SR). On the “IBM TRIRIGA Information and Support Resources” page, there are also IBM Support phone numbers.
Once an SR/PMR is opened, it can be tracked for updates via the SR tool. You may also request an update at any time and this will notify the Support team to follow up with you as soon as possible.
For the most efficient IBM TRIRIGA support experience…
[Admin: This post is related to the 07.14.15 post about collecting data to resolve PMRs, the 07.07.15 post about resolving PMRs as soon as possible, and the 04.26.17 about outlining the process for SRs, PMRs, and APARs.]
In my current project, there was a suggestion to extract (updated) data from TRIRIGA, with a high frequency, and import it into some kind of data warehouse (DW) or business intelligence (BI) solution. Then, from there, perform more advanced reporting and analytics. Have other TRIRIGA solutions implemented something similar? Are there any TRIRIGA best practices or recommendations for staging area, extract-transform-load (ETL), DW, or BI reporting solutions?
[Admin: This post is related to the 12.15.16 post about the IBM TRIRIGA Connector for Watson Analytics. To see other related posts, use the ETL tag or Analytics tag.]
One of our customers is trying to apply all the best practices from the TRIRIGA documentation with different recommendations. One of them is regarding:
Their database department is telling them that if they activate this parameter, they could be doing “dirty reads”. Mainly, if they read and modify in the same tables at the same time. They said that other products control this situation. They wanted to know if TRIRIGA controls it. In case that TRIRIGA controls these situations, they will change it. Can you please confirm if they should set this parameter to ON?
TRIRIGA controls data integrity within the context of the web application. These settings for MS SQL make it behave more like Oracle and DB2, and we recommend that they be set to ON.
Our client is asking for the proper way to migrate project templates (the project itself, tasks, dependencies, roles) between instances. Object migration (they use TRIRIGA 3.4.1) doesn’t move (template) associations, so as a result, all records are created separately. Can I ask your recommendation on a right way to do it?
Are there any suggestions for tools or best practices on validating data after a legacy data load into TRIRIGA?
We are converting from 14 various legacy systems into TRIRIGA. And rather than relying on manual validation, we’d like suggestions for tools that could be used. Since the TRIRIGA database is so complex and convoluted, we thought it’d be best not to try compare scripts at the database level.
[Admin: This post is related to the 01.09.17 post about the best practice for localized data loading.]
