Troubleshooting
Problem
The "Validate Classification" action is not working as expected. It seems to be working fine at a taxonomy level, but not at a category level, as it is supposed to do.
To reproduce it:
- Import the file exported by the customer contaning the custom taxonomy and categories he defined
- Create a Design/Change-Time Policy
- applied for Virtual services (Pre-Update)
- Select all organizations
- Validate Classification action
- from scope ensure that "Apply policy to objects that meet the following criteria" has "Classification" for category "Virtual Service"
- Action List --> Edit action
- Taxonomies --> Select one of the ending categories belonging to the taxonomy you imported (Runtime->Development, for instance).
- Save and activate.
- Edit an existing VS and try to add it a new classification.
- If you add a category belonging to a taxonomy not being the one the category defined in the policy belongs to, that is, one of the standard ones (Countries->whatever), the expected error is returned.
- If you add any category belonging to the taxonomy you imported, you are allowed to save the VS, even if you selected a category different to the one specified in the policy.
It looks like the policy is considering the taxonomy for the validation, instead of the category.
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
20 March 2025
UID
ibm17208380