Skip to main content

Service

What is a Service?​

A Service represents an application scenario or business function module. You can create:

Key Features​

  • Flexible Creation: Freely create, modify, or delete Services
  • Independent Configuration: Each Service can be configured separately with parameters, rules, and policies
  • Usage Monitoring: Independently monitor the request volume, error rate, cost, etc. of each Service

Advantages Summary​

  • Customized Requirements: Freely combine Services to meet customized business needs
  • Functional Decoupling: Services are relatively independent; enable/configure/disable individually without mutual interference
  • Personalized Configuration: Each Service can be personalized according to specific requirements
  • Clear Monitoring: Understand the operational status of each business scenario with insightful data
  • Simplified Management: Break down complex requirements into multiple Services, reducing management complexity

The Service feature empowers you with maximum flexibility. You can freely combine application scenarios and business function modules based on your actual needs, perform personalized configurations, and clearly understand the usage status of each service, enabling efficient utilization of platform resources and achieving business customization.

Relationship Between Service and Vendor​

In this SaaS platform, there is a close association between Service and Vendor. Each Service can choose to bind to a vetted Vendor or not bind to any Vendor.

Binding to a Vendor​

If a Service is bound to a Vendor, all messages sent using that Service will automatically carry the related information of that Vendor. Specifically:

  • If the template used contains the vendor variable, it will be replaced with the name or identifier of the bound Vendor.
  • If the content of the message needs to reflect the sender's identity, the information of the bound Vendor will be used.

The main purpose of binding to a Vendor is to ensure the transparency of the message source, increasing the credibility and user experience of the information.

Not Binding to a Vendor​

If a Service is not bound to any Vendor, the messages sent will not contain any Vendor-related information. In this case:

  • The vendor variable in the template will be replaced with an empty string.
  • No specific sender identity will be presented when sending messages.

Not binding to a Vendor is typically applicable in scenarios where there are no special requirements for the sender's identity.

Vendor Approval​

To ensure the security and compliance of message delivery, the platform requires all Vendors that wish to be bound to a Service to go through an approval process. Only approved Vendors can be bound and used for message delivery in the relevant Services.

Through the flexible binding mechanism between Service and Vendor, this SaaS platform allows you to choose whether to bind an approved Vendor to a Service based on your actual needs, thereby determining whether to include Vendor-related information when sending messages, meeting the diverse requirements of different scenarios.