The SAP Fiori UI text guidelines are not exhaustive. They build on [external_only]other writing guidelines at SAP[/external_only][internal_only]the SAP Style Guide for Technical Communication[/internal_only] and cover only specific conventions for SAP Fiori applications. The guidelines have evolved on an as-needed basis to clarify questions that have arisen during SAP Fiori app development, or to reiterate points that recur in SAP Fiori app design reviews.
[internal_only]We update the guidelines on an ongoing basis as SAP Fiori evolves. For the latest updates, see the change history. If you have a question that has not yet been addressed, please feel free to contact us through the SAP Fiori Design Community. [/internal_only]
The guidelines are based on US English, the primary source language at SAP. There are no specific SAP Fiori text guidelines for other languages.
Finding your way
See the content overview at the beginning of each section to navigate.
Limit the use of abbreviations as much as possible to avoid unnecessary abbreviations appearing on the desktop, where space is often sufficient.
Test your screens on all three device types (smartphone, tablet, and desktop) to ensure that you see the labels live in each case. Optimize as required and as far as space allows.
[internal_only]If you shorten a string that is stored in a front-end properties file, ask your developer to add the full term as a comment for editors and translators.
For more information, see Abbreviations in the SAP Style Guide for Technical Communication.[/internal_only]
Abbreviating “Quantity”
Do not use the abbreviated form Qty. Abbreviations in other languages do not work. If there is enough space on the screen, write out the full word.
Application names
General rules
Ensure that the title of the app (initial screen) matches the title on the tile.
Do not use the tile subtitle for explanations. Use the subtitle only for differentiating information.
Background: Explanations are often redundant and will typically be truncated in some target languages.
Do
You can use tile subtitles to differentiate between similar apps
Don't
Don't use the tile subtitles for hints or explanations
Transactional or hybrid apps
If the user can make changes to the data on the database, start the app name with a verb.
For employee self-service apps, start the name with My.
If the key focus of the app is to process items assigned to the user, start the name with My.
Choose a verb that best fits the main purpose of the app:
For approval apps, start the name with Approve.
If the app is used primarily for CRUD actions (create, update, delete), start the name with Manage.
If the focus of the app is on processing documents, start the name with Process.
Use the plural for the business object, as the user can generally process more than one object within the app.
Create Billing Documents
My Timesheet
My Open Worklists
Approve Supplier Invoices
Manage Purchase Orders
Process Sales Orders
Analytical apps
Use a noun-based name and avoid the word “analysis” (to avoid unnecessary repetition across all analytical apps).
My
Use the plural for the business object where it makes sense.
Journal Entries
Liquidity Forecast
Cash Flow
Cash Flow Analysis
If your app also allows users to take action after analyzing the data (hybrid app), use the naming guidelines for transactional/hybrid apps.
Overview page
Use a noun-based name.
Do not use the term “Overview Page”. This is just the name of the floorplan. However, it’s fine to use “Overview” on its own.
Use the three-letter currency code instead of the currency symbol. This prevents ambiguity when multiple currencies share the same symbol.
EUR
USD
€
$
Case
Unless otherwise specified for individual UI elements, use title case for all SAP Fiori user interface short texts (labels, headings, value help texts, and so on), and sentence case for all messages and explanations.
Relative times
Values and statuses that start with a number
4 days ago
4 items left
Consider using sentence case if a text is very long, making it difficult to read in title case.
For example, you might have a long status text, or long subtitles in the cards on an overview page.
Material damaged in transit
Sorted by turnover and region
Status texts in a table column
If you opt to use sentence case for a certain text type, use it consistently in your context (for example, all subtitles for the cards on an overview page, or all the labels for a set of radio buttons or checkboxes).
Hyphenation
Email
Do not use a hyphen for email.
OData service
Hyphenate OData service in German.
OData-Service
Text wrap
Do not add manual hyphens to wrap texts (for example, on tiles or in column headings).
Background: The point at which a text wraps is determined automatically. [internal_only] We are working on a global solution for hyphenation. Any hyphens you add manually will be redundant once hyphenation is automated.[/internal_only]
Punctuation
Colon
Colons must always be exposed as translatable strings. Other languages may use a different symbol (for example, Chinese), or require different spacing (such as French, which requires a space before the colon).
Where possible, include the colon at the end of the corresponding natural language string.
Colons after field labels
Place a colon after the field label if the field label and value are visually separate and do not form a running phrase or sentence.
Description: Laser Jet Printer
Valid From: 09/13/2013
Forwarded by Joe Bloggs
For form fields, the colon is added automatically by the UI control. For other field labels, the colon must be added manually by the app development team.
Do not add a colon after titles (for example, in an object page header).
Colon as a separator
Use a colon to separate concatenated texts that would otherwise be hard to translate. Note: If possible, avoid concatenated texts in the first place.
Search In: Sales Orders
This format ensures that the verb comes at the beginning in all languages and is never truncated.
Ellipsis (…)
Use the ellipsis (…) if a menu item leads to a set of further menu options.
Do not use the ellipsis:
In placeholders (input prompts) in entry fields. These are texts that show for empty field values, but disappear as soon as the user starts typing or selects a value.
In menu buttons. Here, the dropdown arrow already indicates that there are multiple selection options.
In labels for actions that open a follow-on dialog or screen. Exception : Consider using an ellipsis if it’s standard practice to do so (for example, Browse… to select files).
To indicate a busy state. SAP Fiori normally uses a graphical busy state rather than text. If a text is used, check with your UX designer. Exception : If a text is required, add an ellipsis at the end to indicate that the user must wait (for example, Loading…).
Don't
Don't use the ellipsis in placeholder texts
Don't
Don't use the ellipsis for menu buttons
Period
Many SAP Fiori apps use texts from back-end systems that were written without an ending period, based on the ABAP guidelines. To avoid changing (and retranslating) many legacy texts, we have adopted the following approach for SAP Fiori:
Use periods at the end of complete sentences:
If your sentence is written out in full with all its grammatical components, use a period. Rule of thumb: Add a period if your text is obviously incorrect without one. Examples : :icon-acceptYou don’t have authorization to view this page. :icon-acceptTo start, enter your filter settings.
If your sentence is incomplete, written in short form (implicit sentence), or very short, leave out the period. Rule of thumb: The text does not look “wrong” without a period. Examples : :icon-acceptLeave request created :icon-acceptNo matching items found
Placeholders: Do not use a period for placeholders (input prompt texts). Reason: This avoids a mixture of prompt texts with and without periods on one page. Examples : :icon-acceptEnter an alphanumeric key :icon-declineEnter a 3-digit code.
Illustrated messages: Never use an ending period in the headline for an illustrated message, even if it’s a complete sentence.
Don't use an ending period in the illustrated message headline
Punctuation in buttons and labels
Avoid using hyphens, colons, or parentheses in button texts. Use a preposition instead.
Material Number for Receipt
Material Number – Receipt
Quotation marks
If you need to set off a text in quotes, use double quotation marks.
In the system, always use straight quotes ("…"). Typographical (smart) quotes can lead to errors.
Messages / Descriptions
Use quotation marks if:
Your message or description quotes a label or text on the UI. Example : :icon-acceptTo start, set the relevant filters and choose "Go".
The string contains a dynamic text variable for a customer text, such as a product name. Without quotes, text variables can result in incorrect grammar and make the text difficult to read. Examples : :icon-acceptMaterial "Soft copper pipe 10 mm" is out of stock. :icon-acceptStaffing requirements have changed for project "Quartz".
The string cites a value selected or entered by the user. This can be a text string, date, or number. Quotes help to highlight the user’s entry. Examples : :icon-accept"December 25, 2020" is not a working day. :icon-accept"2026" is not in the current planning cycle.
Your string contains any other variable that may cause grammatical or legibility issues without quotes.
Do not use quotation marks if:
The string contains a variable for a system-generated object ID. IDs are typically numeric or alphanumeric and do not affect the grammar of the text. Example : :icon-acceptPurchase order 12345678 was deleted.
The string contains a variable for an absolute date that is provided by the system. Example : :icon-acceptYour license is due to expire on May 2, 2021.
Your string contains a variable that can be inserted without compromising the grammar or legibility of the text in any language.
Other considerations:
If your string contains multiple variables that all need to be set off with quotes, texts can become difficult to read. Consider alternative formats, such as listing the variables in parentheses or below the main text.
Do not use text variables for system parameters, such as object types or categories. Use a generic term or write separate messages for each case.
Titles
Avoid using quotation marks for concatenated title texts with text variables. Use a colon instead. If in doubt, check with your translation team. Note: If possible, avoid concatenated texts in the first place.
Select: Products
Select "Products"
Slash
Apply the following spacing rules for slashes.
Distinct Concepts
If you are using a slash to separate terms for distinct concepts, include a space before and after the slash. In this case, all the text before the slash belongs to one concept, and all the text after the slash belongs to another.
Use cases in SAP Fiori include:
Two adjacent field labels in a form.
Two labels in a table column header.
Slashes to separate items in a breadcrumb. Note: This is an exception. Normally, SAP Fiori uses commas to separate listed items.
Insurance Type / Tax Rate
Amount in Local Currency / Due Date
Amount in Local Currency/Due Date
Labels for adjacent fields in a form ('Postal Code' and 'City')
Two values in one column ('Division' and 'Plant')
Items a breadcrumb
Qualifying Terms
If all the texts separated by a slash (or slashes) qualify a term that precedes or follows, do not include a space before and after the slash.
Plan/Actual Costs
Plan
Actual
Configure Rules and Approved List of Suppliers/Manufacturers
Configure Rules and Approved List of Suppliers / Manufacturers
Manufacturers
Note: Even if you can use a slash to avoid redundancy (as in First/Last Name), we still recommend writing out both labels in full in forms and column headers if you have the space (First Name / Last Name).
In tile subtitles, space is very limited. You may need to leave out spaces before and after a slash even if the concepts are distinct.
However, you should be sure that the text can’t be misunderstood, especially if you are using compound terms.
Also bear in mind that if space is already tight in English, there may still not be space for the translated text.
Symbols
Do not use ampersands (&) in SAP Fiori apps or app names.
You can use other common symbols, such as %, but avoid more technical or mathematical symbols, such as ∑, <, >, =.
Avoid using symbols that can have multiple meanings (for example # can be a number, a metadata tag, or a phone extension number).
Bear in mind that symbols can be difficult to translate.
% Confirmed
Due in less than 5 days
SWIFT Code: DEUTDE8L875
Due in < 5 days
SWIFT # DEUTDE8L875
Singular and Plural
Messages, descriptions
If messages or descriptions contain a number variable, differentiate between singular and plural cases, depending on the value.
Don’t use parentheses “(s)” to express the plural. This won’t work in all languages.
Your subscription is due to expire in 1 day.
Your subscription is due to expire in 3 days.
Your subscription is due to expire in 1 day(s).
Labels for number values (count)
If a label describes a number value (count), write the label as follows:
Where appropriate, indicate the type of value in the label text.
Number of Purchase Orders
Order Quantity
If space is limited, and the label contains only the name of the object or item, use the plural to cover all possible values (0, 1, or more).
Do
Table title with count / column heading for count
Do
Tab labels with count
Word Choice
Actions for requests
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Approve</div> <div>Grant permission (for example for budget or vacation).</div> </div> <div> <div>Reject</div> <div>Refuse permission.</div> </div> <div> <div>Accept</div> <div>Accept invitation.</div> </div> <div> <div>Decline</div> <div>Decline invitation.</div> </div> <div> <div>Forward</div> <div>Forward a request to a manager or decision-maker.</div> </div>
Completing an action
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Create</div> <div>Save a <strong>new</strong> object to the database. It doesn’t matter how the object was created (from scratch, or by adapting a copy of an existing object). <em>Create</em> is used in both cases.</div> </div> <div> <div>OK</div> <div> <p>Confirm settings that may or may not have been changed (for example, filter settings for a table).</p> <p>Note: A specific verb is preferable (such as <em>Save</em>).</p> </div> </div> <div> <div>Save</div> <div>Standard action for saving changes to <strong>existing</strong> objects when no workflow is being triggered.</div> </div> <div> <div>Save and Next <Qualifier></div> <div> <p>Continue to the next screen or object.</p> <p>We recommend adding a qualifier. While “Next” works as a standalone label in English, other languages may require a qualifier.</p> <p>If you don’t add a qualifier in the English source text, add a note for translators to provide the context.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Save and Next Page</em><br><span class="icon icon-accept"></span><em>Save and Next Item</em><br><span class="icon icon-accept"></span><em>Save and Next Customer</em><br><span class="icon icon-decline"></span><em>Forward</em></p> </div> </div> <div> <div>Submit</div> <div>Submit to a workflow (for example, for manager approval).</div> </div> <div> <div>Send</div> <div>Send a request to another person, especially in employee apps (for example, a vacation request).</div> </div> <div> <div>Next <Qualifier></div> <div> <p>Continue to the next screen or object.</p> <p>We recommend adding a qualifier. While “Next” works as a standalone label in English, other languages may require a qualifier.</p> <p>If you don’t add a qualifier in the English source text, add a note for translators to provide the context.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Next Page</em><br><span class="icon icon-accept"></span><em>Next Item</em><br><span class="icon icon-accept"></span><em>Next Customer</em><br><span class="icon icon-decline"></span><em>Forward</em></p> </div> </div> <div> <div>Finish</div> <div> <p>Trigger the completion of a workflow or process.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Finish</em><br><span class="icon icon-decline"></span><em>Done</em></p> </div> </div>
Stopping or interrupting an action
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Cancel</div> <div>User action to stop a system function before it has been completed.</div> </div>
"Cancel” as a business action
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Cancel <Object></div> <div> <p>If “cancel” is being used as a business term, include the object type.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Cancel Job</em><br><span class="icon icon-accept"></span><em>Cancel Purchase Order</em><br><span class="icon icon-decline"></span><em>Abort</em></p> </div> </div> <div> <div>Don’t Cancel</div> <div> <p>In confirmation dialogs, as negative path action for “Cancel <Object>”.</p> <p><u>Example</u>:<br>Confirmation message: Cancel invoicing job JOB_12345678?<br>Primary action: <em>Cancel Job</em><br>Negative action: <em>Don’t Cancel</em></p> </div> </div>
Navigation actions
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Back</div> <div>Go back to the previous screen.</div> </div> <div> <div>Next <Qualifier></div> <div> <p>Continue to the next screen or object (for example, in a workflow with a sequence of activities, or when navigating to the next image in a <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Fcarousel%2F">carousel</a>).</p> <p>We recommend adding a qualifier. While “Next” works as a standalone label in English, other languages may require a qualifier.</p> <p>If you don’t add a qualifier in the English source text, add a note for translators to provide the context.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Next Page</em><br><span class="icon icon-accept"></span><em>Next Item</em><br><span class="icon icon-accept"></span><em>Next Customer</em><br><span class="icon icon-decline"></span><em>Forward</em></p> </div> </div> <div> <div>Previous <Qualifier></div> <div> <p>Navigate back to the last object or image (for example, the previous image in a <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Fcarousel%2F">carousel</a>).</p> <p>We recommend adding a qualifier. While “Previous” works as a standalone label in English, other languages may require a qualifier.</p> <p>If you don’t add a qualifier in the English source text, add a note for translators to provide the context.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Previous Image</em><br><span class="icon icon-accept"></span><em>Previous Product</em><br><span class="icon icon-accept"></span><em>Previous Item</em></p> </div> </div>
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Add</div> <div> <p>Add an existing item to a list.</p> <p><u>Example</u>:<br><span class="icon icon-accept"></span><em>Add Contact</em> (for example, add a contact from the global address book to a list of my contacts)</p> </div> </div> <div> <div>Create</div> <div> <p>Create a new object (either from scratch, or by adapting a copy of an existing object).</p> <p><u>Example</u>:<br><span class="icon icon-accept"></span><em>Create Purchase Order</em><br><span class="icon icon-decline"></span><em>Create New Purchase Order</em></p> </div> </div> <div> <div>Create and New <Qualifier></div> <div> <p>Create an object from scratch and return to the create screen to add another new object.</p> <p>We recommend adding a qualifier. While “Create and New” works as a standalone label in English, other languages may require a qualifier.</p> <p>If you don’t add a qualifier in the English source text, add a note for translators to provide the context.</p> </div> </div> <div> <div>New <Object></div> <div> <p>Title of an object until the name has been defined (for example, on an object page or “create” dialog).</p> <p><u>Example</u>:<br><span class="icon icon-accept"></span><em>New Purchase Order</em></p> </div> </div> <div> <div>Copy<br>[internal_only]DE: Kopieren[/internal_only]</div> <div> <p>Replicate data from one place to another.</p> <p>Use case 1: Copy and Paste</p> <p>Use case 2: Create a new object or item based on an existing one. In this case, the user adapts the core data copied from an existing object.</p> <p>Do <strong>not</strong> use <em>Duplicate</em>.</p> </div> </div> <div> <div>Copy of <Object></div> <div> <p>Title of a new object until the name has been defined.</p> <p><u>Example</u>:<br><span class="icon icon-accept"></span><em>Copy of Purchase Order 12345678</em></p> </div> </div>
Use of “Country”
<div> <div>Label</div> <div>Description</div> </div> <div> <div>Country/Region</div> <div> <p>Do not use the label <em>Country</em> for politically controversial territories or special regions.</p> <p>This affects all values or selection lists that may contain such territories.</p> <p>An alternative label might be <em>Country/Region</em>, depending on your context.</p> <p>[internal_only]</p> <p>For more information see the <a href="https%3A%2F%2Fhelp.sap.com%2Fviewer%2FDRAFT%2Fe33c591ae4494a659a3f5f983c9d1161%2FPROD%2Fen-US%2F7ea0335681d94c81a2f5d1a31518906e.html">SAP Style Guide for Technical Communication</a><br>(section: <em>The Term “Country” and Its Political Dimension</em>).</p> <p>[/internal_only]</p> </div> </div>
Exporting content
Use the following standard labels for download icons in a toolbar.
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Export to Spreadsheet</div> <div> <p>Export to a spreadsheet application.</p> <p>Don’t refer to specific products.</p> <p><u>Example</u>:<br><span class="icon icon-decline"></span><em>Export to Excel</em></p> </div> </div> <div> <div>Export to PDF</div> <div>Export as a PDF file.</div> </div>
Global actions
Use the following standard labels for the global actions toolbar.
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Copy</div> <div>Copy the current object to create a new object.</div> </div> <div> <div>Edit</div> <div>Make changes to an existing object.</div> </div> <div> <div>Delete</div> <div>Delete the current object.</div> </div> <div> <div>Share</div> <div>Tooltip for the <span class="icon icon-action"></span><em>Share</em> icon.</div> </div>
Local actions – table toolbar
Use the following labels for standard actions in the table toolbar.
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Add</div> <div>Add an existing object or item to a list.</div> </div> <div> <div>Copy</div> <div>Copy the selected object to create a new object.</div> </div> <div> <div>Create</div> <div>Create a new object or item.</div> </div> <div> <div>Edit</div> <div>Make changes to the selected object.</div> </div> <div> <div>Delete</div> <div>Delete the selected object.</div> </div> <div> <div>Sort</div> <div>Tooltip text for the <span class="icon icon-sort"></span><em>Sort</em> icon.</div> </div> <div> <div>Filter</div> <div>Tooltip text for the <span class="icon icon-filter"></span><em>Filter</em> icon.</div> </div> <div> <div>Group</div> <div>Tooltip text for the <span class="icon icon-group-2"></span><em>Group</em> icon.</div> </div>
Navigation
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Back</div> <div>Go back to the previous screen.</div> </div> <div> <div>Open [app]</div> <div>Open an SAP Fiori app.<br>Note: In the SAP Fiori environment, use the term “open” rather than “launch”.</div> </div> <div> <div>Open in <App Name></div> <div>Open the current item in another app.</div> </div> <div> <div>Open In…</div> <div>Show a list of apps in which the current item can be opened.</div> </div>
“No Data” texts
<div> <div>Use case</div> <div>Guideline</div> </div> <div> <div>No data is available</div> <div> <p>When no data is available for the selection or filter criteria entered by the user, SAPUI5 displays a “No data” text by default. <strong>Replace the “No data” text with a more specific text</strong>:</p> <ul> <li>Where appropriate, refer to the business object handled by your app.</li> <li>If the user needs to change a setting to see data, offer a hint.</li> </ul> <p><u>Examples</u>:</p> <p><span class="icon icon-accept"></span><em>No matching products found</em> (for example, in the list of a list-detail app)</p> <p><span class="icon icon-accept"></span><em>No products found. Try adjusting your search and filter settings.</em> (for example, when no items are found for the selected filter criteria in a <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fpage-types%2Ffloorplans%2Flist-report-floorplan-sap-fiori-element%2F%23table">list report table</a>)</p> </div> </div>
Object administration
Standard labels
For object admin data, use the following standard labels:
Created By
Created On
Changed By
Changed On
If your app family has consistently used different labels (such as Last Changed By or Last Changed On), consider using the existing labels for new apps to avoid inconsistencies.
If you are showing a relative date (such as Today or Yesterday), or a mixture of relative and absolute dates, use the labels Created and Changed instead of Created On and Changed On.
Translation
To ensure translatability, the label and value placeholder must be in a single text string.
“Created By: <variable for name>”
Combined date/time fields
In many apps, the date is the main reference point, even if both the date and time are shown. In this case, use the field labels Created On and Changed On.
If the time is an important reference point for users, include both elements in the label: Created On / Created At (or shorten to Created On/At) Changed On / Changed At (or shorten to Changed On/At)
Do not use Created At and Changed At as labels for joint fields where the date comes first.
If users need to scan the exact times, consider using a separate field for the time to make scanning easier: Created At Changed At
SAP S/4HANA: Do not use separate fields for the date and time. Always use the combined date/time stamp for the relevant time zone.
<div> <div>Use case</div> <div>Guideline</div> </div> <div> <div>Standard interaction and processes</div> <div> <p>Use “please” judiciously.</p> <p>Do not use “please” unless you would also use it naturally in a spoken conversation. Base your decision on your target group and language.</p> </div> </div> <div> <div>System constraint or error</div> <div>Consider using “please” if you are inconveniencing the user.</div> </div>
Removing and deleting items
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Delete</div> <div> <p>Delete the <strong>object or item itself</strong>. Use <em>Delete</em> if the object or item has already been <strong>actively</strong> saved.</p> <p><u>Example</u>:<br>Delete an order from the database.</p> </div> </div> <div> <div>Discard</div> <div> <p>Discard a draft for a new object, or draft changes to an existing object. Use <em>Discard</em> if the object or item has <strong>not yet been actively saved</strong> by the user.</p> <p><u>Example</u>:<br>Discard the changes you started making to the measurements for product A.</p> </div> </div> <div> <div>Remove</div> <div> <p>Remove the <strong>reference to an item</strong>.</p> <p><u>Example</u>:<br>Remove contacts from a distribution list.</p> </div> </div>
Setting favorites
The tooltip label for the :icon-favoriteFavorite icon depends on how the app handles favorites:
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Mark as Favorite</div> <div>Flag an item as a favorite without adding it to a list of favorites.</div> </div> <div> <div>Add to Favorites</div> <div>Flag an item as a favorite and add it to a list of favorites that the user can call up independently.</div> </div>
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Show Details</div> <div>Show more information within the same page or dialog (for example, a message long text within a message dialog).</div> </div> <div> <div>View Details (Charts)</div> <div>Display additional information about a chart.</div> </div> <div> <div>Show More</div> <div>Expand a list or screen area.</div> </div> <div> <div>Show Less</div> <div>Collapse a list or screen area.</div> </div> <div> <div>Show All</div> <div>Show all the items in a list.</div> </div>
Signing in and out
<div> <div>Action</div> <div>Description</div> </div> <div> <div>Sign In</div> <div> <p>Standard label for logging into SAP applications. [internal_only]Part of the UX consistency product standard for terminology, <a href="https%3A%2F%2Fwiki.one.int.sap%2Fwiki%2Fdisplay%2Fuxc%2FUXC-015">UXC-015</a>. [/internal_only]</p> <p><span class="icon icon-accept"></span><em>Sign In</em><br><span class="icon icon-decline"></span><em>Log In</em><br><span class="icon icon-decline"></span><em>Log On</em></p> </div> </div> <div> <div>Sign Out</div> <div> <p>Standard label for logging out of SAP applications. [internal_only]Part of the UX consistency product standard for terminology, <a href="https%3A%2F%2Fwiki.one.int.sap%2Fwiki%2Fdisplay%2Fuxc%2FUXC-015">UXC-015</a>. [/internal_only]</p> <p><span class="icon icon-accept"></span><em>Sign Out</em><br><span class="icon icon-decline"></span><em>Log Out</em><br><span class="icon icon-decline"></span><em>Log Off</em></p> </div> </div>
Validity period
<div> <div>Label</div> <div>Guideline</div> </div> <div> <div> <p><em>Valid From</em></p> <p><em>Valid To</em></p> </div> <div> <p>For a validity period, use the labels <strong><em>Valid From</em></strong> and <strong><em>Valid To</em></strong>.</p> <p>If you have only one label for both values, use the label <strong><em>Valid From/To</em></strong>.</p> </div> </div>
Writing for AI
The AI Design Team are developing standard UI texts for use with AI features.
We are currently aligning and cross-referencing the UI text guidelines in this overview and in the individual design guideline articles. However, this is still work in progress. Our goal is to create an overview of all text-related guidelines. In the meantime, please also refer to the guideline articles for the individual controls, patterns, and floorplans.
Formulate button texts as actions, starting with a verb, and keep them as short as possible.
Approve Order
Simulate Payment Run
Payment Run
Display Elements
Tooltip
Note: Tooltips appear only on desktop devices, and not on mobile/touchscreen devices.
Use tooltips only to show the labels for elements that have no text, such as icons.
Use title case.
Icon buttons
If the icon represents an action, formulate the tooltip as an action, starting with a verb. Exception: Standard labels used across the IT industry, such as Settings.
Describe the action that will be triggered by pressing the button. For example, :icon-slim-arrow-downExpand Header, :icon-slim-arrow-upCollapse Header.
If the icon button is a toggle button that merely changes its state (same icon button, “on” or “off” state), always use the positive action for the label. For example, :icon-pushpin-offPin Header for both pinned and unpinned states.
Don't use tooltips if:
A text label already exists. Do not create (redundant) tooltips for field labels that are written out in full and visible on the desktop.
You want to abbreviate a text label. Instead, write the label out in full and ask development/UX to allow enough space for texts in all languages to avoid truncation. Always aim for a responsive solution that will allow users to view the full text on all devices.
You want to provide an explanation. For embedded help, use the SAP Companion instead.
icon-actionShare icon-excel-attachmentExport to Spreadsheet icon-full-screenMaximize icon-exitfullscreenMinimize :icon-declineDisplays the orders you have already processed (additional tooltip for “Completed” label)
SAP Fiori uses a variety of messaging elements for different purposes. This section covers general guidelines for SAP Fiori messages, as well as text guidelines for specific message types.
General Message Guidelines
<div> <div>Topic</div> <div>Guideline</div> </div> <div> <div>“Please”</div> <div> <p>Avoid overusing “<a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23please">please</a>” in message texts. For example, it’s often not necessary when asking users to correct their entries.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>The system is currently unavailable. Please try again later.</em><br><span class="icon icon-accept"></span><em>Include at least one symbol in your password.</em></p> </div> </div> <div> <div>Singular/plural</div> <div>Use separate strings for <a href="http%3A%2F%2Fsingularplural-form%2F">singular and plural cases</a>. Do not use “(s)”.</div> </div> <div> <div>Semicolons</div> <div> <p>Don’t use semicolons to separate phrases in a message text. Instead, use two separate sentences ending with periods.</p> <p>Although semicolons are not incorrect, you are unlikely to see semicolons in modern mobile app interfaces.</p> </div> </div> <div> <div>Variables</div> <div> <p>Use a single string for messages, including variables. This is necessary to enable translators to change the word order for other languages.</p> <p>If you need to set off text variables in messages, use double <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23quotation-marks">quotation marks</a>. Do not use text variables. This can lead to grammatical errors in other languages.</p> <p>Examples:<br><span class="icon icon-accept"></span><em>“<processed items> of <total items> items were processed.”</em><br><span class="icon icon-accept"></span><em>“This item was closed on <date> by <name>.”</em><br><span class="icon icon-decline"></span><em>“The item was deleted by” + “<name>”</em> (two concatenated strings)<br><span class="icon icon-decline"></span><em>“The <business object> <business object number> was deleted.”</em> (the article for an unknown business object name cannot be translated correctly)</p> <p>Before using variables, consider using distinct error messages for each use case. This often allows you to write a friendlier text that is easier to read and translate than a text designed for reuse.</p> </div> </div>
Form Field Validation
Instruct the user what to do to correct the error. Avoid generic error messages.
Select a supplier Invalid entry Enter a valid value
If a value for a required field is missing, use the standard formulation:
<div> <div>Topic</div> <div>Guideline</div> </div> <div> <div>Heading</div> <div> <p>For <strong>message</strong> dialogs, use only the standard headings: <strong><em>Error</em></strong>, <strong><em>Warning</em></strong>, <strong><em>Information</em></strong>, <em><strong>Success</strong>.</em></p> <p>For <strong>confirmation</strong> dialogs, use the imperative of the <strong>action being confirmed.</strong> If the context is clear, only use the verb.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Delete</em><br><span class="icon icon-accept"></span><em>Approve</em></p> <p>If the verb alone would be ambiguous, add a qualifier.</p> <p><u>Example</u>:<br><span class="icon icon-accept"></span><em>Delete History</em></p> <p><strong>Special Case: Confirming Deletion</strong><br>Delete confirmations use a warning message box with <strong><em>Delete</em></strong> as the heading and button. See <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Fmessage-box%2F%23Messaging-FormFieldValidation7">Delete Message</a>.</p> </div> </div> <div> <div>Message text</div> <div> <p>Avoid showing system or configuration details in a message short text. Move technical information to the long text.</p> <p>Do not repeat the short text in the long text. Otherwise, the text shows twice when the long text is expanded.</p> <p><strong>Confirmation prompts</strong>: If your target user is likely to see the message frequently, use a short form that’s easy to scan.</p> <p>Examples:<br><span class="icon icon-accept"></span><em>Approve order 12345?</em><br><span class="icon icon-decline"></span><em>Do you really want to approve order 12345?</em></p> <p><strong>Confirmation prompts</strong>: If the confirmation dialog allows the user to enter a note, use sentence style for the input prompt.</p> <p><strong>Success messages</strong>: Do not use “successfully.”</p> </div> </div> <div> <div>Buttons</div> <div> <p>Use <strong>action verbs</strong> for buttons in all dialogs that involve a <strong>decision with a specific action</strong>.</p> <p><u>Exception</u>: If naming the action takes up too much space, formulate the message as a statement, and use the <strong><em>OK</em></strong>/<strong><em>Cancel</em></strong> buttons. Also consider translation. If the mobile use case is critical for your application, always test on a mobile device.</p> <p><strong>Error messages</strong>: Use <strong><em>Close</em></strong> instead of <em>OK</em> as the button text for closing an error message. Use <strong><em>OK</em></strong> if the user is just acknowledging a piece of information or a group of settings.</p> <p>Do not combine questions with <em>OK</em>/<em>Cancel</em> buttons. Avoid <em>Yes/No</em> buttons.<br>Reason: Like <em>OK</em>/<em>Cancel</em> buttons,<em>Yes</em>/<em>No</em> buttons force the user to read the whole message text.</p> </div> </div>
Use title case for the headings in anchors or tabs.
Avoid repeating the section/anchor heading in a subsection heading.
If different apps in your app family group data in similar ways, consider aligning the section headings.
Tables
Column Headings
<div> <div>Topic</div> <div>Guideline</div> </div> <div> <div>Column headings with multiple labels</div> <div> <p>If a table column contains multiple values, use a slash to separate the labels in the column heading. Include a space before and after the slash.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Price / Local Currency</em><br><span class="icon icon-decline"></span><em>Price/Local Currency</em></p> </div> </div> <div> <div>Singular vs. plural</div> <div> <p>Use the singular in the column heading if there is only one entry per table row.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Product</em> (each row contains one product)<br><span class="icon icon-accept"></span><em>Contacts</em> (each row can contain more than one contact)</p> </div> </div>
Table Content
<div> <div>Topic</div> <div>Guideline</div> </div> <div> <div>Blank/empty fields</div> <div> <p>Leave fields without a value blank.</p> <p>Examples:<br><span class="icon icon-accept"></span><em>” “</em> (blank)<br><span class="icon icon-decline"></span><em>–</em> (hyphen)<br><span class="icon icon-decline"></span><em>N/A</em></p> </div> </div> <div> <div>Table fields with “null” values</div> <div> <p>If the back end returns a “null” value for a table field, also leave the field blank. In most use cases, it will not be critical for end users to know exactly why a field is not filled (“null” value that is never supplied by the back-end system, or “empty” value that might be filled later).</p> <p><strong>In exceptional cases only</strong>: If it is critical for your use case to distinguish between “null” and “empty” values, you can consider showing a text for either “null” values or “empty” values.</p> <ul> <li>If you have one or two fields where a value is not available yet, but expected or possible later, a text such as “Pending” or “Not yet available” could give the user a hint.</li> <li>If you have just one or two fields with “null” values, a standard text “Unknown” could serve as a differentiator. In this case, however, you should ensure that “Unknown” is not a possible value in your dataset.</li> </ul> <p>If you are likely to have several “empty” and “null” value fields in your table, we strongly recommend leaving all the fields blank. This makes the table much easier to scan and helps users recognize fields that are actually populated.</p> </div> </div>
User Input
Input Field
<div> <div>Topic</div> <div>Guideline</div> </div> <div> <div>Placeholder</div> <div> <p>Only offer placeholder text (input prompt) if you need to provide an additional hint. Do <strong>not</strong> repeat the label in the placeholder text.</p> <p>Never use placeholders instead of labels.</p> <p>Use sentence case.<br><u>Exception</u>: The input prompt describes a format with specific capitalization (for example, lower case for a URL).</p> <p>Do not use a period or ellipsis at the end of the text.<br><u>Exception</u>: The input prompt describes a format containing a period.</p> <p>Use a consistent style for all input prompts on one page (the style may vary, depending on your use case).</p> <p>For URL or email address placeholders, use the domain <strong><em>example.com</em></strong>.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>Select a building by location</em><br><span class="icon icon-accept"></span><em>www.example.com</em><br><span class="icon icon-accept"></span><em><a href="mailto%3Ausername%40example.com">username@example.com</a></em><br><span class="icon icon-decline"></span><em>Select a product category</em> (when the label is <em>Product Category</em>)</p> </div> </div> <div> <div>Showing a previous value</div> <div> <p>If you need to indicate the previous value for a field, add the following text after the field value:</p> <p><strong><em>Previously: <Old Value></em></strong></p> <p>Note: This is not a standard feature for forms, but may be required for some use cases.</p> <p><u>Example</u>:<br><span class="icon icon-accept"></span><em>Supplier: DelBont Industries Previously: Company ABC</em></p> </div> </div>
Selection List Options
<div> <div>Topic</div> <div>Guideline</div> </div> <div> <div>No options selected</div> <div> <p>Relevant for: <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Fselect%2F">Select</a>, <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Fselect-dialog%2F">Select Dialog</a>, <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Ftable-select-dialog%2F">Table Select Dialog</a>, <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Fradio-button%2F">Radio Button</a></p> <p>If you need to indicate that none of the options in a list are selected, provide a corresponding text. Show the text at the beginning of the list and place it in parentheses to distinguish it from the other values. Do not leave the entry blank.</p> <p>Use a text that best fits your use case and the content of your list, such as <em>(Not Selected), (Not Assigned),</em> or an app-specific text such as <em>(No Supplier Selected)</em>.</p> <p>Do not use <em>(None)</em>. Although “None” works in English, it is difficult to translate correctly into languages with gendered nouns.</p> <p><u>Examples</u>:<br><span class="icon icon-accept"></span><em>(Not Selected)</em><br><span class="icon icon-accept"></span><em>(Not Assigned)</em><br><span class="icon icon-accept"></span><em>(No Product Selected)</em><br><span class="icon icon-decline"></span><em>(None)</em></p> </div> </div> <div> <div>All options selected</div> <div> <p>If a list is used for filtering, and you need to indicate that all values are included, offer an <em>All</em> option it at the beginning of the list.</p> <p><u>Examples</u>:<br><em>All</em><br><em>France</em><br><em>Germany</em><br><em>Italy</em><br><em>Spain</em></p> <p>Here, <em>All</em> indicates that no filters have been set. France, Germany, Italy, and Spain are all included.</p> <p>Relevant for: <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Fselect%2F">Select</a>, <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Fselect-dialog%2F">Select Dialog</a>, <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Ftable-select-dialog%2F">Table Select Dialog</a>, <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Fui-elements%2Fradio-button%2F">Radio Button</a></p> </div> </div>
Wizard Floorplan
Wizard Steps
If you are using the wizard floorplan, formulate the texts for each step as follows:
Use a noun for the name of the step (for example, Customer). This text appears in 3 places:
The header of the walkthrough screen (showing all steps)
The heading for each step on the walkthrough screen
The heading for each section on the summary screen
Offer an explanatory text for each step in the walkthrough screen (sap.m.text). Phrase this text as an instruction (for example, Enter the payment details.) Note: This explanatory text does not show in the wizard summary.
information
At the moment, it is not possible to formulate the step name in the walkthrough screen as an instruction because the same text is used in the process header and summary screen. We plan to split these texts in a future release.
[internal_only]
Change History
<div> <div>Date</div> <div>Section</div> <div>Change</div> </div> <div> <div>2025-09-02</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23punctuation">Punctuation</a> – Quotation Marks</div> <div> <p>When referring to UI texts in messages, quotes are only needed when referencing the text as it appears on the screen (for example, capitalized field labels).<br><br><em>Former text:</em><br>Use quotation marks if:<br>Your message or description <strong>refers</strong> to a text on the <strong>screen</strong>.</p> <p><em>Updated text:</em><br>Use quotation marks if:<br>Your message or description <strong>quotes a label or text</strong> on the <strong>UI</strong>.</p> </div> </div> <div> <div>2024-09-09</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23writing-for-ai">Writing for AI</a></div> <div>“Writing for SAP CoPilot” section replaced by “Writing for AI”. This section references the <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fai-ui-text">AI UI Text</a> guidelines created by the AI Design Team.</div> </div> <div> <div>2022-10-26</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23ellipsis-">Punctuation – Ellipsis</a></div> <div>“Don’t” example added. Do not use the ellipsis for menu items.</div> </div> <div> <div>2022-05-03</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23what-about-combined-datetime-fields-">Combined Date/Time Fields</a></div> <div>Don’t use separate date and time fields in SAP S/4HANA. Use the timestamp with the combined date and time instead.</div> </div> <div> <div>2022-02-25</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23period">Punctuation – Period</a></div> <div>Exceptions: No ending period in the heading for illustrated messages.</div> </div> <div> <div>2021-10-14</div> <div>Application Names – <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23transactional-or-hybrid-apps">Transactional or Hybrid Apps</a></div> <div>If the main focus of an app is on processing items, start the app name with “Process”.</div> </div> <div> <div>2021-10-12</div> <div>Application Names – <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23transactional-or-hybrid-apps">Transactional or Hybrid Apps</a></div> <div>If an app is used to both create new objects and edit existing objects, use “Manage” as the verb (already a de facto standard in the app names).</div> </div> <div> <div>2021-06-28</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23quotation-marks">Quotation Marks</a></div> <div>Clarified use cases for quotes in messages/descriptions. Separate subsections on when to use / when not to use quotes.</div> </div> <div> <div>2021-06-04</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23selection-list-options">User Input – Selection List Options</a></div> <div> <p>New section on formulating selection list labels for “no options selected” or “all options selected”.</p> <p>Note: The previous rule to use “None” when no items are selected no longer applies. “None” is hard to translate correctly. A translatable text like “Not Selected” is preferable.</p> </div> </div> <div> <div>2020-08-25</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23tooltip">Tooltip</a></div> <div>Tooltip for icon toggle buttons: Always describe the positive state. Same tooltip for “on” and “off” states.</div> </div> <div> <div>2020-07-24</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23word-choice">Word Choice</a></div> <div> <p><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23navigation-actions">Navigation actions</a></p> <p>are now in a separate subsection. “Back” and “Previous” were added.</p> <p>Include a qualifier with “Next” and “Previous” to enable translation.</p> </div> </div> <div> <div>2019-11-11</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23navigation">Word Choice – Navigation</a></div> <div>Added <em>Open</em> as preferred verb for opening an app. Don’t use <em>Launch</em> in the SAP Fiori environment.</div> </div> <div> <div>2019-08-14</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23validity-period">Word Choice – Validity Period</a></div> <div>Added <em>Valid From</em> and <em>Valid To</em> as standard labels for a validity period. If there is only one label for both “From” and “To” fields, use the label <em>Valid From/To</em>.</div> </div> <div> <div>2019-06-24</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23ellipsis-">Punctuation – Ellipsis</a></div> <div> <p>Guideline previously advised using the ellipsis if “a menu item leads to set of further selection options”.</p> <p>This has been changed to “a menu item leads to a set of further menu items”.<br>Reason: We do not want to use the ellipsis after every button that leads to a detailed dialog.</p> <p>Added <em>Browse…</em> as an exception. The ellipsis here is a standard convention.</p> </div> </div> <div> <div>2019-03-07</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23object-administration">Word choice – object administration</a></div> <div>Exception added: If the value for a date field can contain a relative date (like “Yesterday”), use “Created” or “Changed” instead of “Created On” and “Changed On”.</div> </div> <div> <div>2019-02-26</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23quotation-marks">Quotation marks</a></div> <div>Developer hint removed. Standard double quotes (“) can be used to set off text, if necessary. It’s no longer necessary to create double quotes manually using two single quotes.</div> </div> <div> <div>2019-02-12</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23word-choice">Word Choice</a></div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23country">Country</a> entry added. The label “Country” is not appropriate for territories that do not have formal “country” status, and can result in legal issues for SAP (especially in China).</div> </div> <div> <div>2019-02-01</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23word-choice">Word Choice</a></div> <div>“Personalize” removed from section <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23local-actions-table-toolbar">local actions in the table toolbar</a>.<br>Reason: In most cases, standard “Settings” label is used instead.</div> </div> <div> <div>2018-07-12</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23word-choice">Word Choice</a></div> <div>Section added for <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23local-actions-table-toolbar">local actions in the table toolbar</a>.</div> </div> <div> <div>2018-07-09</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23word-choice">Word Choice</a></div> <div>Section added for standard <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23global-actions">global actions</a>.</div> </div> <div> <div>2018-07-06</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23creating-an-object-or-item">Creating an object or item</a></div> <div>Clearer delineation between “Create” and “Add”:<br>Create -> for objects being created from scratch on the database<br>Add -> for adding objects that already exist on the database</div> </div> <div> <div>2018-06-22</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23singularplural-form">Singular/plural form</a></div> <div>Differentiate between titles and label (always use the plural) and explanations/messages (use singular or plural form, depending on the value).</div> </div> <div> <div>2018-05-24</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23object-administration">Object administration</a></div> <div>Guidelines added for <a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23what-about-combined-datetime-fields-">combined date/time fields</a>.</div> </div> <div> <div>2018-05-14</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23removing-and-deleting-items">Removing and deleting items</a></div> <div>Use of “Delete” only for actively saved objects.<br>Added missing action “Discard”.</div> </div> <div> <div>2018-05-08</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23navigation-action">Completing an action</a></div> <div>Added missing actions “Create” and “Add”.<br>Clarified use of “Create”.</div> </div> <div> <div>2018-05-08</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23creating-an-object-or-item">Creating an object or item</a></div> <div>Added missing action “Add”.<br>Modified definition for “Create”.</div> </div> <div> <div>2018-04-24</div> <div><a href="https%3A%2F%2Fwww.sap.com%2Fdesign-system%2Ffiori-design-web%2Ffoundations%2Fwriting-and-wording%2Fux-writing%2Fui-text-guidelines-for-sap-fiori%23form-field-validation">Form field validation</a></div> <div>Standard text added for missing required fields.</div> </div>
