4 Managing Domains
Use domains in Solution Designer to organize and manage specifications such as Customer Facing Services (CFS), Resource Facing Services (RFS), and resources into meaningful groups.
Topics in this document
About Domains
A domain is a logical group or category that represents a specific area or type of service within the telecommunications industry. It is used to organize and classify the specifications, offerings, and capabilities provided by the service provider. Each domain typically represents a distinct aspect of the telecommunications services, such as voice services, data services, network infrastructure, security, customer support, cloud services, Internet of Things (IoT), or any other relevant category specific to your service offerings.
Domains are divided into service domains and technology domains to provide a granular categorization within a specific domain. A technology domain can reference zero or more service domains. Domains are used for filtering when creating service and technology models. For example, if the Mobile service domain is selected, then only those entities belong to the same service domain are available for selection when building the PSR model.
Table 4-1 Types of Domain
| Domain Type | Description | Specifications |
|---|---|---|
| Service | Manage the specifications related to customer services. Service domains represent different types of services that are offered. Examples include Mobile, Broadband, TV, Voice, Cloud Services, and Internet of Things (IoT). |
CFS RFS Resource |
| Technology | Manage the specifications related to the underlying technologies that are used to implement those customer services. Technology domains represent the different technologies used to deliver the services. Examples include DSL, Fiber, Cable, 5G, LTE, Wi-Fi, and Satellite. |
Resource RFS |
You can use multiple domains of the appropriate type to help organize your specifications and models. For example, a Mobile Service offering can have a service domain as Mobile and technology domains as 5G, 4G, and so on.
A service domain can be associated with multiple service models and specifications. Similarly a technology domain can be associated with multiple technology models and specifications. The specifications can have one primary domain and multiple secondary domains.
Domains play an important role in realizing a design. After an initiative is released, you can use the domains belonging to that initiative elsewhere in the application.
Creating Domains
You create domains using the Domains application, or in the Select service domain step when creating service models, or in the Select technology domain step when creating technology models in the guided process.
-
In the Solution Designer landing page, click the Domains application.
-
To create domains, do one of the following:
-
In the Domains application, click Create Domain.
-
In the PSR Models application, click Create Service Domain in the Select service domain step while creating a service model.
-
In the PSR Models application, click Create Technology Domain in the Select technology domain step while creating a technology model.
The New Domain drawer appears.
-
-
Enter the following details:
Table 4-2 New Domain Fields
Name Required or Optional Description Name
Required
Name of the domain. Name must have more than one character.
ID
Required
Id of the domain.
Type
Required
The type of domain.- Service
- Technology
Description
Optional
The description of domain.
Associated Service Domains
Optional
The service domains that are associated with the technology domain. This field appears only when you select Technology as the Type.
Initiative
Required
The initiative that the domain belongs to.
Asset Type in the Implementation Assets section
Optional
The type of the implementation asset. The values are Helper class and Library.
Description in the Implementation Assets section
Optional
The description of the implementation asset.
Download Link in the Implementation Assets section
Required when Asset Type is selected.
The relative path of the helper class files or the third-party library files. For example,
/bucket/helperclass.zip.The helper classes in compressed (zipped) format and the third-party libraries in JAR file format must be placed in S3-compatible object storage and the relative path must be specified.The defined helper class and libraries are loaded from the specified while building the cartridges.
The domain IDs must follow the naming rules. See "About Naming Rules" for more information on naming rules.
Note:
When you edit the Implementation Assets values, the fields do not appear as editable. However, you can edit the details and click Submit. -
Click Create.
The domain is created.
Viewing Domains
A Service Specialist views the domains from the Domains application or from the Initiative Items tab in the initiatives editor page in the Initiatives application.
To view domains:
-
In the Solution Designer landing page, click the application that you want to work with.
-
Do one of the following:
-
In the Domains application, search for a domain using the following criteria:
- Domain name
- Type: Service or Technology
- Status: Lifecycle status
- Initiatives
- Last Updated date
The domain result is filtered based on the search criteria.
-
In the Initiatives application, search for an initiative and click the Initiative Items tab in the initiatives editor page.
-
-
Select a domain to view the details of that domain.
The Domain drawer appears.
The following details are displayed:- Overview tab: Shows the details of the domain.
- Used by tab: Shows all the items such as models, domains, and specifications that the domain is associated with. You can filter the results by searching with the item name.
- After viewing the details, click anywhere outside the dialog box to return to the Domain list page or the initiatives editor page.
Updating Domains
You can update the domain details such as Name, Description, Implementation assets, and Associated service domains.
-
In the Solution Designer landing page, click the application that you want to work with.
-
Do one of the following:
-
In the Domains application, search and select a domain.
-
In the Initiatives application, search for an initiative and select a domain from the Initiative Items tab in the initiatives editor page.
The domain dialog box opens.
-
- Click Edit and update the name, description, implementation assets, and the associated service domain.
- Click Update.
Note:
-
You can't update the domain Type.
-
You can update the domain details only in Definition and Advanced Configuration status. You can't update the details after you complete the initiative's Advanced configuration phase.
Deleting Domains
You delete a domain from the Domains application or from the Initiatives application.
To delete a domain:
-
In the Solution Designer landing page, click the application that you want to work with.
-
Do one of the following:
-
In the Domains application, select a domain.
The domain drawer opens.
-
In the Initiatives application, search for an initiative and click the Initiative Items tab in the initiatives editor page.
-
-
Click Delete.
The domain is deleted if it is not associated with any entities or domains.
Note:
You can delete a domain only in Definition and Advanced Configuration status. You can't delete the domain, if the associated initiative is in the Functional Testing phase, the Acceptance Testing phase, the Approval phase, or the Released phase. You also can't delete a domain if it is referenced by any entity such as PSR models, CFSs, RFSs and so on.