Table of Contents

, ,

Build 2916

New Features/Improvements

  1. Support for multi-column comboboxes
    1. Displayed Columns property for combos brings up a new dialog where you can define multi-column combo-boxes
    2. Pictures are supported (without custom templates)
    3. Custom Layout property has been moved to this new dialog
  2. Ability to build an HTML template used for custom queries (desktop and mobile)
    1. New “Build” button available instead of the predefned templates. This button brings up new Template Builder (based on Kendo UI cards)
    2. Kendo UI cards are used in the template
    3. Operations with records are supported in templates created by Template Builder
    4. Existing templates can be edited without losing information
    5. These templates and Template Builder can be used when defining a template for combo-boxes (operations are not available then)
    6. An example is available in the IssueResolution app (“All Staff” query)
  3. Calendar/Scheduler - search for appointments. New checkbox in the Calendar Pane.
  4. Ability to show steps for wizard forms (Stepper widget). The Panel Header dialog has a new option when wizard navigation is selected - to show steps in the header
  5. Support for the Timeline widget. Queries have a new Display As radio button - timeline. Multiple references have a new widget type - Timeline
    Images and Operations with Records are supported. An example is available in the Library sample app - Customer Editing form, Timeline tab (also in mobile). Also in Library - Loan History in the Item
  6. Support for image cropping and resizing. Display Settings dialog for a Picture attribute now has a checkbox whether to allow cropping and resizing.
    If this is on the user can click on an image and the Edit Image button will appear underneath. This button brings up the Image Editor widget.
  7. Visual Perspectives improvements:
    1. Support for “modern” style of display - when a header of a panel is displayed using Kendo Cards. There is a new property of a content panel called “Display Settings” which specifies whether to display using “modern” or “classic (same as before)” style.
    2. When a new content panel is being created the system asks about the contents straight away
    3. New property of the tab - “Default panel display settings”. These are default display properties of the new ContentPanel
    4. When a new tab is added the dialog displays that allows selecting layout and other properties of the tab straight away
    5. Layout editor for visual perspectives:
      1. Syncronization of panel selection in the tree and preview
      2. Double click on a panel in preview brings up Contents property
      3. It is possible to drag around panels in preview and change their location (all layouts except Border and Accordion)
      4. Preview on Desktop, Tablet and Phone for Responsive layouts
      5. Make panel wider/narrower for Responsive Grid Nested layout
      6. Maximize preview button that hides the tree and displays preview “full screen”
    6. Redesign of Content Panel Contents dialog
      1. Allow editing of all predefined elements
      2. Allow specifying Calendar, Google Map as separate components (as well as embed them into HTML)
      3. Date Range Picker component that allows specifying date range
  8. “Phone” and “Tablet” view for forms - extra buttons on the forms toolbar
  9. IN_CONTEXT function - check if the specified object is in Context
  10. Multi-step processes to implement complex wizards
    1. Every step has to be a process that ends with viewing some form. The process must set the value of the current step
      (using the Current Step Holder Expression property - the object specified in the expression must be in Context)
    2. A form needs to have Wizard Next and Wizard Prev panel operations if Next/Prev buttons are to be supported
    3. The form can display a stepper widget with a sequence of steps
    4. Multistep processes need to specify the name of the start process that kicks off the wizard. This process needs to be unique across different multi-step process (the wizard will kick off even if this process is used as a sub-process)
    5. A finish process can finish the wizard and set the value of the current step to UNDEFINED
    6. The end user can define his own sequence of steps and define which steps will be available. This is done with the new type of a command - User Defined Steps
  11. It is possible to specify an expression when defining badges, rather than using an attribute of an object
    (document using the EvaluateStringAction)
  12. Button-type cell in the Form Designser can be used to display multiple buttons
  13. It is now possible to add combo-boxes and text fields to toolbars of a form or query. When Editing a Toolbar in the Config. Tool there is a new option “Add Input” (under “Add Text”). This works similar to the current Input Control command in a visual perspective menu item (except that it runs an operation rather than command after data is saved. This feature allows creating complex filters for all types of parsers (currently we allow attribute filters in a toolbar for charts and custom queries only). For example, you can have a combo that filters by a particular period (First Quarter, Second Quarter etc). The process can then be called after a selection is made to check the selected value and run the corresponding query.
  14. Grid grouping improvements:
    1. Allow grouping by multiple columns
    2. Allow specifying group header template
    3. Allow end users to group data
  15. Support for Mac Big Sur
  16. Using the latest Java
  17. Tomcat 9.0 (latest)
  18. Improvements to the display of the list of active processes
  19. On/Off strings for switches and “do not display colon after label” settings added to form styles
  20. CSS class and style added to form and grid styles
  21. ENCRYPT_DOC_BASE64 function

Bugs

  1. Inserting a row into a form and then moving it up making it first lost column properties
  2. Viewing a document which name has spaces or #, didn't work
  3. Undefined documents stored in file system could not be “read”
  4. Appointments shown across multiple days in the Calendary Weekly and Daily View lost their colors set by item rules
  5. Clicking on a grouping row in a grouped query with default editing operation used to run the default operation for the first record
  6. When using forms - if focus was set on the Save/Create button and ENTER was pressed the operation was performed twice
  7. Deletion rules were incorrectly written into XML
  8. EXEC_SPF used to always return a double, so you couldn't use it to return a string. Now always returns a string. If a number is required use AS_NUMBER to convert