The Property Expression and Evaluation Modes in this article apply to Settings versions: 1.14, 1.16, 1.18 & 1.20
Expression and Evaluation Modes give you a great deal of flexibility but can be confusing. If you are unsure, we recommend sticking with the defaults that orgvue suggests.
The expression mode determines when a Gizmo expression will be run for a Property Cell.
Note: A Cell is an individual Property value of a Node. If you think of a Property as a column, and a Node as a row, then the Cell carries the value.
|Default||Where there is no value stored in the Cell, then the result of the expression is returned.|
|Initial||The expression is run when creating a Node, and the result of the expression is saved to the Cell. (It is not necessary to use setValue to persist the value). The cell can subsequently be edited.|
|Fixed||The expression will be evaluated for all Nodes, regardless of whether a Cell stores a value or not. The Cells are not editable within Workspace.|
Property Evaluation Modes
The evaluation mode determines How an expression will work. This area is complicated as orgvue has different options when saving a Gizmo expression within a Dataset in Settings and when saving an expression to a Pack in Workspace. This difference is due to maintaining backwards compatibility to OrgVue 2 and earlier versions of Workspace. Settings will be aligned to Workspace in future releases.
|Settings Evaluation Mode||Pack Property Evaluation Mode||Behaviour|
|None||N/A||The expression will be treated as a literal value, returned as entered in the expression box.|
|Auto||Pre-Filter||The expression will ignore any Filtering or Paging that is applied. The expression will be re-evaluated whenever data are edited.|
|On Demand||On Demand||The expression will be evaluated when you activate it in Workspace, and not automatically following edits. The return value of the expression will be saved to the Cell. Typically, On Demand is used alongside setValue expressions to update many Cells at once. An On Demand expression is always evaluated in the context of the active Filter and Paging.|
|Hierarchy||Post-Filter||The expression results depend on any active Filters. Evaluation occurs whenever data is edited or when the Filter is changed. You cannot Filter or Page on a Post-Filter (or Hierarchy) evaluated Property.|
|Script||N/A||A legacy mode which has no equivalence in OrgVue 3.|
As of 2021/08/05, there has been changes made to the Property Evaluation Mode names in order to align with Workspace. These changes do not change the results/behaviour. Please refer to article, “Property & Expression Modes – Workspace Aligned”, for the latest updates in Settings, version 1.22.
Please sign in to leave a comment.