Here is the link to the Format Formula as HTML database I built. Check it out and let me know your thoughts.
Feb
27
These four columns need to be named $144, $145, $146, and $147. This was the surprise, but what a better way to allow developers to control what can be printed. I find it interesting the choice in numbers, and that they have to be these numbers. Make sure that these numbers are used any other column, otherwise the data in the first column will appear in both. I would also recommend that you put the columns in ascending order according to the programmatic name because that is how they are printed, which we have no control over. The last ($147) column is made up of an array of four elements. The default calendar view has the following order Subject, Room, Location, and Chair. Once again the four elements can have any value.
Weekly Settings |
|
![]() |
|
Montly Settings |
|
![]() |
|
Calendar List Settings |
|
![]() |
|

Implementation:
The Link Message inherits values from the selected document.
Because this property is checked any field that has a default value will be populated just like it normally does when it is created, but any field from selected document is also available to be used, if it exists. The next step is to find out what the fields are inheriting from. These are the fields on the Link Message form.
Database, Workflow status, and Due date inherit from a single field.
Here are the field names that they inherit from (they happen to be the same as the field name):
Database: InheritedDBTitle
Workflow status: FlowStatus
Due date: DueDateTime
Because the Link Message can be created from anywhere (as described by Alan), I would recommend adding Link Message information to every form. Not every field needs to be populated by your application, so only choose the ones that apply. I recommend that the fields be computed so the information is available when creating a Link Message in a view. The fields should look like the following:
The Document/Subject follows the same logic but has more options. As shown, if there is a Subject field it will use that, otherwise it will use Topic, then Title and finally BriefDescription.
Document:
@If( @IsAvailable(Subject); Subject; @IsAvailable(Topic); Topic; @IsAvailable(Title); Title; @IsAvailable(BriefDescription); BriefDescription; "")
"Link Message"+ @If(@IsAvailable(InheritedSubject);": "+InheritedSubject;"")
@Command([Compose]; @MailDbName; "Bookmark")