UX: Is there a way to attach files in the Space Management app?


Is it possible to add attachments in the Space Management app? For example, if I click a button on the website, then a form opens for me to choose some file from my local PC. Then I can upload the file to the server. I can also check the file later. If it’s possible, which component should I use?

Yes, it is possible. Use the <triplat-file> component available for the UX Framework. It is used for uploading, downloading, and displaying binary files. You can read more on the <triplat-file> and other components from the documentation pages on your TRIRIGA server: http[s]://[tririga-hostname:port][/context_path]/p/web/doc.

The <triplat-file> component was introduced in TRIRIGA 10.5.2. Here is a link to the release notes. Some UX apps that are currently in development for a future release will make more use of this component, for example, to upload images or photos on comments.

[Admin: This post is related to the 03.08.16 post about modifying the Space apps, and the 12.21.16 post about Space Assessment documentation.]

Continue reading

Can an integration object send web service data with attachments?


We are looking for a way to send web service data including attachments (binary objects). Can an integration object help with that? If not, what else? OSLC or CBA? We need to send requests to web service through digitally signed mail…

The attachment will be generated by BIRT report and stored in binary fields. Then we’ll send it via integration object (web service). The binary field in the output is represented as a DM_CONTENT (Document Manager Content) ID… As I understand it, we can use the keyword “CONTENT” in the data map when using the database scheme, but it doesn’t work for web services. How can this be solved?

Not sure about using the TRIRIGA integration object or Connector for Business Applications (CBA), but it looks like OSLC has an API for this.

Continue reading

How do you access documents in TRIRIGA Document Manager via URL?


Can I access a document stored in the IBM TRIRIGA database via a URL address? I need to get some documents out of a valid IBM TRIRIGA session.

The IBM TRIRIGA platform stores documents in binary large object (BLOB) fields. They are not available in typical operating-system folder or directory structures. To access these documents, you need to login to IBM TRIRIGA and open the Document Manager. There is no direct URL to get into the BLOB field. The document is stored in a way that it cannot be read from a regular browser. You need to use Document Manager to read the documents stored in these BLOB fields. Some forms may have links to Document Manager that load specific documents from BLOB fields.

If the company uses an ECM that supports CMIS, such as Documentum or IBM FileNet Content Manager, you can enable the CMIS in the TRIRIGA Application Platform so that files and folders can be managed by using the TRIRIGA Document Manager and then stored in the ECM. You enable CMIS by setting the CMIS properties in the TRIRIGAWEB.properties file, either on the server or in the IBM TRIRIGA Administrator Console. You must restart the server for the changes to the TRIRIGAWEB.properties file to take effect. After CMIS is enabled, the ECM administrator can proceed to configure the ECM settings as necessary…

[Admin: This post is related to the 12.02.16 post about integrating with CMIS or ECM solutions, the 06.09.16 post about using an ECM solution instead of Document Manager, and the 04.13.16 post about uploading 6500 locations with several attachments each.]

Continue reading

When will TRIRIGA integrate with other CMIS or ECM solutions?


I know that the TRIRIGA Document Management tool was not developed nor intended to be a full-fledged document management system. However, some clients have a need for a more robust document management system for controlling their CAD drawings. Are there any efforts to integrate TRIRIGA with other document management tools? Or are changes being made to implement a third-party document management tool within TRIRIGA? If so, has a timeline been established as to when that would occur?

IBM has announced that the upcoming release of the IBM TRIRIGA Application Platform, version 3.5.2, includes support for Content Management Interoperability Services (CMIS), providing integration between the IBM TRIRIGA document manager and enterprise content management (ECM) implementations that support CMIS, such as IBM FileNet®. The planned availability date for electronic download is December 16, 2016.

To add to this, the initial release is a first phase of CMIS support which is primarily focused on starting to get binary content out of the TRIRIGA database schema. To keep it simple, once you establish a link between TRIRIGA and an ECM solution, and users begin uploading new documents, the binary content for those documents will be routed to the ECM while still retaining a document record in TRIRIGA. More details on this will be in the release notes.

Also note that customers have been integrating TRIRIGA with other document management tools for many years. It does not require the aforementioned CMIS enhancement. Our APIs (CBA, OSLC) offer access to upload and download binary content, and you can create dynamic links to any ECM solution from our records.

Continue reading

IV87402: Email attachments are not seen due to capitalization


TRIRIGA is not able to pick up incoming email attachments if the multi-part section of the server’s email contains the word “ATTACHMENT” in all upper-case capitalization as follows: handlePart – part.Disposition(): ATTACHMENT

It seems that the TRIRIGA Incoming Mail Agent gets the message from the email server and builds the TRIRIGA email message record. The To/From addresses are set up and the body text is there as well. But the attachments are not getting processed into the email attachment BO’s binary field and associated to the email message.

The platform does not ignore the case when checking for attachments or inline mail content. Moving forward, we fixed an issue where incoming mail attachments were not getting processed.

Continue reading