The existing assets will still internally point to the old schema, but when the asset details are displayed the missing schema will not show up. However if the asset is edited you will see something like:


This gives you the option to delete the invalid category by selecting the checkbox, or leaving it there.

Unless the old lifecycles explicitly references the missing schema there is no problem with them. If they use the schema as a selection condition and old assets that still have the category (even though it is deleted) will continue to use that lifecycle. But since that category cannot be selected to be added to other assets that lifecycle will not pick up any new assets.

If there are policies configured with the category it all depends on the policy. Some of the policies are written to understand the category no longer exists and others don't.

There is a minor bug in role scope display section where it displays the wrong category when the real category has been deleted. I just opened defect on that. However as long as there are assets that still are categorized with the deleted category that role will still apply to those assets.

At first the category will still show in the search filter. That is because the filter list is built and refreshed approximately every 10 minutes. So until the list is refreshed it will still show, but it will eventually disappear from the search filters.