SAC connections cleanup
As part of system cleanup you might be asked to delete unwanted SAC connections that were just built for testing. We couldn’t find those details in SAC, also there was no prebuilt/standard SAC report that gives connection and model lineage/dependency details or where used details.
Our SAC tenant has 25 connections. Our clients build ad-hoc AFO reports. So now the problem is users don’t want to see all the unwanted connections when building AFO report (it confuses them). It means that we have to cleanup/delete unwanted connections.
Why 25 connections:
When our client started with SAC, they had only one tenant for both developers (pre-prod) and the clients (prod). We just maintained separate folders for pre-prod and prod content. Down the line our client has got one more tenant. So now pre-prod and prod has sperate tenant each. They made made the existing tenant as prod and the new tenant as pre-prod. This way our prod tenant ended up with many (25) unwanted connections.
Also, our pre-prod has approx. 50 connections. So, we decided to cleanup pre-prod first and then the prod.
(pre-prod cleanup would work as a pilot project)
We cant blindly delete/cleanup connections as those might be used in models/stories/applications in someone’s personal folder. We wanted to figure out which all models are using the connections we wanted to delete. We tried to find out if SAC standard stories or applications in the System folder (pic1) and in the System menu/Overview (pic2) gives any such details (pic2). Overview in the pic2 was able to provide each of the connection is used in how many models but not the name of the model in which its used.
So, we thought if we can use SAC prebuilt models and build a story that might give the details we were looking for. Finally, the RESOURCE model in the pic3 was of little help and we built a story using it. The objects/fields/columns in the RESOURCE model have fields Connection name, Object Name, Object Type, Resource Name which helped us with our cleanup activity pic4. However RESOURCE model didn’t have a field that gives the folder details of the model i,e which folder that model exists in. It was also the case that multiple models had same name in our tenant. So, we have to open all the duplicate models one by one and look if model id matched with the model id (resource name column) in the story pic4. So this way RESOURCE model was helpful to some extent in our cleanup activity.
So the ones performing the cleanup activity can make use of the RESOURCE model which gives you some direction to start with.
This is my first blog. Please pardon me if the blog is not well structured. I am open for your valuable suggestions.