What are the new best practices for upgrading TRIRIGA apps?


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.

Resources

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.]

Continue reading

Advertisements

IV96536: Revising contract causes double-posted cost amount


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.]

Continue reading

Why doesn’t TRIRIGA CAD Integrator complete the Sync Full process?


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.]

Continue reading

Why aren’t service requests available after customizing form?


When submitting a Change Space or Need Space request, I see the following message when I click on the Create Draft button:

“No services are available under the Service Request section for the building. Please contact the Application Administrator.”

If you look at the triBuilding form, it does not appear to have a “Service Request” section. Where should I be looking on the building record to address the issue?

This error is happening because I changed the name of the triChangeSpace form to cstChangeSpace since I needed to customize the form. If I keep my changes in place, I can rename the form to triChangeSpace and this message does not appear. The message also did not prevent me from being able to submit the request. The form name change also prevented me from selecting the Service Request type in the form, which I think is why the message is displayed in the first place…

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. To others interested, here are the new naming convention best practices.

[Admin: This post is related to the 06.10.16 post about finding information on object labels and revisions.]

Continue reading

IV93170: Revised Funds discounted twice in capital projects


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.

Continue reading

IV90499: Uploading with the same name has different versioning


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 [1]. If you go to the Related Documents tab, you will see two line items in the Related Documents section.

In 3.4.2.5, 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?

Continue reading