How do you identify orphaned classes?
Been cleaning up our production 2017.1 instance of Health Connect in preparation to a move to Health Connect 2020.1 (on IRIS!)
One thing I have found I we have built up a number of old classes and other configuration files.
It would be nice to start on the new server with a clean slate.
Is there any way to identify classes that haven't been used for a long time so they can be reviewed and removed?
Kind regards,
Stephen
Could you add a little more detail on what you mean with "classes" and "used"?
If you are talking about generic ObjectScript classes and look at usage as plain invocations from any ObjectScript code, you may not be able to find that at all. If, on the other hand, you're looking for Business Services, Processes and Operations classes, there's a good chance we can pull much of that from available metadata (up to your most recent purge). Also, for persistent classes, you may be able to find whether they were recently accessed through SQL by looking into the Statement Index, but that of course only is about SQL and doesn't guarantee you they weren't used otherwise.
If you are interested in Business Services, Operations, Processes (as well as DTLs, and routing rules) as Benjamin mentioned the new Interface Maps may be of help. Interface Maps doesn't exist in 2017.1, but you could upgrade a test instance to 2020.1 to do your analysis of orphans before doing the main upgrade.
Thanks - interface maps looks cool - I'll check in 2020.1.
I meant any classes, including plain objectscript that are called by running code, but I'd like to include dtl's and 'standard' classes for business process, etc., routing rules and schema's
I'm just used to tools that identify unused methods and classes from other IDE's and I thought maybe I missed existing functionality?