1. Solution Designer User's Guide
  2. Configuring Service and Resource Specifications

7 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 a new component:

    1. Click New component to create a new component.

      The New component drawer 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 7-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. If you are updating a relationship type, update it first and save the changes in the components page and click Done in the Edit Configuration page. Reopen the Edit Configuration page to update the other details.

    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 hierachy, 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. Repeat the steps 5 and 6 for associating more components and specifications.

  8. Click Done.

When you select or create a resource for logical device component and select Exclusive as the relationship type, you must add only those resources with the following resource types:
  • Device Interface Specification
  • Custom Object Specification
  • Custom Network Address Specification
  • IPv4Address Resource Extension
  • IPv6Address Resource Extension
  • Flow Identifier Specification
If you add any other resource type to the logical device component, the Publish operation fails with errors. You must reconfigure to add the specified resource types to the logical device components.
You can do the following in the Edit Configuration page:

  • When you hover over the entities in the specification, Solution Designer highlights the complete relationship hierarchy for that entity.

  • To expand all the entities in the specification, click Expand All on the top left. To collapse all the entities in the model, click Collapse All on the top left.

  • To collapse the descendants for a selected entity, click the three dots on the entity and click Collapse. To expand the immediate children for a selected entity, click the three dots on the entity and click Expand. To expand all the descendants for a selected entity, click the three dots on the entity and click Expand All.

  • To remove a specification, click the specification and click Remove in the specification details pop-up. Removing a specification removes it from the canvas but doesn't delete it permanently.

  • To delete a component, click the component and click Delete in the component details pop-up. Deleting a component deletes the component permanently.

  • To delete a relationship between a component and specification, click the three dots on the component and select Remove link to child specifications where child specifications are the specifications that are related to the selected component.

  • You can search for any entity including components by clicking Search. Type the name of the entity that you want to search in the model. The searched entity is expanded in the model tree and when you click the entity in the left side, the entity along with its children is shown in the model canvas.

  • You can set the display settings for the configuration. You can select Entity icon and Entity type to display the entity icon and the entity type. You can choose the orientation to display the configuration horizontally or vertically.

Defining Design Parameters

You define the design parameters that are passed 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. In 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 page and click the Design Parameters tab.

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

      The corresponding specification drawer opens that lists the defined design parameters.

  3. Click the + icon to add a new design parameter to the selected specification.

    The New design parameter drawer opens.

  4. Enter a data element, name, and default value. The default value is pre-populated with the default value that you entered in Data Elements. You can select an existing element or create a new element to be a design parameter. Select + Create Data Element to create a new data element. See "Creating New Data Elements" for more details.

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

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

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

  8. Click Add.

    The design parameter is added.

  9. Repeat steps 3 to 8 to define more design parameters.

You can search for the associated design parameters in the Design Parameters tab. You can see the consolidated view of the design parameters to design action mapping. You can see all the design parameters along with its design action mapping where you can change to the mappings with the view of data in full context of the 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 drawer 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 are specific types of data with particular properties that you can use in a service in Solution Designer. For example, a characteristic can be an ID, a feature, or a telephone number. Few characteristics are added by default based on the resource type and those are called as hard attributes. You can define data elements or feature groups that are entity characteristics within the CFSs, RFSs, resources, and locations.

To define characteristics:

  1. In 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 applications, search and open the specification page and click the Characteristics tab.

      The Characteristics tab page listing the existing characteristics and the hard attributes opens.

    • 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 for the characteristics that are already defined for the selected specification using name.
  3. Enter the details of the characteristics as follows:

    • Select an existing data element or create new data element and select it to be the characteristic. You can also select or create a new feature group as an 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 for the characteristic. The default value is pre-populated with the default value that you entered in Data Elements.

    • Select Required if the characteristic must be mapped with the design parameters in the Parameter Mapping tab. This field is not available for the data elements of type Feature Group.

    • Select Changeable if the characteristic changes frequently or if you need to track the life cycle of an characteristic. In the Mobile Service example, customers often upgrade services for monthly quota. You can select Changeable for the Monthly Quota characteristic and track the characteristic’s history for auditing purposes. When realizing CFSs and RFSs in the UIM run-time application, Solution Designer saves the changeable characteristics to the Service Configuration specifications.

    • (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. Click Submit.

    The characteristic is added to the specification.

  5. Repeat the steps 3 and 4 to define more characteristics to the specification.

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.

    To map the design parameters manually, click the text box in the Destination column to map the design parameter. Clicking the text box lists the first 15 parameters which includes the characteristics (User Defined and Hard Attribute) defined for the specification and the available design parameters defined for its immediate child specifications. For those parameters that are not displayed, you must search them by typing the parameter name in the search field. The result displays parameter names along with the component information to identify the specification to which it is associated to.

    When you select an entity in the Destination column, you can choose Auto select. Auto select automatically maps 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. Repeat step 3 to define more mappings.

    After you complete the parameter mapping, click Save.

    The parameter mappings are saved.

Mapping Parameters Automatically

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 map all the source design parameters with the matching destination parameters at once by selecting Automap in the Parameter mapping drawer. 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

You define the design policies to provision the service in UIM. It allows you to define the design and assign conditions, so at runtime, if the condition is met, then the defined logic is run to assign appropriate resources in UIM to fulfill the service. These are simple policies that have if-then conditions. You can manage the following types of design policies in Solution Designer:

  • Standard Policies: Define the standard policies within Solution Designer for designing and assigning service specifications based on the design parameters. You can create simple standard policies for CFSs and RFSs. In the Mobile Service example, if the State is ON; then select the 5G Profile RFS else select the 4G Profile RFS.

    You can create the following three types of standard policies for resources:

    • Standard Policies for Specification Selection: Define the standard policies within Solution Designer for designing and assigning resource specification based on the design parameters. The specification selection policy is applicable only for resource specifications.

    • Standard Policies for Resource Selection: Define the standard policies within Solution Designer for designing and assigning resource based on the characteristics. As an example, based on Service Address, reserve and assign the phone numbers from the range in the inventory. The resource selection policy is applicable only for resource specifications.

    • Standard Policies for Naming: Define the standard policies within Solution Designer for naming policies, when a resource specification instance is created in the run-time application. You can define a naming policy based on the design parameter, ID, string, or combination of them. The naming policy is applicable only for resource specifications.

    .

  • Advanced Policies: Define advanced policies in Solution Designer. A developer implements the advanced policies in Design Studio Eclipse environment using the extended designer class. Solution Designer builds the solution with standard policies and advanced policies. In the Mobile Service example, select UDR in the same State as the 5G Profile RFS is an advanced policy.

Note:

When you define a design policy with feature group parameter in condition and that feature group having multiplicity more than one, only the first instance is considered to satisfy the condition.

Defining Standard Policies

To define standard policies:

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

  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 tab 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 + drop-down and select Standard policy.

    The New standard policy page opens.

  4. Enter the name, description, component, and default value. The Component drop-down lists only those components that are related to the selected specification. 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. The Default Value drop-down lists the specifications that are related to the component that was selected in the Component drop-down.

  5. In the Conditions section, do the following:

    1. Drag and drop the design parameters from the Parameters panel on the right. The Parameters panel displays the design parameters 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 in the Select Value field that must be validated with the actual value. Select a value if you have to defined valid values for the parameters or enter a value if you do not have valid values defined for design parameters.

      You can create multiple conditions by repeating the steps a to c.

      When you add multiple conditions within a group, all the specified conditions must be met to run the corresponding Then clause.

  6. In the Then drop-down, select the option Create or Select. Create option creates the selected specification at runtime. Select option selects the specification based on the selected advanced policy in the Select policy drop-down at runtime.

    Note:

    When you select the option Select in the Then drop-down, that standard policy must have a corresponding advanced policy to select the entity.
  7. Click Add New Group to add more conditions and repeat steps 5 and 6. When you add multiple groups, the group that meets all the specified conditions first is considered and the corresponding Then is invoked.
  8. Click Save.

    The standard policy is listed in the Design Policies page.

  9. Repeat steps 3 to 8 to add more standard policies.
Defining Specification Selection Policies

To define specification 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 tab 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. Follow the steps 4 to 7 in "Defining Standard Policies" to add conditions for the specification selection policy.

  6. Click Save.

    The standard policy is listed in the Design Policies page.

  7. Repeat steps 3 to 6 to add more specification selection standard policies.
Defining 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 tab 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. Enter the name, and description.

  6. 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.

    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 defined valid values for the characteristics or enter a value if you do not have valid values defined for design parameters.

      You can create multiple conditions by repeating the steps a to c.

      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.

  7. Click Save.

    The standard policy is listed in the Design Policies page.

  8. Repeat steps 3 to 7 to add more specification selection standard policies.
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 tab 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.

  7. Repeat steps 5 and 6 to add 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.

  8. Click Save.

    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 Advanced Policies

To define an advanced policy:

  1. In 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 tab 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 the + drop-down and select Advanced policy.

    The New advanced policy page opens.

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

  5. Enter the notes regarding the policy that you are defining 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.

Advanced Policy Setup Process

Perform the following steps to set up an advanced policy:

  1. Add an advanced policy with notes in the Notes tab regarding the policy. These notes that you enter are added as comments in 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 Workspaces.

    When the publish operation is successful, the requested Design Studio workspace is generated. The Design Studio workspace can be downloaded and imported in to Design Studio Eclipse environment. The Design Studio project contains base class and an extended designer class. You can write the code for the advanced policies in the extended designer class.

  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. Write the implementation code in the extended designer class in Design Studio Eclipse environment for the advanced policy using the comments and compile them. See "Extending Solution Designer" in Developer's Guide on how to define advanced policy implementation.

  6. Use Object Store Utility for updating 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 for 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.

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.

Defining Delivery Policies

You define the delivery policies in Solution Designer. Delivery policies are a set of delivery actions that communicate to a delivery system. For example, an activation system performs delivery actions to configure a network; a shipping system performs delivery actions to pick, pack, and ship physical goods; and a workforce management system performs delivery actions to dispatch work to a field technician.

When you define a resource, you can specify that it is a delivery action target. Only those resources which are defined as delivery action targets can be delivery targets in delivery policies. You define a delivery policy for an RFS or a resource that includes a set of delivery parameters, to indicate the parameters that are involved along with the type of delivery action. With multiple delivery policies, you can have delivery actions destined for different types of delivery systems defined against a single specification.

Available delivery types and the corresponding action codes are:

Table 7-2 Delivery Types and Action Codes

Delivery Types Action Codes

Activation

Activate

Alter

Deactivate

NFV Orchestration

Instantiate

Terminate

Supply Chain Management

Ship

Recover

Test

Initiate

Workforce Management

Install

Reconfigure

Uninstall

All Applications

 NA

Partner Gateway

Order

Revise

Cancel

During service order fulfillment, a design and assign process defined by the design policies produces a service configuration that defines the delivery actions that must be run to fulfill the requested service.

A delivery action represents a unit of work that is performed to realize a resource in a network. A delivery action also defines delivery parameters that describe the work to be done, and these delivery parameters also map to properties of a resource assigned to or referenced by the service configuration. You define the delivery action in Solution Designer by mapping the delivery parameter to the delivery action code and its value. For each delivery action operation, you can select the Value field as required or optional, inputs, outputs, or both.

To define a delivery policy:

  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 or Resource Specifications application, search for an RFS or a resource and open the specification editor page and click the Delivery Policies tab.

      The Delivery Policies page opens.

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

      The Delivery Policies drawer opens.

  3. Click the + icon to add a new delivery policy.

    A New delivery policy drawer opens.

  4. Enter a name, a delivery type, a delivery target, and a description. Only those resource specifications which have Delivery Action Target set are displayed in the Delivery Target drop-down. When defining a delivery policy for an RFS, only those resource specifications that are related as a child to the selected RFS with Delivery Action Target set are displayed in the Delivery Target drop-down.

  5. Add delivery parameters.

    To add delivery parameters:

    1. Click the + icon in the Delivery Parameters section.

      A New delivery parameter drawer appears.

    2. Enter a name and default value. The default value is pre-populated with the default value that you entered in Data Elements. Select an existing data element or create a new data element. See "Creating New Data Elements" for more details.

    3. (Optional) Enter the Multiplicity details. Multiplicity section appears only when you add a data element of type Feature Group as delivery parameter.

      • Select a number in Minimum in the Multiplicity section if you need as many instances in the delivery system such as Activation, Workforce Management and so on. Minimum indicates the minimum number of times the delivery parameter can appear in the delivery system. Selecting the value 1 means that this delivery parameter must appear once in the delivery system.

      • Select a number greater than Minimum in Maximum in the Multiplicity section. Maximum indicates the maximum number of times the delivery parameter can appear in the delivery system. Selecting a value means that this delivery parameter can appear that many times in the delivery system.

      • Select Unbounded if there is no specific limit and this delivery parameter can appear any number of times in the delivery system. If you want to have at least one occurrence of the delivery parameter, select the value 1 in the Minimum field and select Unbounded (no explicit limit). If there is no required minimum number of occurrences, select the value 0 in the Minimum field and select Unbounded.

      To make a delivery parameter as required, set Minimum value to 1 and Maximum value to 1. To make a delivery parameter as optional, set Minimum value to 0 and Maximum value to 1.

    4. In the Characteristic mapping section, select the source characteristic which lists the characteristics of the related resource specification. This maps the characteristics to the selected delivery parameter. You can also map feature group to the destination characteristic that has exactly matching multiplicity. You can map the feature group itself or the individual elements in it.

    5. In the Delivery action mapping section, select Value for the listed action codes. The action codes are listed based on the chosen Delivery Type.

    6. Click Save.

      The added delivery parameter is listed in the delivery parameters section in the New delivery policy drawer.

    7. Repeat steps a to e to add more delivery parameters.

  6. Click Save.

    The delivery policy is added and listed in the Delivery Policies tab in the Service Specifications application, Resource Specifications application, or in the Delivery Policies drawer in the PSR Models application. The Delivery Policies provides the consolidated view where you can see all delivery parameters along with its Action Codes mappings. You can make changes to the mappings by seeing the data in full context of other parameters.

After you define the delivery action mapping in the Delivery Parameter in Solution Designer, you can override the existing implementation with your custom implementation using the extended class. To write the implementation code for delivery action mapping, see "Extending Solution Designer" in Developer'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.