Recent Updates

  • Enhancements have been made to enable users to add in fields into Event Forms to Track Start Time, Finish Time, Linked Time, and the Time calculations to work out the difference between these. In addition to these enhancements, Start Time and Finish Time can now be added to a Report (even if they are not specifically tracked as Time Fields in the Event Form).

  • Previously, there were a number of workflows that had been set up attempting to track and report "Time" as a field. However, depending on the way the workflow was set up, and the type of date field it was referencing, the calculation could be incorrect (e.g., referening Entered On in a calculations was not supported), and there were still a number of limitations associated with alternate workflows.The Time Calculation and Time Difference Fields now enable users to accurately measure and store time in an Event Form. Mover, the addition of Start Time and End Time as a Report Property to include, ensure start time and end time can always be accessed.

    N.B. If there is a date override field in the Event Form, the Start Time will always default to 12:00.

  • Updated on: Mar 01, 2017

    Group Entry enhancements

    Group Entry now adds in multiple columns to fit the width of the page. Filtered searches are now also condensed into lists.

  • Previously when a form with In Form Reports or Charts was entered or opened, all of the data for each of the In Form Chart would load, irrespective of whether the Report or Chart were visible. So if a form had a large number of these types of fields, it would be slow to load, AND it also placed a lot of unnecessary load on the server.

    Now, if an In Form Report or In Form Chart is set not to appear using visibility settings, it will only load when it is displayed.

    NOTE, this does NOT work on forms where css is used to hide In Form Reports and Charts. It only works where a field is set based on visibility settings within the form.

  • Functionality has been added that enables a Dashboard to appear immediately on the Front Page page, which enables users to bypass having to click on the "Dashboards button to select the Dashboard. Any Front Page enabled Dashboards can be built directly into a Custom Page Layout so that the appear immediately when a user logs in.

  • Previously, when a smartflow trigger fired off a smartflow target entry, the target would not automatically resave if the trigger event was updated. Now, it automatically updates on any resave or edit.

  • Updated on: Dec 14, 2016

    D3 enabled for mobile

    There are two new aspects to the D3 dashboards for the Mobile App.

    1: Existing/or new custom dashboards set up on the Admin Page will display on the mobile apps IF they have been mobile enabled.

    2. The other major change is that a dashboard element that can be set so that an Event Form field can appear in the Dashboards module

    See below for details:

    IMPORTANT: For the Fusion staff who build/enable the system dashboard layouts for mobile, keep in mind is the width of the mobile screen needs to be accounted for for any dashboard. If you are enabling an existing Dashboard, ALWAYS login on mobile to ensure it displays correctly.

  • Individual display properties can now be set for any field selected to be "Chart by Default" or for any field selected to chart in an In Form Chart.

    The following can be customised for each field (some settings only appear for some specific chart types):

    • Colour (select colour or write in the # code)
    • Stroke width (1-10)
    • Shape size (1-10
    • Shape fill (Yes/No Tick)
    • Border (1-10)
    • Border width (1-10)
    • Saturation (0-100%)
    • Labels (Yes/No Tick)
    • Shadow (Yes/No Tick)

    The Defaults (that may pull through from a Chart Properties set via the Application Details or from the Chart Properties on the Event Form) will be set automatically. To override these for a field, simply select "Customse" for the field's Chart Properties. The steps below outline how to customise the properties for any field set to Chart by Default or that is included in an Inform Chart.

    NOTE: Any In Form Chart can include a mixture of fields set to be the default, or to be customised. Similarly, some Chart by Default fields or In Form charts may be set to default, while others in the Event Form are set to be customised. This is fine, just check that you are always happy with the way the charts look on the system with live data in them!

    The following charting examples simply highlight the chart styling diversity, NOT good design sense!

  • The chart properties allow colours to be set for up to 10 time series within each chart. A specific Chart Property template can be applied to the entire application (via the Edit Application Details Module) which would then make that template the default for the application.

    IF an alternate Chart Template is created, it can be applied to a specific Event Form (Via the Chart Properties in the Advanced Form Properties). If this is set, it will override the Application Template settings. See the "Chart Styling Changes for the Application" document.

    IF a user has set colours and size properties for a field within an Event Form for an In Form Report or a field that is set as Chart by Default, then these settings will override any Form Chart Styling Templates, AND/OR the Application Properties Styling Template. For more on setting up individual colours and properties on a field by field basis in an Event Form, see the document on "Set the chart properties (colour, line width and transparency) for each field within an Event Form".