If you make a field required, such as the “Description” field, and you copy and paste spaces from a Word document into the “Description”, you will be able to submit the request. Essentially, you have a submitted record, where the “Description” is required but still blank. Meanwhile, if you attempt to create a request with a “Description” where you manually enter the spaces, it will not let you submit it.
Moving forward, a text field value containing only spaces and/or carriage returns will be considered as empty, and will fail the required field validation, if applicable.
After changing the name and copying a template, the name change is saved in the database for the copied template. However, it displays a “Copy of” the original name. In other words, the name stored in the database is different from what is being displayed in the TRIRIGA interface. So when you copy a template, it fetches a different name from the database and concatenates “Copy of” with that name. This seems incorrect from the front end.
Moving forward, we fixed an issue where the capital project template name was modified and then copied, but the copied template was not created with the modified name. This happens only for non-US English users only.
[Admin: To see other related posts, use the Templates tag.]
Since TRIRIGA is new territory for a lot of you out there, and I have already received various queries about this, let’s take a brief look at the correct sequence to create a new TRIRIGA classification as follows:
- 1. Create a new BO within the Classification module, and add other fields, if needed.
- 2. Set up the Publish Name (BO Mapping). Tip: For classifications, you use the Name field as the lone field in the Publish Name to prevent entering duplicate classification entries. The Name field is in the Record Information section when you click Find in the BO Mapping tool.
- 3. Save the BO.
- 4. Create an association between the new BO and itself by using Is Parent Of. This action creates an Include. Note: Create this association from within the Data Modeler, not within the Association Manager. Also, when creating Includes, ensure that the Parent BO is in the Revision in Progress state before you create the association. Otherwise, the Include is not created properly.
- 5. Publish the BO.
- 6. Revise the Classification BO.
- 7. Create an association between the Classification BO and the new BO that was created in Step 1 using Is Parent Of. This action creates an Include.
- 8. Publish the Classification BO.
- 9. Copy the triClassification form and assign the new form to the BO that was created in Step 1. Add at least the Name field to the form.
- 10. Change the label of the new form to match the label of the new BO.
- 11. In the State Family, click Find to import the other states and transitions.
- 12. In the Includes/Forms tab, add the newly created form to the Includes list. (Add it to itself.)
- 13. Publish the form.
- 14. Revise the triClassification form.
- 15. In the Includes/Forms tab, add the newly created form to the Includes list.
- 16. Publish the triClassification form.
Thus far, we have the Classification definition metadata and no Classification records exist yet. In order to create records, follow the last 2 steps as follows:
- 17. From the Classification Hierarchy Master detail view, create the local parent for the new Classification as a child of the Hierarchy root record.
- 18. Create the actual new Classification records under the local root for the new Classification.
[Admin: To see other related posts, use the Classifications tag.]
We are currently using TRIRIGA to track our real estate leasing and capital projects. Recently, we have had 2 of our member firms from 2 other countries show interest in following the same TRIRIGA practices with leasing and capital projects as we currently follow.
My question is: How best can we have the 2 countries use the same TRIRIGA product we have, but just have another instance, instead of using our instance of TRIRIGA? This way, we would have 2 different instances for both of the countries. Also, is it possible to have country-specific logins so that users from one country can get into only their country’s instance of TRIRIGA?
[Admin: This post is related to the 09.05.16 post about getting started with Portfolio data.]
To create a logical copy of your TRIRIGA database schema, use the Oracle data pump for exporting database dump files. More information can be found here in the Oracle Help Center. It is recommended to run these steps from your database server with a privileged database user, and to stop the TRIRIGA application beforehand.
(1) Create directory object in Oracle where you want to download the dump. Information on how to do this can be found here in the Oracle Help Center.
(2) Run the export command expdp as follows. Substitute the variables properly.
expdp <db_admin>/<admin_pw> DUMPFILE=<dpump_dir>:<filename>.dmp SCHEMAS=<schema_name> LOGFILE=<dpump_dir>:expschema.log
[Admin: The same article is also posted in the Watson IoT Support blog.]
The most pervasive issue I have seen overall has been problems with the source sheet. Typically, I start my Data Integrator process by building a spreadsheet with the column headers using the TRIRIGA application. Starting from the Data Integrator interface, reached from Home > Tools > Data Integrator, and using the Create Header action, you can generate a base sheet. It’s as easy as selecting the fields you want to use, and exporting a sheet to begin working with it. You also have the option to simply open Excel and type in the fields you want to use.
A known issue is encountered when copying and pasting from the application into Excel. In fact, this is one of the key points I want to make. Copying data from the TRIRIGA application, or from any other tool, into Excel, will almost invariably introduce formatting into the spreadsheet. This is the most common cause of issues with the upload process. HTML formatting information will cause problems with the upload.
The method I have found that aids in getting around this restriction is to use the Copy/Paste VALUES option when pasting data into the spreadsheet. This removes the formatting tags, and allows for a clean upload. At times, I have experimented with copying and pasting an entire spreadsheet into a new sheet, again using the VALUES option, to clean up an upload sheet prior to saving as a text file. This yields good results and has solved many issues for me.
Another area where I have encountered issues in the past is when trying to make edits to the text file after exporting it from Excel. I strongly recommend that this NOT be done. If any edits are warranted, please make the changes in the spreadsheet and re-export the text file. In fact, I would recommend deleting the original text file, and doing a fresh export each time any edits are made. This eliminates the possibility of bringing in bad data, or merging unexpected edits…
If you make a copy of a form that has the same name but a different prefix, and then upgrade, the form is not listed as a form in the Report Builder. But it will be listed, if you go to the Form Builder.
As a temporary fix, change the label of one of those forms and it will show up. We needed to sort the form labels based on lowercase strings and the pair <label, name>, so that identical labels will still be displayed. Moving forward, an issue was resolved in the Report Builder, where forms under the same module and business object, and with the same label but different names, would not be listed. Only one of the forms with the same label would be displayed.
[Admin: This post is related to the 02.24.17 post by Rob Zombron about forms missing from Report Builder.]
If you used to work on Real Estate Leases and Generate Payment Schedules before TRIRIGA 3.4.2, you know that every time you needed to copy a Payment Schedule, you would need to open the record, and click “More” > “Copy”.
Since “Copy” was the only action under that “More” button, the Development team made a decision to move this out and place it beside “Save” and “Save & Close”. The issue is that for base TRIRIGA 3.4.2/10.4.2, the “More” button was removed, but the “Copy” button was never placed in the form. It was fixed in TRIRIGA 10.4.2.1, and in the following fix packs.
So, if you are going to test TRIRIGA 10.5 to evaluate an upgrade, the “Copy” action is missing. This was a regression fixed in the most recent 10.5 fix packs.
[Admin: The same article is also posted in the IBM Support Portal. This post is related to the 01.19.16 post about TRIRIGA fix packs.]