3 Limitations and Restrictions

This chapter describes the limitations and restrictions that apply to the OSM-SCD integration, including considerations for OSM release 8.0.x and SCD release 8.3.x. It explains the system constraints, supported features, and specific guidelines you must follow during deployment and operation.

Limitations and Restrictions

This topic describes the limitations and restrictions for OSM release 8.0 and SCD release 8.3. Consider the following limitations when working on these releases of OSM and SCD.
  • Orders submitted to OSM via the TMF REST API must contain values for all desired product characteristics, even for those that have been modeled with a default value in SCD. Failure to submit orders this way will result in those characteristics being deemed missing or empty.
  • You must not model Product Specifications with characteristics that are complex data structures (Feature Groups in Solution Designer).
  • You cannot retire a capabilities cartridge that has moved to production.
  • You cannot use special characters in the value of a routing rule condition. For example, if "Australia & New Zealand" is one of the enumerated values on a product specification attribute, then you cannot use them in the conditions of a routing rule.

DevOps Considerations

This topic describes the DevOps considerations that you need to keep in mind while working on OSM and SCD.
  • SCD Integration Callback: OSM Cartridge Assembler (OCA) uses a single Solution Designer URL for callbacks. OSM retrieves required data through this callback during cartridge assembly. An OSM cloud native instance can only interact with one Solution Designer instance.
  • Version Digit Ownership: Version Digit Ownership: During dynamic cartridge assembly, OCA manages the last field of the 4 field cartridge version. This ensures cartridge versions are unique and can be be mapped to initiative publishes.
  • OSM Workspace: You can connect multiple OSM instances to one Solution Designer instance. Each OSM instance operates in a separate workspace. You can support different stages such as development, quality assurance, and user acceptance testing.

Miscellaneous Considerations

This topic describes the miscellaneous considerations that you need to keep in mind while working on OSM and SCD.
  • OCA Cartridge Manifest Exposure: OCA provides a dedicated GET endpoint that lists manifests for each loaded capabilities cartridge. The returned JSON document can contain multiple manifests. However, Solution Designer imports only one manifest at a time. Therefore, you must edit the JSON file to separate each manifest into its own document before importing, if the OCA is to be used as the source of the capabilities cartridge manifest (instead of direct communication between the Solution Developer and the Catalog Administrator).
  • Undeploying a Cartridge from OSM: In non-production environments, you can take down the cloud-native instance, delete and recreate the OSM schema, and restart the instance. This purges the database of all orders and previously deployed cartridges.

    Note:

    You should take this action only when nothing needs to be preserved.
    In production environments, where purging the entire database is not an option, you can use the cloud native toolkit to remove specific cartridges. You can add the cartridge entries to the specification file, set the fast-undeployed state, and run synchronization. This process undeploys cartridges with precise control.
  • SCD Publish Number: When you reinstall SCD as a fresh environment, all the database records are deleted and the SCD publish counter resets. When this happens, you may end up publishing to an OSM instance using an operation ID that was used on this OSM instance previously. Currently you also need to wipe OSM workspaces when the Solution Designer counter resets. This action keeps the operation IDs aligned between the applications.
  • Decomposition Rules: In Design Studio, you are able to create decomposition rules for a single target order component. This allows different conditions to be used during different stages of decomposition. In Solution Designer, there is only one rule and the configuration applies to two target order components - system and granularity. It is not possible to use different conditions for each of these targets.