Object Labels and Revisions
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.
For more information, see the documents, (1) “Converting your modified TRIRIGA objects to use the TRIRIGA revisioning features and application upgrade best practices” and (2) “Best practices for upgrading your TRIRIGA applications“.
[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.]
After revising and reissuing a standard contract, the cost amount becomes cumulative against the budget.
As a temporary fix, do not revise the contract. Instead, post a change order to the contract. We needed to set the reverse transaction to “true” for 3 workflows. Moving forward, for capital projects, the standard contract will no longer double-post values after revising.
[Admin: To see other related posts, use the Costs tag or Change Orders 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’re unable to perform a Sync Full of CAD drawings if there are any people assigned to the spaces. Here’s the ci.log error:
ERROR [com.tririga.ci.sync.SyncServiceImpl](pool-1-thread-2) Sync failed.
com.tririga.ci.error.CiRuntimeException: com.tririga.ci.remote.shared.error.CiSharedException: Attach associated object could not find the association to use.
The CAD hierarchy for the custom configuration is not mapped correctly for triSubSpace. Custom business objects and forms were created for all property hierarchy items. But the existing triSubSpace CAD hierarchy node for triSubSpace was not changed. It still references “Space Mapping”, instead of “cstSpace Mapping”. This means both space mappings are part of the application definition (which have different forms). This was causing the Sync Full to fail. Updating the triSubSpace hierarchy node to point to the cstSpaceMapping will resolve this error.
[Admin: This post is related to the 09.12.16 post about a Sync failure in CI, and the 08.05.16 post about a Sync Full error in CI.]
[Admin: As a side note, with the 3.5.1 introduction of object labels and revisions, you’re not required in 3.5.1 or later to use the classic “cst” naming convention any more. For reference, here are the new naming convention best practices.]
This was seen with TRIRIGA Application 10.5.2. The final amount for the Revised Funds is being discounted twice for positive or negative values…
Check the Revised Funds value. In the client’s example, it was expected to be $900,000.00 USD as only $100,000.00 was discounted out of $1 million USD. But it was discounted twice and it showed $800,000.00 in the Revised Funds column.
It was noticed that, in 3.4.1.x, when uploading a document through the Notes & Document tab, the document will get uploaded fine. When a second record is brought up and you go to Notes & Documents, and upload a document with the same name that was previously used, the file name will be uploaded and given a . If you go to the Related Documents tab, you will see two line items in the Related Documents section.
In 184.108.40.206, when you upload the same file twice, you see one line in the Related Documents and the revision changed from 0.0 to 0.1. Both uploads show in the History tab of the record. Why is the versioning different?