Language Reviews of Missions in SAP Discovery Center

Deliverables / More

What is a Mission

Missions in SAP Discovery Center connect the business use cases with their technical implementation. These use cases might be related to SAP BTP, its services, or other SAP solutions, such as SAP SuccessFactors, SAP S/4HANA, SAP S/4HANA Cloud, SAP Customer Experience, SAP ECC, and so on, that use SAP BTP services.

There are two types of missions:

• Platform missions: created by SAP colleagues
• Partner missions: created by SAP partners and dedicated to their partner solution
• Missions provided by SAP, called Platform missions
• Missions provided by SAP partners sometimes called App missions
• Non-technical missions of one of these categories: SAP Enterprise Support, SAP Preferred Success and SAP Cloud Competency

To ensure that all these missions are well-written and easy-to-follow, we need the help of the User Assistance community. We need to involve all UA colleagues who have their service or product part of a mission. For a list with UA responsibility, see the Who Is Who? page.

How to Use Missions

Missions are free of charge and available publicly. Both internal and external users can start them. The steps of a mission are presented in a project board, organized in columns (phases) and in every column, there are ordered tiles (cards). To see the full content in a project board, you have to start a mission.

When you start a mission, you create your own instance of this mission. You and the mission's creators/experts are the only ones who have access to your mission instance. In your started mission you can:

• Invite members, these are the colleagues you are working with and they will also see the content of your mission instance. You can either add them to the entire project board, or to a specific card.
• Mark a card or a phase as completed, or not relevant for your implementation.
• Add or remove content that is specific to your implementation.
• Ask questions in the comments of every card. Only mission experts and colleagues you have added can see these questions and their answers. The mission experts will directly answer your questions in the same thread.

For more information, see:

• Guidelines to Create Missions in the Mission Manager Tool

Recommendations for UA Developers Who Review Missions

To edit a mission and propose comments to the mission authors, follow these steps:

1. Copy the content from the mission overview and the project board and paste it into a Word file. Then, either use the Track Changes options or simply put comments with your proposals.

2. Check if the overview of the mission and its project board meet all the requirements. If not, put comments in the Word file and send the file to the mission authors.

Format the Mission Overview

Follow these guidelines when editing the mission overview:

• The title of a mission must be title case, max. 60 characters long and start with a verb.
• The diagram must have a human-readable explanation, not the name of the .png file.
• The Use Case section contains the business case explained.
• The Current Position section gives an overview of the current situation the customer is in. This is the situation we want to improve by the solution proposed in the mission.
• The Destination section explained how the current situation of the customers would be improved if they implement the mission.
• The How You Get There section gives a general idea what the solution proposed in the mission contains and how it can be implemented.

Format the Project Board of a Mission

These are the most common issues related to the project boards of the missions:

• Use only official names for products and services. See Approved Names in SAP Brand Tools.
• The text in the cards must be clear and easy to follow. It's better to reuse information (there is an automatic reuse form the Tutorial Navigator and GitHub, tutorials and GitHub pages appear embedded when the card description contains the URL only without any markup. It is recommended to use the source code editor when you embed these pages), or use links to the official documentation.
• When describing procedures, use numbered lists.
• Cards represent single steps, therefore it's better to use sentence style for the cards' titles.
• Cards' titles start with a verb.
• The columns of the project board represent phases. Their titles should be verbs written in All Caps.

Product Names

Guideline: Make sure that you use only approved names for products/components. Check them in the Approved Names in SAP Brand Tools. Do not use abbreviations that are not officially approved!

Sentence Style and Title Case

Guideline: Titles of mission cards should be in sentence style. See English: Capitalization (Sentence Style and Title Case).

Guideline: Titles of missions should be in title case. See English: Capitalization (Sentence Style and Title Case).

Diagrams

Guideline: Diagrams in the overview of the mission should have human-readable names.

Links

Guideline: When inserting a new link, always use the title of the page as the displayed name. Never hide links behind words like "here", "this", "blog", and so on.

Procedures

Guideline: When you have steps and the order matters, always use numbered list, not bulleted.

Guideline: When describing steps in a User Interface, mark the UI elements in bold. This improves readability.

Guideline: When interacting with a UI element:

• Use the verb choose instead of click, or press.
• Use the verb select, when you have a dropdown menu, for example.
• Use the verb select, when you have checkboxes.

Guideline:

When meaning a verb, these are written separately:

• Set up
• Log in
• Log out

When meaning a noun, these are written as one word:

• Setup
• Login
• Logout

When writing steps, follow this pattern:

In the <UI-element-exactly-as-it-appears-in-the-UI> field, enter <exact-value-that-needs-to-be-entered>.

In the <UI-element> field, select <> from the dropdown menu.