The Primary Alias, and aliases, are not required for a Site entry so no need to worry about this however the below is true and maybe why they are not showing.
As a Site can be associated to more than one company, you need to ensure that if you offline the Site that it does not affect other companies.
There are a number of places that Sites can be used:
- People Profiles
- Application requests e.g. Incidents, Changes, etc.
- Potentially Approval Mappings
- SLA's - if using Site specific targets
So you would need to be vigilant when making updates to the Sites.
Hi Edison, one example of impact is:
When you drop a site and do not update the ticket user locale, when the solver try to update the ticket it will see an error msg, asking to update the user details.....for operation team, it is bad.
Do the following procedures to minimize the risk in your task:
1 - Create a site and capture the Filters and SQL logs. This gives you a more detailed view of how data is organized.
2 - Update a person's profile, add/update a site, to also see how the data is organized.
3 - Validate whether site data is part of the tickets (inc, chg, pbm ...) or is fetched from other related tables.
Thanks for taking interest in this.
We are on ROD so to gather logs we would have to log a ticket with BMC.
Any other suggestion which we can enact at the configuration level?