Product ClassificationsWhen creating or editing a Services Product, users can assign a product classification. By default, the value is blank and you can select one of these classifications:
You can hide any of these classifications if your company does not use them. For more information, see Show or Hide Product Classifications. Your company can add additional product classifications. You must have a Customization Administrator license and the Administrator access role to perform this task. Use the Data Model Customization app (Specialize Data Model page) to define a new package and extension. Product Nesting (Composition Rules)Users can use the Product Nesting category for a product to define the structure based on the product classification of each node. For example, if a Services Product uses the Financial Product classification, your business practices could allow any type of other of product classification to be nested. However, if a Services Product uses the Financial Component product classification, you might not want to allow products with the Financial Product or Financial Service classifications to be nested under it. By default, there is no restriction to how you can compose the product structure. You can update the composition rules (for example, to prevent a Financial Product classification from being nested within a Financial Instrument classification). If you added additional product classifications, those classifications also show in this matrix. After adding a product classification, it automatically can be composed into any existing classification, and any classification can be nested under it. The matrix you define determines what types of products can be added in the Product Nesting category. If you change the product classification rules, any Services Products in the Release, Obsolete, Canceled, or General Availability states are not impacted. No changes are immediately made to Services Products in the Create, Draft, or Review states, however, when you promote that product to Review or Release, the app evaluates the product nesting structure with the current classification rules and will not allow the promotion if the structure is no longer valid. When defining or editing a Services Product, you do not have to select a product classification. For any Services Product without a classification, you can add any other classification to it, and you can add it to any other classification. The product classification for that product must be set before you can promote it to Review. If your choice now creates an invalid structure, the app does not allow the promotion. For example, this table shows a possible set of product classification rules:
In this example, any product classification can be nested in a Services Product with the Financial Product classification, but nothing can be nested for a Financial Instrument classification. You can nest Financial Components and Financial Instruments in a Financial Service classification (which can then be nested in a Financial Product classification). For a Financial Component classification, you can only nest a Financial Instrument. Product Content RulesYour company can define document classifications for Services Specifications and Services Documents. The classifications for these document types are defined independently. You must have a Customization Administrator license and the Administrator access role to perform this task. Use the Data Model Customization app (Specialize Data Model page) to define new packages and extensions. By default, no document classifications are defined. After you create the document classifications, you can define which document classifications can be used with which product classifications. The default value is Several, so if you do not make any changes, any document classification can be used with any product classification. For example, this table shows a possible set of document classification rules:
In this example, any document classification can be used for a Services Specification for a Services Product that uses the Financial Product classification. However, for products that use the any of the other product classifications, only Services Specifications with Pricing Documents defined as the document classification can be added. The document classifications for Services Documents work the same way, using the extensions defines specifically for Services Documents. If a Services Document or Services Specification does not have the document classification set, it can be added to a Services Product with any product classification. That is, no classification rules govern that document. Lifecycle BehaviorYou can configure how Services Management treats Services Products revisions when they are released. The default behavior is that you can have multiple released product revisions at the same time and the product owners decide when each revision is used. You can change this behavior so that only the latest (best so far) released product revision is always used. In this case, each product revision replaces the preceding revision when it is released. To implement this behavior, you choose to float on release. Float on release means that connections to a Services Product "floats" to each new release of that Services Product's revision. | ||||||||||||||||||||||||||||||||||||||||||||||||||||