updateCategoryHierarchy
- Description
- This transaction updates a category hierarchy. This transaction can be used as a coarse-grained transaction to add or update one or more categories, category relationships, or category entity spec uses.
- Web Services
- Operation name: updateCategoryHierarchy
- Example
- Update the description and end date of a category hierarchy.Run a coarse-grained transaction that will make the following updates on an insurance provider's product category hierarchy:
- Add a new Whole Life category.
- Update the description of an existing Term category.
- Update the end date of an existing category relationship between the Life Insurance and Term categories.
- Add a new category relationship between the Life Insurance and Whole Life categories.
- Update the start date and end date of the category hierarchy.
- Usage information
- For more information on category hierarchies and related rules,
see the addCategoryHierarchy transaction.
You can only inactivate a category hierarchy if there are no active categories in the hierarchy, and no products actively associated with the categories.
Localized content can be added or updated for the CategoryHierarchyName and CategoryHierarchyDescription elements.
When using this transaction as a coarse-grained transaction, the following transactions may also apply: - Preconditions
- The category hierarchy must exist
- Mandatory input
-
- CategoryHierarchyId
- CategoryHierarchyLastUpdateDate
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- Not applicable
- Request message
- <TCRMTxType> updateCategoryHierarchy
<TCRMTxObject> CategoryHierarchyBObj
<TCRMObject> CategoryHierarchyBObj
with optional business objects: - Response objects
- CategoryHierarchyBObjwith optional business objects:
- Special note
- Not applicable