You can modify the type's display name, description, icons and advanced options. You cannot modify the type's Schema Name or its Namespace property. These two properties are set when the type is created and cannot be changed thereafter.You can modify the type's display name, description, icons and advanced options. You cannot modify the type's Schema Name or its Namespace property. These two properties are set when the type is created and cannot be changed thereafter.With respect to attributes:You can add new optional attributes to the type at any time.You can add new required attributes if there are no existing instances of the type in the registry. If there are existing instances of a type, you can add a new required attribute of type slot or classification, but not of type relationship or file.If you add a new attribute, regardless of whether it is optional or required, no automatic update of existing instances takes place. This prevents the potential degradation of performance that could arise from the automatic update of a large number of instances.You cannot modify the data type for an attribute, but you can modify many of an attribute's other options. Be aware that certain attributes are not permitted if assigned (that is, non-empty) instances of the attribute are present in the registry. For information about the kinds of changes you can make to an existing attribute, see the property and option descriptions in Define Attributes for a Type.You cannot delete an attribute from a type if an instance of the type exists with a value assigned to the attribute. In such a situation, you must first remove the attribute's value from each such instance before you can delete the attribute.A sub type inherits all of its attributes from its base type. To add new attributes to a sub type, you do one of the following:Add the attributes to profiles of the base type and inherit the profiles in sub type, ORClone the profiles of the base type and then add the attributes to the cloned profiles in sub type.You cannot delete attributes or edit the properties of attributes within the inherited profiles in the sub type. However, you can delete and edit attributes within cloned profiles in the sub type.You can add, modify, delete, rename, and reorganize the profiles associated with a base type at any time.You can modify, delete, rename, and reorganize the base type profiles associated with a sub type at any time, if the profiles are cloned from the base type.You cannot modify, delete or rename the base type profiles associated with a sub type, if the profiles are inherited from the base type.Modifying the cloned profiles and attributes in a sub type will not affect the profiles and attributes in the base type.When recloning the base type profiles within a sub type, any new attribute that is added to the base type, and any attribute that is already deleted from the sub type but still available in the base type, will be cloned in the sub type.Recloning the base type profiles within a sub type does not affect the existing attributes in the sub type.Beginning with version 9.9, CentraSite provides the ability to define consumable asset types for an asset type. If you are upgrading to CentraSite 9.9 from a version of CentraSite that did not support the definition of consumable types, CentraSite assigns each virtual asset type (Virtual Service, Virtual XML Service, Virtual REST Service) a default consumable type definition for the User, Group, and Application asset types.You cannot remove a consumable type from an asset type definition if an instance of the consumable type is already registered as consumer of an instance of the selected type. In such a situation, you must first unregister each such consuming instance before you can remove the consumable type.Important: | If you are modifying one of the predefined asset types installed with CentraSite, review the information in Predefined Asset Types in CentraSite before you begin. It explains the kinds of modifications that you can make to the predefined types.If you are using CentraSite in conjunction with other software products, for example, the products of the Software AG webMethods Product Suite or a third-party product, those products can add their own asset types to CentraSite. Be aware that CentraSite treats these types as user-defined custom types, which can be modified by an administrator with the appropriate permissions (just like any other custom type). Modifying or deleting these types in CentraSite can lead to inconsistencies or errors in the product that uses the type. For example, if you modify or delete a type that is used by the webMethods Product Suite, components such as the webMethods Integration Server may no longer be able to publish assets to CentraSite. To prevent these types of errors, do not modify or delete any asset type on which other Software AG components or third-party products depend. |
