11 Configuring Service and Resource Specifications

Learn how to configure the details of specifications using the tabs in the Service Specifications and Resource Specifications page. You can configure relationship between the entities, define the design parameters that come from the upstream order management system, define the characteristics that match the inventory management system, map the design parameters to the entity characteristics to fulfill the order, define the design policies to assign appropriate resources from the inventory system, and define the delivery policies to send the appropriate details to the delivery systems.

Topics in this document

Configuring Relationships between Specifications

You can define the relationships between specifications in the Configuration tab in the Specifications page.

You can configure the following relationships between specifications:

  • CFS to location, resource, RFS, or another CFS

  • RFS to location, resource, or another RFS

  • Resource to location, another resource, or an RFS

You define relationships between specifications by adding components to the specification in the Configuration tab. A component represents a specific entity that is needed to complete the specification. Each specification requires at least one component to relate the other specifications. For example, a CFS requires at least one component to relate to RFS, resource, or location specification.

To configure the relationships between specifications:

  1. In the Solution Designer landing page, click the Service Specifications or Resource Specifications application.

  2. In the Service Specifications or Resource Specifications application, select a specification by searching for it.

    The corresponding specification page opens.

  3. Click the Configuration tab.

  4. Do one of the following:

    • Click Create Configuration if no configuration exists.

    • Click Edit if you already have any configuration defined, which opens the diagram in the edit mode in full screen.

    The Edit Configuration page opens.

  5. In the Edit Configuration page, click the + symbol to add a component to the configuration. You can create a new component only; you cannot search for any existing components.

    To create new components:

    1. Click New component to create a new component.

      The New component dialog opens. You can create a new component that relates to the selected specification. For example, if the selected specification is Mobile CFS, you can create a Subscriber Profile RFS component and then relate the 4G Profile RFS and 5G Profile RFS to the component. For each specification that you relate, you must create a corresponding component.

    2. Enter the following details:

      Table 11-1 New Component Fields

      Name Required or Optional Description
      Name Required Name of the component.
      Type Required Type of the component such as resource facing service component, resource component, location component.
      Minimum Cardinality Required The minimum number of instances of the component that can appear at runtime.
      Maximum Cardinality Required The maximum number of instances of the component that can appear at runtime.
      Relationship Type Required The relationship type of the component. When you create a component for Other Resource specification, select Config hierarchy as the Relationship type. See "Relationship Types" for the details on relationship types.
      Description Optional The description of the component.

    3. Click Create.

      The component is created and added to the Edit Configuration page.

      The component is added as a child of the selected specification in the configuration.

      To update the component, click the component and update the details. Whenever you update the component details, you can save the changes in the components page and click Done in the Edit Configuration page.

    See "About Components" for more information on components.
  6. After you add a component, click the + symbol on the component and select an existing specification that matches the type of the component. When you add a resource specification of type Other Resource to a component that has Relationship type as Config hierarchy, a configuration is created in the UIM run-time. Any component and the resource specification that are added as a child of the Other Resource specification, are created as configuration items in UIM run-time.

  7. Click Done.

Note:

When you select or create a resource for a component whose parent is logical device resource, and the relationship type as Exclusive, only the following resources types are available in the Resources dialog:

  • Device Interface Specification

  • Custom Object Specification

  • Custom Network Address Specification

  • IPv4Address Resource Extension

  • IPv6Address Resource Extension

  • Flow Identifier Specification

You can perform several actions in the Edit Configuration canvas. See"Features in the Configuration Canvas" for the details on the features available in the Edit Configuration canvas.

Defining Design Parameters

You define the design parameters to pass the information from the upstream order management systems to the specifications in Solution Designer. A design parameter identifies the data elements or features that apply to CFSs, RFSs, or resources. Data elements define the data that is necessary to fulfill your service. Feature group is a group of data elements that you want to use together. In the Mobile Service example, in Mobile CFS, the design parameter Service Address can be created as a feature group which has city and state as its data elements.

You also define the design action mapping for the design parameter. Design action mappings identify which of the design parameters on the specification are exposed in the signatures of operations acting on the entity. For example, the set of design parameters identified as inputs on the Add action will be part of the request to create an instance of the entity.

Design Action Mapping

A design action mapping is an operation that can be invoked on a specification in the context of a service configuration. You can define design actions for CFSs, RFSs, and resources. Action codes represent the specific types of actions permitted for each mapping. For example, an action can include a number of action codes to represent create, disconnect, and remove. Design Action Mapping includes a group of action codes, each of which can be performed against the associated specification. For example, a design parameter can affect change to a customer facing service because it includes the action codes Add, Move, and Delete.

You can select one or more of the following action codes for the design parameter:

  • Add

  • Change

  • Disconnect

  • Move

  • Resume

  • Suspend

You can specify whether a design parameter is required or optional to a specification. For each design action operation, you can select whether the design parameter will be provided as input, output, or both.

The values for each action code are:

  • Optional In/Out

  • Optional In

  • Optional Out

  • Required In/Out

  • Required In

  • Required Out

A set of design parameters is identified as required or optional for a specific action code. For example, in the Mobile Service example, if you are creating a new service order, the MSISDN design parameter is a required input parameter and also a required output parameter. The value of the MSISDN design parameter is required from the upstream order management system and that value must be passed to the downstream inventory management system to provision the service accordingly. In this case, define the design action mapping with action code as Add and the Value as Required In/Out.

After you define the design action mapping in Solution Designer, you can override the existing implementation with your custom implementation using the extended designer class. To write the implementation code for design action mapping, see "Extending Solution Designer" in Developer's Guide.

Defining Design Parameters

To define design parameters:

  1. On the Solution Designer landing page, click the desired application.

  2. Do one of the following:

    • In Service Specifications or Resource Specifications application, search and open the specification page and click the Design Parameters tab.

    • In the PSR Models application, for service model and technology model, in the Configure Model step, expand Design Parameters and select a specification.

    • In the PSR Models application, for product fulfillment model, in the Configure parameters step, expand Design Parameters and select a specification.

    The specification drawer opens with a list of defined design parameters

  3. Click Add design parameter.

    The New design parameter drawer opens.

  4. Enter a data element, name, and default value. The default value is populated from the Data Elements. You may select an existing data element or create a new one by selecting + Create Data Element. See "Creating New Data Elements" for more details.

  5. Select Persist to automatically create a corresponding characteristic and a parameter mapping. Persist is only available for newly created design parameters.

  6. (Optional) Enter Multiplicity details. This section appears only when you add a feature group as a design parameter. See "About Multiplicity" for more information on multiplicity.

  7. Add Design Action Mapping by selecting appropriate values for the action codes (Add, Change, Disconnect, Suspend, Resume, and Move) according to your business requirements.

  8. Click Add to save the design parameter.

    The design parameter is added.

You can search for associated design parameters in the Design Parameters tab. A consolidated view of design parameters and their design action mappings is available, allowing you to update mappings in the context of other parameters.

Editing Design Parameters

To edit a design parameter:

  1. In the Design Parameters tab, search for design parameters by typing the name in Search.

  2. Click the design parameter name in the Design Parameters tab.

    The Edit design parameter dialog opens.

  3. Edit the data element, name, default value and design action mapping.

  4. Click Save.

    The modified design parameter is displayed in the Design Parameters tab in the Specifications application or in the Design parameters page while configuring the model in the PSR models application.

    To edit the design action mapping, click Edit in the Design Parameters tab and change the values. Then click Submit.

Deleting Design Parameters

To delete a design parameter, click Delete in Design Parameters. On confirmation, the design parameter is deleted. Deleting a design parameter removes the data element from the specification. The data element remains in the Data Elements application so you can reuse that data element in another specification within the same initiative. To delete a data element from the application, you must navigate to the Data Elements application and delete them. See "Deleting Data Elements" for more information.

Defining Characteristics

Characteristics represent specific data properties you can associate with a service or resource in Solution Designer. For example, a characteristic can be an ID, a feature, or a telephone number. Some characteristics are added by default based on the resource type and these are referred to as hard attributes. You can define data elements or feature groups as entity characteristics for CFSs, RFSs, resources, and locations.

To define characteristics:

  1. On the Solution Designer landing page, click the desired application.

  2. Do one of the following:

    • In Service Specifications or Resource Specifications applications, search and open the specification page and click the Characteristics tab.

      The Characteristics page opens that lists the existing characteristics and the hard attributes.

    • In the PSR Models application, in the Configure Model step, expand Characteristics and select a specification.

      The corresponding specification drawer that lists the existing characteristics and the hard attributes opens.

      Note:

      You can search the list of defined characteristics for the selected specification by name.
  3. Enter the details of the characteristic:

    • Select an existing data element, or create a new one. Optionally, select or create a new feature group as a characteristic. You can create data elements or feature groups within the Characteristics tab. See "Creating New Data Elements" for more details.

    • Enter the name of the characteristic.

    • Enter a default value, if needed. The default is pre-populated from the associated data element.

    • Select Required if the characteristic must be mapped to a design parameter in the Parameter Mapping tab. This option is not available for feature group characteristics.

    • Select Changeable if the characteristic changes frequently or if you need to track its lifecycle. For example, in the Mobile Service scenario, you may mark Monthly Quota as changeable so you can audit changes over time. For CFSs and RFSs realized in UIM, Solution Designer records changeable characteristics in the Service Configuration specification.

    • (Optional) Enter the Multiplicity details. Multiplicity section appears only when you add a data element of type Feature Group as characteristic. See "About Multiplicity" for more information on multiplicity.

  4. (Optional) Enter Derived value. You can derive the value of a characteristic from the specification's design parameters and the custom text. The actual values are set in the UIM runtime environment.

    Note:

    The Derived value field is available only for characteristics of type Numeric or Text.
    To add a derived value for a Text characteristic:

    1. Click anywhere in the Derived value text box.

    2. Do one of the following:

      • Select Add design parameter to use a parameter’s value. In the Add Design Parameter task dialog, select the design parameter from the drop-down list which displays all the Numeric and Text design parameters.

      • Select Add Text (String) to add custom text.

      You may combine design parameters and text; for example, merge the Line1 and Line2 design parameters to create an Address characteristic.

    To add a derived value for a Numeric data type characteristic:

    1. Click anywhere in the Derived value text box.

    2. Do one of the following:

      • Select Add design parameter to use a value from the specification’s numeric design parameters. In the Add Design Parameter task dialog, select the design parameter from the drop-down list which displays all the Numeric design parameters.

      • Select Add Operatorto derive a value mathematically. The supported operations include addition, subtraction, multiplication, and division. This option is available only for Numeric data type characteristic.

      • Select Add Value to enter the static numeric value.

      You can mix static values and parameter values in arithmetic expressions.

  5. Click Submit.

    The characteristic is added to the specification.

Note:

At runtime, characteristic values follow this precedence:

  • The derived value (if present) takes the highest priority and overrides parameter mapping or any default value.
  • If a value is set using parameter mapping, it takes precedence over the default value.

Editing Characteristics

To edit entity characteristics:

  1. In the Characteristics tab of Service Specification or Resource Specification, click Edit.

    The characteristic is editable and you can change the details.

  2. Click Save.

    The modified entity characteristic is displayed in the Characteristics tab in the Service Specifications application, in the Resource Specifications application, or in the Characteristics section while configuring the model in the PSR models application.

Deleting Characteristics

To delete a characteristic, click Delete next to the characteristics in the Characteristics tab. On confirmation, the characteristic is deleted from the specification. Deleting a characteristic removes the data element from the specification. The data element remains in the Data Elements application so you can reuse that data element in another specification within the same initiative. To delete a data element from the application, you must navigate to the Data Elements application and delete them. See "Deleting Data Elements" for more information.

Mapping Design Parameters

You map the design parameters of a specification to the specification's characteristics and the design parameters of its child specification. When mapping parameters, the data elements and feature groups must be of the same type. For example, you must map a design parameter of boolean type to a characteristic of boolean type only. When you map design parameters to its characteristics in Solution Designer, at runtime, the value for the mapped parameter is passed from the order management system to the inventory management system to provision the services.

You can map the design parameters manually or automatically or both: You can map parameters automatically and also choose to map few of them manually.

If you have to perform any mappings other than the available mappings, you can map them by writing the custom code in the extended designer class. To write the code for parameter mappings, see "Extending Solution Designer" in Developer's Guide.

Mapping Design Parameters Manually

To map design parameters manually:

  1. In the Solution Designer landing page, click the application that you want to work with.

  2. Do one of the following:

    • In the Service Specifications application or Resource Specifications application, search and open the specification editor page and click the Parameter Mapping tab.

      In the Parameter Mapping tab, click Edit. The Parameter Mapping drawer opens.

    • In the PSR Models application, in the Configure Model step, expand Parameter Mapping and select a specification.

      The Parameter Mapping drawer opens.

  3. You can manually map all the design parameters. The Source column lists all the defined design parameters and the Destination column lists the mapped characteristics or the mapped design parameters of child entities.

    For mapping multiple design parameters manually, perform the following steps:

    1. Click Add mapping in the text box in the Destination column.

      The Select destination slider slides.

    2. Do one of the following:

      • Hover over the design parameters and click Select parameter which associates the selected parameter to the source design parameter and closes the slider.

      • Click Auto select to automatically map the specification design parameter to its own characteristics and to any child entity design parameters based on the name and referenced data element type.

    You can map a source design parameter to multiple destination parameters. You must map a feature group source parameter with only a feature group destination parameter with matching multiplicity. You must map all the required characteristics to the source design parameters.

  4. After you complete the parameter mapping, click Save.

    The parameter mappings are saved and displayed in the Parameter Mapping tab.

Mapping Parameters Automatically

To map the design parameters automatically:

  1. In the Solution Designer landing page, click the application that you want to work with.

  2. Do one of the following:

    • In the Service Specifications application or Resource Specifications application, search and open the specification editor page and click the Parameter Mapping tab.

      In the Parameter Mapping tab, click Edit. The Parameter Mapping drawer opens.

    • In the PSR Models application, in the Configure Model step, expand Parameter Mapping and select a specification.

      The Parameter Mapping drawer opens.

  3. Click Automap to map all the source design parameters with the matching destination parameters at once.

    Clicking Automap maps the design parameters and characteristics with the same name and data elements type of that source entity. It also maps the design parameters of the child specifications with the same design parameter name and data elements type. You can change the automatic mapping and manually map to a different parameter. You can map manually for some parameters and use Automap for the rest of the parameters. In such case, clicking Automap automatically maps the appropriate parameters and retains the manual mappings that have different names.

    You can click Automap multiple times as needed. If a new RFS or resource is added later, you can click Automap to automatically map the parameters of the newly added specifications.

    Click Reset to remove all the mappings and clear the data so that you can start the mappings afresh.

Defining Design Policies

Design policies define how a service or resource is provisioned in UIM. They allow you to specify logic and assignment conditions, so that at runtime, if a condition is met, the defined logic is run to assign the appropriate resources in UIM to fulfill the service. These policies typically use simple if-then rules. In Solution Designer, you can manage two types of design policies:

  • Standard Policies

  • Advanced Policies

Note:

When you define a design policy with a feature group parameter in the condition, and the feature group has a multiplicity greater than one, only the first instance is considered for condition validation.

Defining Standard Policies

Standard policies define the design and assign of service specifications and resource specifications. You can configure and assign service specifications based on design parameters, and configure and assign resource specifications based on design parameters, characteristics, and inventory groups. For example, in the Mobile Service scenario, if the State is ON, select the 5G Profile RFS; otherwise, select the 4G Profile RFS.

You can create the following types of standard policies:

  • Standard Policies for Service Specifications: Assign service specifications based on design parameters. These are the default design policies for service specifications. The specification selection policy is applicable only for resource and service specifications. The design policies created for service specifications are Specification Selection policies by default.

  • Standard Policies for Resource Specifications:

    • Specification Selection Policies: Assign resources based on design parameters.

    • Resource Selection Policies: Assign resources based on their characteristics or inventory group. The resource selection policy is applicable only for resource specifications.

      • Characteristics based: Assign resources by characteristic values. For example, select a phone number from inventory range based on Service Address.

      • Inventory group based: Assign resources based on inventory group characteristics. Only Inventory Groups with the same initiative and in Released status are available.

    • Naming Policies: Define naming logic for resource specification instances created at runtime. Naming can be based on a design parameter, ID, string, or a combination. The naming policy is applicable only for resource specifications.

    • IP Creation Policies: Define the creation of IP Subnets and IP Addresses, based on characteristics of the IP specification. This applies only to IPv4Subnet and IPv6Subnet specifications. The IP Creation policy is applicable only for IPv4Subnet and IPv6Subnet specifications.

Defining Standard Policies for Service Specifications

You can define standard policies for Service specifications which are specifications selection policies by default.

To define standard policies:

  1. On the Solution Designer landing page, click the desired application.

  2. Do one of the following:

    • In Service Specifications applications, search and open the specification editor page and click the Design Policies tab.

      The Design Policies page opens.

    • In the PSR Models application, in the Configure Model step, expand Design Policies and select a service specification.

      The Design Policies drawer opens.

  3. In Design Policies tab, click the Add drop-down and select Standard policy.

    The New standard policy page opens.

  4. Enter the policy name and description.

  5. Select a component in the Component drop-down. The Component drop-down lists only those components that are related to the selected service specification.

  6. Select a default value in the Default Value drop-down that lists the specifications related to the chosen component.

  7. Add conditions in the Conditions section:

    1. Drag and drop the design parameters from the Parameters panel. The Parameters panel displays the design parameters for the selected specification.

    2. Select the operator from the available operators. The available operators are Contains, Equals, Not equals, Equal ignore case, Contains ignore case, and Not equal ignore case.

    3. Select or enter a value in the Select Value field that must be validated with the actual value. Select a value if you have to define valid values for the parameters or enter a value if you do not have valid values defined for design parameters.

      Multiple conditions within a group require all conditions to be met for the corresponding Then action to run.

  8. In the Then drop-down, choose Create or Select:

    • Create: Creates the chosen specification at runtime.

    • Select: Uses an advanced policy or resource selection policy from the Select policy drop-down.

    The then part of the condition is displayed based on the component that you select. If you select an RFS component in the Component drop-down, the Then clause is displayed with RFS.

    Note:

    If you use Select, an appropriate advanced or resource selection policy must exist for the entity.

  9. (Optional) Click Add New Group to define additional condition groups. The first group whose conditions are met will trigger its Then clause.

  10. Click Add.

    The standard policy is listed in the Design Policies page.

Defining Standard Policies for Resource Specifications
You can define the specification selection policies, resource selection policies, and naming policies for the resource specifications.

Note:

When you create a standard policy for a Logical Device or Logical Device Account resource specification, Solution Designer can create the resource automatically.
Defining Resource Selection Policies

You can define the specification selection standard policies, resource policies based on its characteristics and the inventory groups. The resource selection policy is applicable only for resource specifications.

For specification selection standard policies, see "Defining Specification Selection Policies".

For characteristics based resource selection policies, see "Defining Characteristics Based Resource Selection Policies".

For Inventory group based resource selection policies, see "Defining Inventory Group Based Resource Selection Policies".

Defining Specification Selection Policies

To define specification selection standard policies for resources:

  1. On the Solution Designer landing page, click the desired application.

  2. Do one of the following:

    • In Resource Specifications applications, search and open the specification editor page and click the Design Policies tab.

      The Design Policies page opens.

    • In the PSR Models application, in the Configure Model step, expand Design Policies and select a resource specification.

      The Design Policies drawer opens.

  3. In Design Policies tab, click the + drop-down and select Standard policy.

    The New standard policy page opens.

  4. Select Specification selection as the Standard policy type. The Standard policy type is available only when you create a standard policy for resource specification.

  5. Add conditions for the specification selection policy. See "Defining Standard Policies" to add conditions for the specification selection policy.

  6. Click Add.

    The standard policy is listed in the Design Policies page.

Defining Characteristics Based Resource Selection Policies

To define Characteristics Based Resource Selection Policies for resources:

  1. On the Solution Designer landing page, click the desired application.

  2. Do one of the following:

    • In Resource Specifications applications, search and open the specification editor page and click the Design Policies tab.

      The Design Policies page opens.

    • In the PSR Models application, in the Configure Model step, expand Design Policies and select a resource specification.

      The Design Policies drawer opens.

  3. In Design Policies tab, click the + drop-down and select Standard policy.

    The New standard policy page opens.

  4. If you are creating a standard policy for a resource specification, select Resource selection as Standard policy type. The Standard policy type is available only when you create a standard policy for the resource specifications.

  5. Select Characteristics based as Selection rule.

  6. Enter the name and description.

  7. In the Settings section, select All or Any in the If clause. Select All if all the conditions must be met to select a resource. Select Any if any of the conditions can be met to select a resource.

    To add conditions:

    1. Drag and drop the characteristics from the Characteristics panel on the right. The Characteristics panel displays all the hard attributes and the user defined characteristics for that specification.

    2. Select the operator from the available operators. The available operators are Contains, Equals, Not equals, Equal ignore case, Contains ignore case, and Not equal ignore case.

    3. Select or enter a value based on characteristic type. The value that you enter is validated with the actual value. Select a value if you have to define valid values for the characteristics or enter a value if you do not have valid values defined for design parameters.

      When you add more than one condition, at run time, the first available resource is selected based on the resource type and the conditions that are met. For example, if the design policy is created for logical device resource and the conditions are entered as id Equals VMS and name Contains Voice, in UIM, the first available logical device with id as VMS and name that contains Voice is selected.

  8. Click Add.

    The standard policy is listed in the Design Policies page.

Note:

You must associate the resource selection policy to any of its parents' specification's standard policy to select an appropriate resource.
Defining Inventory Group Based Resource Selection Policies

To define resource selection standard policies for resources:

  1. In the Solution Designer landing page, click the application that you want to work with.

  2. Do one of the following:

    • In Resource Specifications applications, search and open the specification editor page and click the Design Policies tab.

      The Design Policies page opens.

    • In the PSR Models application, in the Configure Model step, expand Design Policies and select a resource specification.

      The Design Policies drawer opens.

  3. In Design Policies tab, click the + drop-down and select Standard policy.

    The New standard policy page opens.

  4. If you are creating a standard policy for a resource specification, select Resource selection as the Standard policy type. The Standard policy type is available only when you create a standard policy for resource specification.

  5. Select Inventory group based as Selection rule.

  6. Select Inventory group. The Inventory group drop-down list displays all groups with the same initiative as the selected specifications and those currently in the Released status.

  7. Enter the name and description.

  8. In the Settings section, select All or Any in the If clause. Select All if all the conditions must be met to select a resource. Select Any if any of the conditions can be met to select a resource.

    To add conditions:

    1. Drag and drop the characteristics from the Characteristics panel on the right. The Characteristics panel displays all the hard attributes and the user defined characteristics for the selected Inventory group.

    2. Select the operator from the available operators. The available operators are Contains, Equals, Not equals, Equal ignore case, Contains ignore case, and Not equal ignore case.

    3. Select or enter a value based on characteristic type. The value that you enter is validated with the actual value. Select a value if you have to define valid values for the characteristics or enter a value if you do not have valid values defined for design parameters.

      When you add more than one condition, at run time, the first available resource is selected based on the resource type and the conditions that are met.

  9. Click Add.

    The standard policy is listed in the Design Policies page.

Note:

You must associate the resource selection policy to any of its parents' specification's standard policy to select an appropriate resource.
Defining Naming Policies

You can create a naming policy only for resource specifications.

To define a naming policy for resource:

  1. In the Solution Designer landing page, click the application that you want to work with.

  2. Do one of the following:

    • In Resource Specifications applications, search and open a resource specification and click the Design Policies tab.

      The Design Policies page opens.

    • In the PSR Models application, in the Configure Model step, expand Design Policies and select a resource specification.

      The Design Policies drawer opens.

  3. In Design Policies tab, click the + drop-down and select Standard policy.

    The New standard policy page opens.

  4. Select Naming as the Standard policy type.

    Enter the name and description.

  5. In the Settings section, select Type as Design Parameter, ID, or String. When you select Design Parameter, select Value from the design parameters defined for that specification. You can specify to use the automatically generate IDs using ID type or specify a constant text that must be added to the name using String type.

  6. Click Submit to add the settings to the naming policy.

    The naming policy can have multiple settings and any new settings that you add are appended to the naming preview. Naming preview section displays the preview of the naming policy. For example, the naming preview displays <ID>naming policy string<DE-DownloadSpeed1> which means that there are three settings added to the naming policy and they are ID, string, and design parameter.

  7. Click Add.

    The standard policy for naming is listed in the Design Policies page.

    Note:

    You can have only one naming policy for a resource. If you add a new naming policy, you may choose to overwrite the existing policy.
Defining IP Creation Policies

The IP Creation policies creates the IP Subnets and IP addresses. This policy is available only for IPv4Subnet Resource Extension and IPv6Subnet Resource Extension specifications.

To define IP Creation Policies for resources:

  1. In the Solution Designer landing page, click the Resource Specifications application

  2. Search the preloaded IPv4Subnet or IPv6Subnet specification editor page.

  3. Revise the IPv4Subnet or IPv6Subnet specification. See "Revising Resource Specifications" for information on revising IPv4Subnet and IPv6Subnet specifications.

  4. Click the Design Policies tab.

  5. click the + drop-down and select Standard policy.

    The New standard policy page opens.

  6. Select IP creation as the Standard policy type.

  7. Enter the name and description.

  8. In the Conditions section, select All or Any in the If clause. Select All if all the conditions must be met to create the IP resources. Select Any if any of the conditions can be met to create the IP resources.

    To add conditions:

    1. Drag and drop the characteristics from the Characteristics panel on the right. The Characteristics panel displays all the hard attributes and the user defined characteristics for that specification.

    2. Select the operator from the available operators. The available operators are based on the characteristics type. The operators include Contains, Equals, Not equals, Equal ignore case, Contains ignore case, and Not equal ignore case.

    3. Select or enter a value based on characteristic type. The value that you enter is validated with the actual value. Select a value if you have to define valid values for the characteristics or enter a value if you do not have valid values defined for design parameters.

  9. In the Then create drop-down, select the Entity. Select IPv4Subnet or IPv4Addresses if the selected specification is IPv4Subnet Resource Extension specification. Select IPv6Subnet or IPv6Addresses if the selected specification is IPv4Subnet Resource Extension specification.

    • If you have selected IPv4Subnet or IPv6Subnet in the Entity drop-down list, enter Quantity and Prefix length. Quantity defines the number of subnets that must be created at runtime and Prefix length identifies the Classless Inter-Domain Routing (CIDR) in which the subnets must be created.

    • If you have selected IPv4Address or IPv6Address, enter Start address and optionally End address. If you enter an end address, the IP addresses between the start address and the end address are created contiguously.

  10. Click Add New Group to add more conditions and enter the conditions accordingly. When you add multiple groups, the group that meets all the specified conditions first is considered and the corresponding Then is invoked.

  11. Click Add.

    The standard policy is listed in the Design Policies page.

Note:

You must associate the IP creation policy to any of its parents' specification's standard policy to select an appropriate IP resource.

Defining Advanced Policies

Advanced policies in Solution Designer provide the flexibility to implement complex provisioning logic that extends beyond standard if-then scenarios.

While you define the advanced policy’s structure in Solution Designer, a developer implements the logic in Design Studio using the extended designer class. Solution Designer combines both standard and advanced policies to build a complete solution.

For example, in the Mobile Service scenario, you may require an advanced policy such as: Select the UDR in the same state as the 5G Profile RFS.

To define an advanced policy:

  1. On the Solution Designer landing page, click the application that you want to work with.

  2. Do one of the following:

    • In Service Specifications or Resource Specifications application, search and open the specification editor page and click the Design Policies tab.

      The Design Policies page opens.

    • In the PSR Models application, in the Configure Model step, expand Design Policies and select a specification.

      The Design Policies drawer opens.

  3. In Design Policies tab, click Add and select Advanced policy.

    The New advanced policy page opens.

  4. Enter the policy name, description, component, and default value. The Component drop-down lists only those components related to the selected specification. The Default Value drop-down lists the specifications related to the selected component.

  5. Enter clarifying notes regarding the policy in the Notes tab. For example, in Mobile Service example, you can enter the notes as Select UDR in the same state as RFS.

  6. Click Save.

    The advanced policy is listed in the Design Policies page with the status In Progress. After you add the advanced policy implementation assets in the General Information tab, the advanced policy status moves to Ready.

Procedure for Setting up an Advanced Policy
Perform the following steps to set up an advanced policy:

  1. Add the advanced policy in Solution Designer, and include explanatory notes in the Notes tab. These notes will be inserted as comments within the generated extended designer Java class when you publish the initiative.

  2. Publish the initiative that is in Advanced Configuration status to generate Design Studio workspace. See "Publishing Initiatives to Generate Design Studio Workspaces" for more information on how to publish an initiative to the generate Design Studio Workspace.

    After a successful publish, the requested Design Studio workspace is generated.

  3. Download the Design Studio workspace from the Publish operation that is in the Simulated Success status.

  4. Import the Design Studio workspace into Design Studio Eclipse environment. See "Importing Projects" in Design Studio Modeling Basics Guide for more information on importing the workspace into Design Studio.

  5. In the Design Studio project, you will find a base class and an extended designer class. Write the advanced policy implementation in the extended designer class using the notes as reference comments. Compile your code as needed. See "Extending Solution Designer" in Developer's Guide on how to define advanced policy implementation.

  6. Use Object Store Utility to update the designer classes, helper classes, and third-party libraries information in Solution Designer. See "Working with Object Store Utility" in Developer's Guide for information on how to work with Object Store Utility.

  7. Transition the initiative to the Functional Testing phase.

  8. Republish the initiative to Test workspace and the DevOps engine builds the test cartridge including the implementation code in the location specified in Link in the Advanced policy implementation assets section. See "Adding Advanced Policy Implementation Assets" for adding advanced policy implementation asset details.

Editing Design Policies

To edit a design policy:

  1. In the Solution Designer landing page, click the application that you want to work with.

  2. Open the specification in the Service Specifications, Resource Specificationsapplication, or in the Configure Model step in the PSR Models application.

  3. In the Design Policies tab or the Design Policies drawer, click the design policy to be edited.

    You can edit the details of the policy.

  4. Click Save.

    The modified policy is displayed in the Design Policies tab in the specifications editor page or in the design policies while configuring the model in the PSR models application.

Deleting Design Policies

To delete a design policy, click the delete icon for the policy in the Design Policies tab. On confirmation, the design policy is deleted from the specification.

Replaced Connections with External Systems

The External Systems module is introduced to define the applications that Solution Designer connect to in order to perform actions. In a workspace, you can add the external systems of type OSM and UIM as participants. Launch is also an external system, however, it does not function as a workspace participant. In this release, Connections is replaced by External Systems.

For more information, see "Managing External Systems" in Solution Designer User's Guide.

Editing Delivery Policies

To edit a delivery policy:

  1. Open the specification in the Service Specifications application, the Resource Specifications application, or in the Configure Model step in the PSR Models application.

  2. Click the delivery policy to be edited.

    You can edit the details.

    Note:

    You cannot edit the delivery type if the delivery parameters have been defined.

  3. Click Save.

    The modified policy is displayed in Delivery Policies in he Service Specifications application, the Resource Specifications application, or while configuring model in the PSR Models application.

Deleting Delivery Policies

To delete a delivery policy, click Delete. On confirmation, the delivery policy is deleted.

Automatic Creation of Resources Using Advanced Policies

Problem: When you define a standard policy for creating a resource, Solution Designer automatically creates the resource only for the following specifications:

  • Logical Device Specification

  • Logical Device Account Specification

  • Custom Network Address Specification

  • Custom Object Specification

  • Device Interface Specification

  • Flow Identifier Specification

  • IPv4 and IPv6 Address and Subnet Specifications

  • Telephone Number Specification

A Device Interface Specification is created automatically only when it is related to a Logical Device Specification that has a standard policy for automatic creation. Solution Designer does not create resources automatically for any other specifications.

Solution: For all the other specifications, you can define an advanced policy for resource creation and implement the required logic in the extended designer class.