This is a guideline, some parts are optional (if there's no content you need to add to some paragraphs, remove the whole part). <Your name here in italics, plus your company name> Title Simple and suggestive. How would you like your pattern or cookbook to be named, when it will be mentioned by a group of C/AL developers discussing implementation by the coffee machine? A good title is memorable and descriptive. Abstract This is the abstract. No longer than a few lines, to determine the goal/purpose of this pattern or cookbook. Description What problem does this solve? When to use it. Diagrams if needed (no guideline here, use what diagrams best describe the idea). Usage This section provides a generic example (with diagrams if needed) on how to do the implementation. After reading this, the developer should be able to implement the pattern in his/her own code. Can contain code examples if needed. NAV Specific Example This is a real life (NAV demo) example of the implementation. Contains code examples or application screens if needed. NAV Usages A short list of where else in NAV this is used. Ideas for improvement And why do we think this improvement is worthwhile. What is the business reason? Consequences If applicable, add here the results and trade-offs of using this pattern or recipe, for example: - Disadvantages or limitations - Situations when using it doesn't fit or might be overdo. Related Topics A short mention of a related pattern (or other article) name and abstract. NAV Versions Example Supported from … Valid until … Obsoleted by pattern … Concrete example, pattern .NET exception handling: Supported from NAV 2015 Recommended usage until NAV 2015 R2 (the pattern still works here but new platform functionality had made a better practice possible, see the pattern <link to new pattern>) References Optional. Has this been described in NAV certification materials, published books or blogs? Add them here.