I’ve noticed that the triStatusCL column of the T_TRIPEOPLE table has been defined as VARCHAR2(1000) by default. Can we resize it using SQL? What’s the impact? According to my understanding, all of the classification type fields are defined in the same way, correct?
This is actually set by design, and uses a thousand characters for compatibility reasons. But there might be a size change based on platform changes in the future.
[Admin: To see other related posts, use the Character tag or Classifications tag.]
Is AutoCAD LT compatible with CAD Integrator functionality?
No, it’s not compatible. See the compatibility matrix for IBM TRIRIGA CAD Integrator/Publisher. At the bottom, the comments provide more details.
For example: “My understanding is that the CAD Integrator does not work with the LT versions of AutoCAD because LT versions do not support database connectivity and cannot use programming tools such as VBS, LISP and ObjectARX.”
[Admin: To see other related posts, use the Integrator tag or AutoCAD tag.]
Is anyone having issues publishing CAD drawings via IBM TRIRIGA Platform 3.5.2, CAD Integrator 12.1.6, and Windows 10 OS? The support compatibility matrix mentions support for IBM TRIRIGA 3.5.2 with Windows 10 OS, but it doesn’t specifically mention that CAD Integrator 12.1.6 is supported by Windows 10 OS.
IBM TRIRIGA CI 12.1.6 with Windows 10 OS is supported and should publish without issue.
[Admin: To see other related posts, use the Integrator tag.]
We have an IBM-hosted environment that will be connected to an IBM-hosted FileNet instance as the CMIS. After configuring everything, the connection is established and the containers are created in FileNet, but the actual file is not uploaded. Has anyone been able to have this integration work in their environment? Here is a snippet of the error log when CMIS integration is active…
This was most likely due to a misconfiguration on the TRIRIGAWEB.properties or CMIS side. TRIRIGA supports the CMIS 1.1 standard. IBM TRIRIGA can be configured to store documents in Enterprise Content Management (ECM) systems that support the Content Management Interoperability Services (CMIS) ECM gateway Version 1.1 of the CMIS standard, as established by OASIS.
These gateways are specific to the vendor of your particular ECM and should be installed accordingly, if one does not already exist in your organization. See the Support Matrix. IBM FileNet adheres to the CMIS 1.1 standard. So, as long as the FileNet version has support for 1.1, it is supported by TRIRIGA.
[Admin: A similar question is also posted in the triDeveloper Google group. To see other related posts, use the CMIS tag or ECM tag.]
We understand that sometimes with new TRIRIGA platform and application version releases, a new version of Crystal Server will be required (tested by IBM and supported) in order for our existing Crystal Reports to function. Deviation from the tested and supported version of Crystal Server identified in the compatibility matrix is considered to be a significant risk.
From what we have been told, the version of TRIRIGA is tightly coupled with the supported version of Crystal Server.We are looking for a better understanding of how clients who may be using a shared Crystal Server across their enterprise handles upgrades to the TRIRIGA platform. Because our business recommended the use of their enterprise Crystal Server with our existing TRIRIGA application, we would like to understand the issues and risks of going with using a shared server where the upgrade schedule (annually) differs from our TRIRIGA upgrade schedules (2 years for platform, 5 years for combined application/platform).
Are there other clients of IBM who use a shared enterprise Crystal Server? When they want to upgrade TRIRIGA, do they always have the appropriate supported Crystal Server version paired with TRIRIGA? If not, what are other accepted (if risky) solutions? Potentially, if we went with the enterprise Crystal Server, it would likely often be further ahead than the version recommended by our platform.
[Admin: To see other related posts, use the Crystal tag.]
Component API documentation for developing applications with UX Framework is deployed with your TRIRIGA server. Component documentation can be accessed via the following endpoint:
- The [tririga-hostname:port] and [/context_path] are the specific values you’d normally use to access your IBM TRIRIGA environment.
Once at the component documentation page, you can browse or search the TRIRIGA delivered components that are available on your specific platform version using the left-hand panel. Further down in the list, you can find documentation for the available third-party components delivered with the corresponding version of Google Polymer. (This version varies, based on the TRIRIGA platform version. See the Support Matrix for more information.)
In the right hand panel, the documentation provides information about the selected component, generally with sample usage, styling and an API reference. In some cases, there are also demos available. You can toggle between the Doc and the Demo for a component using the buttons in the top right of the page…
[Admin: Similar content is also found in UX Article 2: Implementing UX. This post is related to the 12.11.15 post about the UX framework.]
I’m looking for any information on what third-party tools can be integrated with TRIRIGA, specifically, ERP systems like CGI’s Momentum and other construction-based tools. I’ve looked at the IBM TRIRIGA Compatibility Matrix, but I’m sure the list isn’t as complete as the work that’s been done.
Here are a couple of links that might point you to the right people. In each post, click “Continue reading” to see the original Facebook discussion. From there, the TRIRIGA group members might offer further info. Good luck!