The duality of objects of work—Distinguishing objects of work that live outside of an application from those that live inside of an application

Microsoft Dynamics AX product content comprises the terms, verbs, phrases, and sentences that appear on the user interface (UI), in tooltips, in exception messages, in the glossary, and subsequently, in help topics, and in white papers. In our product content, we should follow a practice of distinguishing objects of work that live outside of the…

0

Crafting an effective exception message

Microsoft Dynamics AX typically displays four classes of messages: Confirmation messages A confirmation message is displayed to verify whether the user wants to complete an action. For example: Do you want to save the changes to the customer registration? [Save, Do not save, Cancel] Error messages An error message is displayed when an exceptional condition…

0

Distinguishing between concepts in Microsoft Dynamics AX 2012: percent vs. percentage

In this blog entry we take a closer look at how we apply the concepts named percent and percentage in Microsoft Dynamics AX. We use the term percent to represent a proportional rate expressed in hundredths. For example: The organization’s profits increased 1.3 percent this quarter. A numeral is always used with the term percent in…

0

Distinguishing between concepts in Microsoft Dynamics AX 2012: stock vs. inventory

In this blog entry we take a closer look at how we apply the concepts named stock and inventory in Microsoft Dynamics AX 2012. But before we examine the concepts named stock and inventory, I offer some background on and a clarification of the term item, which is also applied in unique contexts with respect…

3

Distinguishing among concepts in Microsoft Dynamics AX 2012: commitment, agreement, and contract

In this blog entry we take a closer look at how we apply the concepts named commitment, agreement, and contract in Microsoft Dynamics AX. These concepts have two aspects: a social aspect and a documentation aspect. In the following conceptual object model, I offer a visualization of these two aspects and of the relationships among…

0

Content is the user interface

In Microsoft Dynamics AX, product content comprises all of the text—the terms, verbs, phrases, sentences, and so on—that appear on the user interface (UI), in tooltips, in error messages, in the glossary, and subsequently, in help topics, in white papers, and so on. Partners and customers use the Microsoft Dynamics AX application because they need…

0

The state of equilibrium: Balancing the voice of the application and the voice of the customer

When we consider which terms and words to use in Microsoft Dynamics AX product content, such as on the user interface, in the glossary, in error messages, in help topics, in white papers, and so on, we must continuously deliberate the two relationships of key elements that are inextricably linked: Voice and the audience. – and…

0

Measuring the quality of content submissions

In this blog entry I examine the practice that we apply for evaluating quality with respect to glossary entry submissions for the Microsoft Dynamics AX glossary. While the focus of this blog entry is on glossary entry submissions, the practice I document is applicable to all product content that we deliver, such as user interface…

0

How the practice of diagramming sentences enables our terminology practice

Who remembers how to diagram a sentence? For those of you for whom sentence diagramming is a distant memory, let me kindly offer a refresher—diagramming sentences is the practice of visually representing the grammatical structure of a sentence by differentiating the parts of a sentence that comprise a thought or a concept. The goal of…

0