Create a Service class

Steps to create a Service class

To create a Service class in the Dynamo Marketplace, you must complete a series of configuration steps.

The overall workflow includes:

• creating a new Service class from scratch or from a template;
• configuring service attributes, parameters, and operational settings;
• defining the information required from the Buyer during the ordering process;
• configuring any outputs returned after provisioning and activation;
• configuring the service provisioning method.

This guide describes the operational workflow for creating a Service class. For an explanation of the core concepts, refer to the guide Service components and structure in the Dynamo Marketplace.

Create a Service class

A Service class defines the technical structure of a service, the available attributes, the information required from the Buyer, and the provisioning methods used by the service.

You can create a new Service class:

• from scratch;
• using a predefined template;

During Service class configuration, the following sections are defined:

• Name & category – defines the Service class name, category, and subcategory;
• Service details – defines the price-relevant technical attributes whose values are used to define the service variants and their pricing;
• Order configuration – includes the attributes inherited from Service details and allows you to define additional information required from the Buyer for provisioning that does not affect the service price;
• Output attributes – configures the information returned after provisioning and activation;
• Provisioning – defines the provisioning method through email or API integration.

Create a Service class from scratch

Creating a Service class from scratch allows you to manually define its structure, attributes, and configuration.

• Sign in to the Provider dashboard;
• From the side navigation menu, select Service management > Service class;
• Select Create service class in the upper-right corner;
• Review the introductory information in the Explanation step and select Next;
• Configure the Name & category section:
  • Service class name – assign a name to the Service class;
  • Category – select a category from the available options;
  • Sub category – select a subcategory from the available options;
  • Select Save & next.
• Configure the Service details section:
  • the section includes:
    • Price-relevant technical attributes – attributes whose values define the service variants and affect their pricing;
    • Service-specific technical attributes – attributes required for service provisioning whose values do not affect the service price;
    • Basic information details – basic service information that is added when creating the Marketplace Service and cannot be configured in the Service class;
  • add service technical and commercial attributes;
    

    For price-relevant technical attributes, use Plain text, Numeric, Dropdown, Boolean, or Date attributes. These attributes must be configured as required because each variant must have a value for every price-relevant attribute.

  • configure rules, validations, and available values as needed;
  • organize the layout and structure of attributes;
  • Select Save & next.
• Configure the Order configuration section:
  • define the information required from the Buyer during the ordering process;

    Attributes defined in Service details are automatically inherited in Order configuration and cannot be edited in this section. To modify them, return to the Service details section. Additional attributes created directly in Order configuration can use any of the available attribute types.

  • configure any parameters required for provisioning;
  • Select Save & next.
• Configure the Output attributes section:
  • define the information returned after provisioning and activation;
    

    Output attributes can use any of the available attribute types.

  • configure any access, configuration, or delivery information;
  • Select Save & next.
• Configure the Provisioning section:
  • select the provisioning method supported by the service;
  • configure any parameters required for integration or fulfillment;
  • Select Submit to complete the Service class creation process.

Create a Service class from a template

Templates allow you to quickly create a Service class using a preconfigured structure that includes attributes, settings, and standard sections.

A Service class created from a template remains compliant with the standard services defined by Dynamo if the attributes provided by the template are not modified or deleted. You can add additional attributes without affecting compliance. Compliant Service classes are included among the standardized services available through the dedicated Storefront filter.

• Sign in to the Provider dashboard;
• From the side navigation menu, select Service management > Service class;
• Select the Templates tab;
• Locate the template you want to use and select Use template;
• Review the introductory information in the Explanation step and select Next;
• Configure the Name & category section:
  • Service class name – assign a name to the Service class;
  • Category – automatically populated by the template;
  • Sub category – automatically populated by the template;
  • Select Save & next.
• Review the Service details section:
  • the template may already include configured technical and commercial attributes;
  • you can add new attributes using the Attributes side panel;
    

    For price-relevant technical attributes, use Plain text, Numeric, Dropdown, Boolean, or Date attributes. These attributes must be configured as required because each variant must have a value for every price-relevant attribute.

  • Select Save & next.
• Review the Order configuration section:
  • configure the information required from the Buyer during the ordering process;
    

    To keep the Service class compliant with the template, you cannot delete the existing attributes. You can modify their conditions, such as validation rules or regular expressions, and add new attributes.

  • define any parameters required for provisioning and activation;
  • Select Save & next.
• Review the Output attributes section:
  • configure the information returned after provisioning and activation;
    

    Output attributes can use any of the available attribute types.

  • define access information, technical parameters, or delivery information as needed;
  • Select Save & next.
• Configure the Provisioning section:
  • select the provisioning method supported by the service;
  • for API integration provisioning:
    • download the ZIP package generated according to the Service class configuration defined in the previous steps;
    • open the downloaded ZIP package and refer to the readme.md file for instructions on how to develop and configure the required mapping;
    • complete the Excel file included in the package by specifying the names of the six files required for the Meson configuration;
    • upload the completed Excel file together with the six files specified in it;
    • if this is the first service created by the Provider using API-based provisioning, contact Dynamo to define how Dynamo will interact with and authenticate to the Provider APIs. This integration is configured specifically for each Provider and requires an offline setup step;
  • for Email-based provisioning, no templates or integration files are required;
  • Select Submit to complete the Service class creation process.

If you use API-based provisioning, after uploading the required files you must wait for authorization from Dynamo. Authorization is granted after the correct operation of Meson has been verified. You will be notified by email when the authorization process is complete.

Information displayed in the Service class list

The Service class list displays several status indicators:

• Is compliant – indicates that the Service class was created from a template and that the attributes provided by the template have not been modified or deleted. Additional attributes can be added without affecting compliance with the standard services defined by Dynamo;
• Customisation – displays the completion status of the Service class configuration; when Customisation is Completed, the operations available depend on the Meson status;
• Meson status – indicates the status of the Meson technical integration used for API-based provisioning:
  • Meson Deployed – the Service class is active and services based on it can be published;
  • Authorized – services can be created based on the Service class, but they cannot yet be published;
  • Pending – the Service class is waiting for authorization from Dynamo. As part of the authorization process, Dynamo verifies that the uploaded Meson configuration is working correctly.

What to do after creating a Service class

After creating a Service class, you can use it to create one or more service offerings from the Service management section. The same Service class can be reused to create multiple service offerings.