TRIRIGAFEEDIA is a WordPress hub that collects feeds from multiple IBM TRIRIGA forums, blogs, and channels into a single, searchable, and social stream. Welcome!
“Best blog a TRIRIGA developer can get. Check it out!” ~Mani Sanjeevi 01.12.15
We want to integrate IBM TRIRIGA with FileNet using CMIS 1.1, but we need to know what is all of the standard metadata that TRIRIGA sends to FileNet. For example, the file name, date creation, date modification, document type, document size, TRIRIGA user owner, etc. And if it is possible to send custom metadata when creating new custom fields in the Document business object? How can we do it?
The following properties are sent as part of the integration: Document Name, Document Type, Document Path. The Owner is going to be the CMIS username as defined in the TRIRIGAWEB.properties. Further custom metadata is not supported. The purpose of the CMIS integration is to have the binary content not stored in the TRIRIGA database as BLOBs.
[Admin: This post is related to the 07.26.17 post about CMIS FileNet integration issues, and the 12.02.16 post about integrating with CMIS and ECM solutions. To see other related posts, use the CMIS tag or ECM tag.]
What we think of as the “traditional office” (clusters of cubicles in the center of a space, surrounded by private offices around the perimeter) is going away — about 70% of US offices have some type of “open office” design.
Companies are starting to go beyond just workplace space planning by investing in healthy building features and looking for ways to provide more choice and autonomy to their employees, but why? Are these strategies actually working, or are they just following trends? Is it worth it to redesign your office layout and make dramatic changes to how your employees work?
Let’s dig into some statistics that shed some light on how the workspace impacts the employee experience and what that might mean for your company:
[Admin: This post is related to the 05.17.16 post about the use of meeting rooms (and collaborative overload), the 11.01.17 post by FacilitiesNet about the inefficient use of office space, and the 06.01.18 post by FM:Systems about the employee-centric workplace. To see other related posts, use the Workplace tag.]
How long can a password be in IBM TRIRIGA?
There is no maximum password length imposed by the out-of-the-box TRIRIGA system. The encrypted password length is 500 characters. However, that encrypted length translates to about 125 characters.
[Admin: To see other related posts, use the Password tag.]
Does anyone have experience in project integration (data transfer) from an external existing project through any IBM TRIRIGA integration module? Our templates and mapping have been identified, but the question is about reproducing the overall standard when a project is created. This seems hard. In order to have this project consistent in TRIRIGA, we think that we need to be consistent with the following:
Any help and experience would be great, even if the answer is it’s too hard.
Without detailed knowledge on the user’s part, such as a fundamental knowledge of all of the application functionality, it would really be best to engage IBM Services to implement this integration. It’s not impossible, but it really would need a lot of care.
[Admin: To see other related posts, use the Integration tag.]
Starting in IBM TRIRIGA 3.5.3, the Report Scheduler application provides administrators the ability to schedule and automate reports, queries, and external reports. Administrators can select the reports to run, setup a schedule and time, and identify who receives the reports. Once scheduled, the platform will run the reports, and send the them in an email notification as an attachment.
The application is found under Tools > System Setup > Report Scheduler.
Part 1: Introduction
With 150+ IBM TRIRIGA completed projects across the globe, ValuD has the largest and most experienced team focused exclusively on IBM TRIRIGA. ValuD offers a variety of delivery models to meet our clients’ needs to ensure customer success whether for a new implementation or an upgrade. In the first of a four-part series, we share our best practices for TRIRIGA application upgrades…
Part 2: Lease Accounting
In our earlier post, we shared best practices followed by ValuD during IBM TRIRIGA upgrades. In this post, we highlight the best practices for IBM TRIRIGA 10.5.3 upgrades especially related to FASB/IASB lease accounting standards…
Part 3: Modifications & Metadata
Our earlier posts focused on IBM TRIRIGA application upgrade steps adopted by ValuD. In this post, we share best practices following the actual upgrade process…
Part 4: Record Data
In our last and final post on this series, we talk about record data tips and IBM TRIRIGA application upgrade delivery best practices that ValuD recommends…
[Admin: This post is related to the 08.07.17 post and 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.]
I am trying to export foreign language data using integration object. Alphanumeric values are exported correctly, but I cannot figure out the character set used for foreign language values, namely Japanese. The Japanese values are displayed correctly when I look at the data from a browser, and the data is stored in UTF-8 in the database. But when I export the value out to a file using the integration object, the value is no longer in UTF-8. Does anyone know what character set the integration object uses? How I can change it to UTF-8?
You are absolutely right that it should use UTF-8, but after talking to a co-working and looking at some code it does not appear that is the case. Submit a PMR and reference RTC 292380 and include that you were referred by me to submit the PMR… This issue is tracked by APAR IJ02452.