Introduction

Within the data sheet topic, you have to provide details on the features of your service. Each feature consists of the following:

Feature title
Feature description

Getting Started

We recommend that you start by writing the description first and think of the title afterwards. It is much easier to come up with a meaningful title if you have already defined the feature content in the description.

Provide 2 to 8 features for each service.

Feature Title

The feature title is supposed to be a summary of the description, but more in the sense of a benefit taking on the perspective of the reader or user. It should give the reader an idea of the feature at first sight.

Start the title with a capital letter and a verb (to directly address the reader).
Use sentence style.
Do not exceed a maximum of 40 characters in English.
Avoid words such as "enable," "help," or "provide" - everything we create at SAP is designed to help or enable customers.
Tips and tricks: Try to answer the question: "What benefit does the feature offer to the reader or user of the service?" ("You (the reader) will benefit from using the service, because...")

Feature Description

The feature description is supposed to give information on activities the reader or user might perform with the service ("do" rather than "facts"). Each description therefore should start with a verb:

Start the description with a capital letter and a verb and end with a period.
Use a minimum of 80 characters and do not exceed a maximum of 260 characters in English.
Avoid words such as "enable," "help," or "provide" - everything we create at SAP is designed to help or enable customers.
If you refer to non-SAP products in your description, use the appropriate product trademarks.
Stick to the facts and make sure your descriptions do not promise anything, such as increasing revenue or systems that will run error-free.

Multitenancy Support

If your service supports multitenancy, add the following feature:

Feature title: Benefit from multitenancy support
Feature description: Use this service in tenant-aware (multitenant) applications. Run them on a shared compute unit that can be used by multiple consumers (tenants).

Examples

The following table lists the Consent Repository service features:

<div> <div>Feature Title</div> <div>Feature Description</div> </div> <div> <div></div> <div>Create and manage your own consent forms and purposes in different languages to meet your business needs.</div> </div> <div> <div></div> <div>Determine whether your customers have granted or withdrawn their consent.</div> </div> <div> <div></div> <div>Allow the exchange of personal data with your business partners. You can allow this exchange to different degrees.</div> </div> <div> <div></div> <div>Identify expired or withdrawn consent records and delete them, if required, for example, on request from a data subject. You can configure retention periods to help you manage deletion.</div> </div> <div> <div></div> <div>Use this service in tenant-aware (multitenant) applications. Run them on a shared compute unit that can be used by multiple consumers (tenants).</div> </div>