Upgrading from DataSplice 4.0 Build 169
From DataSplice
Several minor changes were introduced with how actions are handled in the display settings section of the view editor, which will cause display and behavior issues in certain cases.
This document describes the configuration changes needed to use views created with DataSplice build 169 or earlier, with the latest versions.
Custom Events in Display Settings
Older versions of DataSplice required duplicate Execute Command navigation actions to be created in the view display settings that wrapped any custom events available as actions in the navigation menu. To simplify configuration, custom events can now be added directly to the navigation menu, and Execute Command actions no longer have a Command Type option to refer to custom events and view actions.
Views with the old configuration style will display errors when the actions are accessed by the user:
Steps to update the configuration:
- Ensure the Custom Event has the same name as the Navigation Action. For instance with the Work Orders view, rename the Start Clock custom event to Start Work. Otherwise any entries in the navigation menu collection will be lost.
- Delete execute action command from the Navigation Actions collection in the view display settings. The navigation menu bindings will now refer directly to the custom event.
The older DataSplice builds had a single Condition setting for entries in the navigation menu collection that controlled whether or not items were available in the display.
This has been changed to have two expressions: Condition controls whether or not the item is displayed in the first place, and Enabled specifies when the user is able to perform the action. This can reduce flashing behavior when the user is moving between records where particular actions may or may not be available.
In addition, the older versions used the Category setting to control which of the display modes the action would be displayed on. For instance, grid,record would only display the action in data modes.
In newer versions the Category setting is treated like the category setting in the home screen collection. The category can be set to an arbitrary name, which will group items with the same category in the display. Items with Normal display type will be grouped under sub menus with the category name, and Common display types will display a single button with the category name which will have a drop list of the grouped actions.
Views that specify the display mode in the item category will show strange buttons in the display with newer versions of DataSplice:
Steps to update the configuration:
- Evaluate the Condition statement and move some or all of the logic into the Enabled setting as needed. This needs to be done on a case by case basis depending on the intent of the original expression.
- Replace values in the category with condition statements with the same logic. The DisplayMode() method can be used to match a particular display mode.
For example, the following:
would be changed to:
The Create Work Order expression is left as is, because it is better to not display the item at all if the user does not have permission to create a record.
The expressions for Start Work and Stop Work are moved to control when the items are enabled. This prevents the buttons from flashing on and off the screen when the user moves between records.
The grid,record category settings, which prevent displaying the items on the search screen can be replaced with a DisplayMode() <> 'filter' condition.
