Problem: When you create any of the entities using TMF APIs, ensure that the ID does not contain hyphen or period. When you publish an initiative to the test workspace, the publish operation generates non-compilable java class name in the UIM project when any of the entities in the initiative has a hyphen or period in its IDs.

Solution: When you create entities using TMF APIs, you must not use hyphen or period in the entity IDs. The entities include service model, technology model, customer facing service, resource facing service, resources, and domains.

Problem: The four data elements Subject ID, Customer ID, Commercial ID, and Service Address are not generated in the cartridge generated by the DevOps engine. When you do not have these data elements as design parameters, these are not added in the service action parameters to the cartridge by default.

Solution: Four data elements Subject ID, Customer ID, Commercial ID, and Service Address are preloaded in the Data Elements application in Solution Designer. You must configure these four data elements as design parameters in those specifications for which you want to generate service action parameters by the DevOps engine. When you publish the initiative that contains these specifications, the DevOps engine adds the service action parameters in the cartridges.

Problem: When defining the delivery parameters for a specification, you cannot map the entity characteristics from the parent specification of type Feature group to the delivery parameter. You cannot select the feature group characteristic in the Source Characteristic field in the Characteristic Mapping section in the New delivery parameter drawer in the Specifications application.

Workaround: You can map the individual data elements of the feature group to the delivery parameter instead of mapping the feature group itself. You may need to create as many delivery parameters as the data elements in the feature group.

Problem: When you define a standard policy for creating a resource, Solution Designer creates the resource automatically only for logical device specification. Solution Designer does not create the resource automatically for all the other specifications.

Solution: For all the other specifications, you can define an advanced policy for creating a resource and write the implementation code in the extended designer class for creating a resource other than logical device specification.

Problem: When you define an advanced policy in the extended designer class, third party libraries are not supported.

Solution: When you write the implementation code in extended designer class, do not load the third party libraries. The DevOps engine has the supported libraries to generate the cartridges.

Limitation: In Solution Designer, domain names must have more than one character and cannot have single character.

Limitation: When you remove Associated Service Domains from technology domains, Solution Designer allows you to remove the associated service domains which may result in invalid PSR model configuration. There is no appropriate validation that disallows the removal.

You must ensure that removing an association maintains the model integrity by checking Used by tab in the technology and service domains.

Limitation: In the PSR model or specification configuration, when you click + symbol using the mouse or by pressing F2 key using the keyboard, you must use the mouse to navigate within the New component drawer or the specifications drawer that it opens. The specifications include resource facing services, resources, and locations. The + symbol appears in the canvas, component, or specification.