| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | dialog number(+) | 0;1 | NUMERIC | B | The dialogue number is used to uniquely identify a message. | |
| 1 | type(+) | 0;2 | SET OF CODES | 1:ERROR 2:GENERAL MESSAGE 3:HELP | This code is used to group the entries in the FileMan DIALOG file, according to how they are used when interacting with the user. | |
| 1.2 | package(+) | 0;4 | POINTER | 9.4 | C | This is a pointer to the Package file. Each entry in this file belongs to, and is distributed by, a certain package. The Package field should be filled in for each entry on this file. |
| 1.3 | short description | 0;5 | FREE TEXT | D | Short description is used to identify an entry on lookup. The "WRITE" identifier will display this description if it is not null. | |
| 2 | description | 1;0 | WORD-PROCESSING | Used for internal documentation purposes. | ||
| 3 | internal parameters needed | 0;3 | BOOLEAN | y:YES | Some dialogue is built by inserting variable text (internal parameters) into windows in the word-processing TEXT field. The insertable text might be, for example, File or Field names. This field should be set to YES if any internal parameters need to be inserted into the TEXT. If the field is not set to YES, the DIALOG routine will not go through the part of the code that stuffs the internal parameters into the text. | |
| 4 | text | 2;0 | WORD-PROCESSING | Actual text of the message. If parameters (variable pieces of text) are to be inserted into the dialogue when the message is built, the parameter will appear as a 'window' in this TEXT field, surrounded by vertical bars. The data within the 'window' will represent a subscript of the input parameter list that is passed to BLD^DIALOG or $$EZBLD^DIALOG when building the message. This same subscript should be used as the .01 of the PARAMETER field in this file to document the parameter. | ||
| 5 | parameter | 3;0 | MULTIPLE | .845 | ||
| 6 | post message action | 6;E1,245 | FREE TEXT | If some special action should be taken whenever this message is built, MUMPS code can be entered here. This code will be executed by the BLD^DIALOG or $$EZBLD^DIALOG routines, immediately after the message text has been built in the output array. For example, the code could set a special flag into a global or local variable to notify the calling routine that some extra action needed to be taken. | ||
| 7 | translation | 4;0 | MULTIPLE | .847 | ||
| 8 | called from entry points | 5;0 | MULTIPLE | .841 |