What is the best practice for deleting or retiring records?


I have some records in the classifications hierarchy. These classifications are now associated to several BOs, like building equipment and tasks. I want to delete some of the values in the classification hierarchy because they are values we do not want users to use in the future. I understand that the best practice is the change the status of the record to “Retire” for audit purposes. But if we decided to just delete those records, what is the impact to any of the associated BOs? Would I have to create a workflow to remove the associations?

There are certain classification records that are used in forms, workflows, and/or queries. If you delete one of these records that are used in the application, you will in effect, lose some application functionality. Take, for example, “triClauseType” (Lease Clause), where several of these classification values are used on the Lease Clause form to determine which sections of the clause to unhide.

I suggest a best practice would be to look in the Data Modeler for the business object of the classification you want to delete records on. Select the triNameTX field and click ‘Where Used’. If nothing comes back you should be pretty safe to make changes to that classifications record list (add, delete, modify). If you see any workflows, queries, forms, etc., come back as using this field, you’ll need to analyze each to determine if your business needs them. However, I’d suggest pushing back against the business and advise that the application requires the values in question.

[Admin: To see other related posts, use the Classifications tag or Hierarchy tag.]

Continue reading

Advertisements

Is there a way to retire all attached child records in bulk?


We are working to clean up a rather large list of child records (floors and spaces) that are attached to retired parent records (buildings). Is there an easy way to mass retire child records? Also, is there a workflow that can be run when a building is retired to avoid this issue in the future?

[Admin: To see other related posts, use the Retire tag.]

Continue reading

Can you retire a job plan to get rid of unneeded draft work tasks?


When the Operations team was changing a job plan, the wrong date was entered, and it created over 1,800 work tasks. They have since tried to retire them and they changed to Draft status. To get rid of these, can the job plan itself be retired?

[Admin: To see other related posts, use the Job Plan tag.]

Continue reading

IV96787: Retiring contract does not retire change orders or invoices


If you try to retire a contract that has a change order or invoice, the system should consider it, provide some logic to it, and/or provide a notification that you can’t retire it. The same should apply when you try to retire a change order that has other change orders or invoices associated to it.

The standard contract record that is in a Completed state cannot be retired if it has pending standard contract change orders or contract invoices associated to it. (The expectation was that the associated records would also be retired, or if not, a notification stating that they would not be retired.) Moving forward, the issue has been resolved by displaying an Attention message to the user that the standard contract cannot be retired because of the pending change orders or contract invoices. Also, the Retire and Delete actions on the change order form have been removed, so the user will not be able to retire the change order.

[Admin: This post is related to the 10.24.15 post about the behavior of contracts and change orders. To see other related posts, use the Change Orders tag.]

Continue reading

How do you avoid the tree error after deleting hierarchy records?


I’m loading data via the Data Integrator into a Classifications business object. In the first load, my data is successfully loaded. However, I notice some data mapping issues. So I delete the records from a query, then I clear cache. In the second load, my data is successfully loaded. I go into the Classifications hierarchy form and get the dreaded message:

“Please contact your system administrator. The tree control reported this error while trying to draw itself: There was an error in the database or the query definition.”

When this happens, I tell myself that I deleted the records too quickly and didn’t allow the system to reset in time. The solution is the dreaded wait time for the Cleanup Agent to process records that takes 12 hours, 1 day, 3 days, or sometimes 1 week, before all records with a TRIRECORDSTATESY is null, are removed from the database. The only workaround seems to be to increase the Cleanup Agent time. However, is there a sequence of steps I need to follow before I delete records from a hierarchy form, so that I don’t get the dreaded message each time?

Regarding your scenario of loading hierarchy records, deleting them, then reloading the same records to cause the tree control to fail, that should be considered a platform defect. I would advise you to enter a PMR, so Support can look into this issue. The tree control should never fail to render as you describe it.

To help with your issue, there is an unsupported platform feature that allows the Cleanup Agent to delete data immediately. If you add the following property to your TRIRIGAWEB.properties file and set CLEANUP_AGENT_RECORD_DATA_AGE=2, the Cleanup Agent when run will delete records that are 2 minutes old. This allows you to immediately delete a bad data load, and allows you to run it cleanly again a second time without conflicts from that data already existing in a null state.

[Admin: This post is related to the 08.11.16 post about the Organization hierarchy tree not being displayed, the 08.04.16 post about unretiring and returning records to null, and the 02.24.16 post about executing the Cleanup Agent (a.k.a. Platform Maintenance Scheduler) after retiring a record.]

Continue reading

How do you remove Area Overlay mappings in CAD Integrator?


By mistake, in TRIRIGA CAD Integrator, I created some Area Overlay mappings. Now I’m stuck with it. Does anyone know how to remove these areas? I tried to retire them, but it’s not working.

You can delete or remove the associations to these objects in TRIRIGA.

Area Overlays are just another business object in TRIRIGA, and what you’re seeing there are records you created which are instances of that object, that are associated to your floor. If you go to the Floor record in TRIRIGA (whichever floor you’re linked to), you’ll see a tab called Allocation, and then Area Overlays is a section there which allows you to remove them. 

[Admin: The same question is also posted in the main Application Platform forum.]

Continue reading