This note is actually opened when the Note Map feature that is accessed from the Launch Bar.
It is possible to create any child notes in it without any additional meaning. For example, it can be used to store a list of note maps which can be linked to from other notes or bookmarked.
Whenever a search is executed from the full Search, the query will be stored here, grouped by month. Only the search parameters are stored and not the results themselves.
This section can be accessed without going to the hidden tree by simply going to the Global menu and selecting Advanced → Open Search History.
Notes can be added as children of this tree, but it's generally not recommended to do so to not interfere with the normal history process.
This section can be used by scripts to create their own notes that should not be directly visible to the user. The note can be identified by scripts by its unique ID: _userHidden
This tree lists all of the notes that are shared publicly. It can be useful to track down which notes are shared regardless of their position in the note tree.
This section can be accessed without going to the hidden tree simply by going to the Global menu and selecting Show Shared Notes Subtree.
This is where the note structure for the User Guide is actually stored. Only the metadata is stored, as the help itself is present as actual files in the application directory.
This note is actually opened when the Note Map feature that is accessed from the Launch Bar.
It is possible to create any child notes in it without any additional meaning. For example, it can be used to store a list of note maps which can be linked to from other notes or bookmarked.
Whenever a search is executed from the full Search, the query will be stored here, grouped by month. Only the search parameters are stored and not the results themselves.
This section can be accessed without going to the hidden tree by simply going to the Global menu and selecting Advanced → Open Search History.
Notes can be added as children of this tree, but it's generally not recommended to do so to not interfere with the normal history process.
This section is used for Bulk Actions. The last configuration for bulk actions will be stored as part of this note, each action in its own action label.
Notes can be added as children of this tree, but there won't be any benefit in doing so.
This section can be used by scripts to create their own notes that should not be directly visible to the user. The note can be identified by scripts by its unique ID: _userHidden
This tree lists all of the notes that are shared publicly. It can be useful to track down which notes are shared regardless of their position in the note tree.
This section can be accessed without going to the hidden tree simply by going to the Global menu and selecting Show Shared Notes Subtree.
This is where the note structure for the User Guide is actually stored. Only the metadata is stored, as the help itself is present as actual files in the application directory.
Labels can
be used for a variety of purposes, such as storing metadata or configuring
- the behaviour of notes. Labels are also searchable, enhancing note retrieval.
-
- For more information, including predefined labels, see
+
For more complex scenarios, it is possible to type in a JavaScript expression
- in order to apply the necessary changes.
-
To apply a suffix (- suffix in this example), to the note
- title:
note.title = note.title + " - suffix";
-
To alter attributes of a note in a bulk action, such as setting the #shareAlias label
- to the title of the note:
note.setLabel("shareAlias", note.title)
+
+
+
+
The Bulk Actions dialog makes it easy to apply changes to multiple
+ notes at once, ranging from simple actions such as adding or removing a
+ label to being executing custom scripts.
+
Interaction
+
+
The first step is to select the notes in the Note Tree:
+
+
It's possible to apply bulk actions to a single note (and potentially
+ its child notes) simply by clicking on it (with a left click or a right
+ click).
+
To select a range of notes, select the start note, hold Shift and
+ select the end note. The selected notes will appear highlighted in the
+ note tree.
+
+
+
Right click in the Note Tree and
+ select Advanced → Apply bulk actions.
+
By default, only the selected notes will be affected. To also include
+ all the descendants of the notes, check Include descendants of the selected notes.
+ The number of affected notes at the top of the dialog will update to reflect
+ the change.
+
Click on which action to apply from the Available actions section.
+ A detailed description of each is available in the next section.
+
+
For each action selected, the Chosen actions section will update
+ to reveal the entry. Each action will have its own configuration.
+
To remove an action, simply press the X button to the right of it.
+
It is possible to apply multiple actions of the same type, such as adding
+ multiple types.
+
+
+
When all the actions are defined, press Execute bulk actions to
+ trigger all of them at once.
+
For convenience, the last bulk action configuration is saved for further
+ use and will be restored when entering the dialog again.
For each note, if it doesn't already have a label of
+ the given name, it will create it. Keep the New value field empty
+ to create a label without a value, or complete it to assign a value.
+
If a note already has this label, its value will be updated.
+
+
+
Update label value
+
+
For each note, if it has a label of
+ the given name, it will change its value to the specified one. Leave New value field
+ empty to create a label without a value.
+
Notes without the label will not be affected.
+
+
+
Rename label
+
+
For each note, if it has a label of
+ the given name, it will be renamed/replaced with a label of the new name.
+ The value of the label (if present) will be kept intact.
+
Notes without the label will not be affected.
+
+
+
Delete label
+
+
For each note, if it has a label of a given name, it will be deleted (regardless
+ of whether it has a value or not).
For each note, it will create a relation pointing to the given note.
+
Notes without this relation will not be affected.
+
+
+
Update relation target
+
+
For each note, it will modify a relation to point to the newly given note.
+
Notes without this relation will not be affected.
+
+
+
Rename relation
+
+
For each note, if it has a relation of the given name, it will be renamed/replaced
+ with a relation of the new name. The target note of the relation will be
+ kept intact.
+
Notes without this relation will not be affected.
+
+
+
Delete relation
+
+
For each note, if it has a relation of the given name, it will be deleted.
+
Notes without this relation will not be affected.
+
+
+
+
Notes
+
+
Rename note
+
+
For each note, it will change the title of the note to the given one.
+
As a more advanced use case, the note can be a “template string” which
+ allows for dynamic values with access to the note information via
+ FNote, for example:
+
+
NEW: ${note.title} will prefix all notes with NEW: .
+
${note.dateCreatedObj.format('MM-DD:')}: ${note.title} will
+ prefix the note titles with each note's creation date (in month-day format).
+
+
+
+
+
Move note
+
+
For each note, it will be moved to the specified parent note.
+
As an alternative for less complex situations, the notes can be moved
+ directly from within the Note Tree via
+ cut → paste or via the contextual menu.
+
+
+
Delete note
+
+
For each note, it will be deleted.
+
As an alternative for less complex situations, the notes can be removed
+ directly from within the Note Tree by
+ selecting them and pressing Delete.
This section is used for Bulk Actions.
+ The last configuration for bulk actions will be stored as part of this
+ note, each action in its own action label.
+
Notes can be added as children of this tree, but there won't be any benefit
+ in doing so.
+
Backend Log
diff --git a/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Workspaces.html b/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Workspaces.html
index 8248864a1..ba02c1a86 100644
--- a/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Workspaces.html
+++ b/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Workspaces.html
@@ -20,17 +20,21 @@
care about personal notes.
So far workspace consists of these features:
-
note hoisting - you can "zoom" into
- a workspace subtree to focus only on the relevant notes
+
+
note hoisting - you can "zoom" into
+ a workspace subtree to focus only on the relevant notes
+
easy entering of workspace:
-
visual identification of workspace in tabs:
-
-
+
+
visual identification of workspace in tabs:
+
+
+
Configuration
diff --git a/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Note Tree.html b/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Note Tree.html
index 530a8aaca..657385b07 100644
--- a/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Note Tree.html
+++ b/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Note Tree.html
@@ -55,7 +55,7 @@
In the right-click menu, operations such as Cut, Copy, Move to, Clone
to or Delete will apply to all the selected notes. It is also possible
- to apply Bulk actions to
+ to apply Bulk actions to
them. The rest of the options will not be available and will appear disabled
in the menu.
Other events are bound to some entity, these are defined as relations -
meaning that script is triggered only if note has this script attached
to it through relations (or it can inherit it).
+ 
+