Scenario notes

scenario notes allow you to document and communicate essential details about your {{scenario singular lowercase}} with other make users notes serve as an effective way to provide context, instructions, or explanations about different parts of your {{scenario singular lowercase}} before you start using notes, keep in mind you can attach a note to any module or any route in your {{scenario singular lowercase}} each module or route can contain up to 200 notes each note has a 10,000 character limit when you use a lot of formatting, like emojis and links, you might reach the note length limit faster than without formatting make stores your notes in html format, which uses extra characters to set formatting create notes how to add a note to a module or route right click on the module or route where you want to add a note select add a note from the context menu enter your content in the text editor optional use the formatting toolbar to style your text, add links, or insert emojis click ok to save your note this is how notes are displayed in a scenario builder when a note is attached to a module a note is attached to a route view notes you have several options to view notes in your scenario what to do what you'll see mouse over the note marker a preview of the note click once on a note marker the complete note content with scrolling for longer notes click the sticky note icon in the toolbar the note panel showing previews of all scenario notes tips double click on a note to open it in edit mode manage notes how to edit notes double click on the note you want to modify make your changes in the text editor click ok to save your updates or cancel to discard them delete notes how to delete notes open the note you want to delete click the trash icon in the top right corner of the note window confirm you want to remove the note when prompted when you delete a note, this action is permanent and cannot be undone best practices use notes to document complex logic or explain non obvious workflow decisions add implementation details that might help other team members understand your approach document any specific requirements or dependencies for modules explain the purpose of different routes to clarify workflow branching keep notes concise but informative for better team collaboration