I’ve made some modifications to a handful of forms that are connected to CAD BO Mapping records (e.g. triEmployee, triSpace, triFloor, etc.). I’ve updated the label to follow the traditional TRIRIGA customization standards and relabeled them with “cst” such as “cst-triSpace”. However, in AutoCAD, when I attempt to Smart Attach and/or Publish drawings, I get an error that seems to point towards the GUI Name of the form not lining up to the CAD Mapping. How do I get CAD Integrator to pick up the same form but with a different label?
When renaming those forms, you must make a few changes to the CAD backend:
- 1. Create new CAD Mapping records that point to the new form. I recommend checking the old mapping records to make sure all fields are added properly.
- 2. If you added any required fields, I believe that they need to be added to the CAD Mapping record.
- 3. Open the CAD Hierarchy and make sure each node is pointing to the new Mapping record that you created from Step 1.
- 4. Update the form on the CAD Label Style to point to the new form.
Note: If you are on a newer platform, I recommend keeping the form names as “tri”, and using object labels to manage versioning.
[Admin: To see other related posts, use the Integrator tag or Object Label tag.]
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.
[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.]
When the user go through the Object Label Manager to access a form and change the name. The system allows you to name it the same as another form, resulting in duplicate form names. There is currently no error handling for this. Meanwhile, if you access the form from the Form Builder itself and try naming it the same as another, the system will give you an error.
The issue was that the link into Form Builder from Object Label Manager’s Labeled Objects tab was not passing in the module ID and the BO ID for the form, thus the unique name validation for the module was failing to occur. This fix obtains the the module ID and BO ID for the form selected and correctly passes it to Form Builder. Moving forward, we resolved an issue in Object Label Manager, where opening a form from a link under the Labeled Objects tab would allow a user to change the name of the opened form to a name that already existed in the form’s module.
[Admin: To see other related posts, use the Object Label Manager tag.]
Why are different object labels displayed for the object label that I selected in Object Label Manager?
In IBM TRIRIGA 3.5.2, this is new and it is working as designed… The list of objects on the Labeled Objects tab contains not only objects that currently have the object label, but also objects that previously had the object label. The current label for each object is displayed in the Current Object Label column.
[Admin: This post is related to the 06.10.16 post about finding information on object labels, and the 05.17.16 post about whether to stop renaming objects.]
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.]
When you click the hyperlink for a navigation collection, a navigation item, or a portal in the Name or Type column on the Labeled Objects tab in the Object Label Manager to open the object in its respective builder, nothing happens. When you click the hyperlink for other objects such as forms or applications, the objects open in their respective builder.
When you click the hyperlink for an object such a query, form, or application in the Name or Type column of the Labeled Objects tab for an object label in the Object Label Manager, the object opens in its respective builder. This behavior is expected. However, when you click the hyperlink for a navigation collection, a navigation item, or a portal, nothing happens.
This functionality is not supported for navigation collections, navigation items, and portals. The workaround is to open the object directly in its respective builder. For example, open a portal directly in the Portal Builder. This functionality has never been supported in the Object Migration tool either. When you click a navigation collection, navigation item, or portal link in the Object Finder panel or the Objects panel, they do not open in their respective builder. Nothing happens and no error occurs. The same workaround applies.