Versions Compared

Version Old Version 30 New Version Current
Changes made by

John Ivett (Unlicensed)

John Ivett (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following table lists the new features, bug fixes and known faults for Version 3.80 of Konect.

New Features

Affects

Description

Details

Reference

Konect App

Text

annotation for photographs on

annotation on photographs taken on iOS devices

Konect provides text annotation on photographs taken on iOS devices

is now supported

Previously iOS devices only supported arrow and shape annotation on photographs. Text annotations can now be added directly to photographs and are saved permanently as part of the photo.

KO-179

Konect Manager

Example

solutions – KPK demo datasets

Projects (KPK packages) are now available

Konect Manager provides access to example

solutions such as Tree Management. The example solutions can be downloaded from a web link to Konect Manager

project packages that contain complete workflows including dataset definitions, forms, lists and project definitions. Population of the package library has commenced and expansion of the library will continue as new packages are produced over the coming months. The packages can be imported into Konect Manager from a web link. The packages can be used as a template for workflows or they can be modified and enhanced to better reflect your own processes.

KO-202

 Bug Fixes

Affects

Issue

New Behaviour

Reference

App

DEVICE: Child list rules generated dynamically

When a child list was associated with a parent list, a set of rules relating each parent item to its child items was created. However, when either the parent or child list was updated, the rules were not.

Now the rules are created dynamically as needed and lists

Konect App

Edits to Pick Lists in parent forms were not being transferred to linked child forms where "Copy Value" fields are being used

Lists are kept up to date in linked datasets. This

is particularly relevant to the situation where a child list is

means that in a linked child dataset, a list parented by a ‘Copy

value’ field where the value is copied from a List field
  •   Let there be an Integer field called INT that has a default value of 0.
  •   Let there be an Integer field called VIS_INT that has a visibility rule of 'INT not equal 0', that is, it will only be visible when the field INT is not equal to zero.
    •  

    Value’ field that has derived (copied) its value from the linked parent dataset, will continue to work correctly if the lists used in the parent dataset are edited.

    KO-180

    Konect App

    DEVICE: Visibility rule fails on default value for Integer field

    The following error has been fixed:

    Visibility rules based on default values for Integer fields fail to work correctly

    When a new record is created, fields with visibility rules based on default integer values display correctly. For example: 

    • "Number of Defects" is an integer field type with a default value of 1
    • "Total Area" is an integer field
    • "Total Area" has a visibility rule = "Number of Defects" is not equal to 1
    • When a new record is created and the default value for  "Number of Defects" is accepted (1), then "Total Area" is not displayed in the form
    • When a new record is created
    on the client device, VIS_INT should be hidden but it is visible. 
    • and the value for  "Number of Defects" is changed to 3, then "Total Area" is displayed in the form

    KO-182

    Manager

    KM: Solution for KS-34, HTTP network error 407 The Http client has been given a longer timeout period in order to thwart 407 errors

    Konect App

    Deleting a photo in an offline project causes konect to freeze

    This problem is now rectified. Photos are saved correctly when operating in offline mode.

    KO-

    205Manager/

    223

    Manager

    KM: Stacked map objects not rendering in the correct order

    The map features of child records were not displaying in the correct z-order. Records created at later times must sit on top of records created before them and this was not happening.

    KO-206

    Manager

    KM: Forms can be saved with invalid field constraints

    A form could be saved with invalid field constraints. For example, if a Text field has a maximum length limit of 7 and the default value is ‘AUSTRALIA’, then the form could be saved. This release disables the 'Save' button until field constraints are valid and consistent.

    KO-209

    Konect App

    Unable to move (edit) map features in an offline project where the map features are stored through a query on the target dataset

    Spatial editing of map features in an offline project using a query on a dataset is now supported.

    KO-234

    Konect Manager Konect App

    Yes/No fields in selection

    lists rendered with ticks and crossesWhen a map is zoomed out, many features may be sitting on top of each other. If the user clicks on this mass of features

    lists were  not displayed with meaningful values

    If multiple features are found at the click point on the map, a selection list is presented which

    contains all the features under the click point so that the user may

    shows the 'Selection Field' values nominated in the primary form settings. The user can select the required record from all the features listed. If the one of the selection fields is a Yes/No field, then the values for that field

    will

    are now presented as green ticks

    and

    (yes) and red crosses (no).

    As an

    For example,

    let there be a form called

     in a form called 'House Renovation'

    that has

    there are two selection fields called 'Room'  and 'Renovated'

    and let

    and 'Renovated'

     be

    App

    DEVICE: Deleting photo in offline project causes konect to freeze

    This release fixes the following problem:

    1. Create an offline project that has a form that has a photo field.

    2. Create a record with no photos and save it.

    3. Open the record again.

    4. Take a photo for the photo field but don't save the record.

    5. Delete the photo from the photo field.

    6. Press the 'Save changes' button'.

    konect permanently displays the message 'Saving your changes now'.

    KO-223

    Manager

    KM: Missing .CSV file extension is used as a folder during export of data

     is a Yes/No field. If there are six records under the click point then the following image shows the values of 'Renovated' with ticks and crosses.

     

    Image Modified


    KO-220

    Konect Manager

    KM: Visibility rule depending on List field does not honour ‘not equal to’ operator

    Version 3.70 of Konect did not honour the ‘not equal to’ operator for field visibility based on values of List fields. For example, assume there is a List field called ‘Animal Type’ that has three values ‘Dog’, ‘Mouse’ and ‘Rat’.

    Let there be a Text field called ‘Action Required’ that has a visibility rule: VISIBLE if ‘Animal Type’ not equal to ‘Dog’.

    The visibility rule was not honoured in Release 3.70 when operators for visibility rule were enhanced.

    Release 3.80 honours the ‘not equal to’ operator for visibility rules based on List fields.

    KO-221

    FAIL Error messages on Save or navigation in KM

    407 Proxy Authentication Required

    500 Internal Server Error

    502 Bad Gateway

    		 Various error messages were displaying intermittently when operating on various tabs and performing various save and navigation tasks in Konect Manager. These errors are now resolved.

    KO-205

    Konect Manager

    Stacked map objects were not drawing (rendering) correctly on the map at different map zoom levels

    Map objects collected sequentially now display in stacking order representing the sequence in which they were drawn. For example a linked dataset with multiple records representing different inspection stages (proposed, authorised, re-inspected) and with map styles based on the stage (red, blue, green) now show the correct style for each stage as the records are collected - red when proposed, blue when authorised, green when re-inspected.

    KO-206

    Konect Manager

    Forms can be saved with invalid field constraints

    The 'Save' button is now disabled until field constraints are valid and consistent. For example, if a Text field has a maximum length limit of 7 and the default value is ‘AUSTRALIA’, then the form can't be saved.

    KO-209

    Konect Manager

    Visibility rules no longer the ‘not equal to’ operator

    Version 3.70 of Konect abandoned the ‘not equal to’ operator for conditional field visibility based on list values.

    The ‘not equal to’ operator for visibility rules has been reintroduced. This now means that both the Equals and Not Equals case is supported and when combined with the new multiple value selection, visibility rules now have much more power eg show Defect Type if Asset Category = Standard Bin or Cradle Bin or Metal Enclosure.

    KO-221

    Konect Manager

    When a dataset was exported to a CSV file and the extension ‘.CSV’ was missing from the File Name, a folder rather than a file was created

    During the export of CSV files, a file with the format "Filename.csv" will be exported even if the ".csv" extension is missing from the File Name shown in the Save dialog eg "Filename" or "Filename.csv" will save as a file named "Filename.csv" in the correct folder.

    KO-226

    Manager

    KM: Select 'Primary Form' tab when new form created

    Konect Manager

    When creating a new dataset the user interface remains focused on the last used Dataset tab

    When a new form is created the 'Primary Form' tab is now always selected.

    KO-227

    App

    DEVICE: Unable to move map feature in query in offline project

    If an offline project had a query and the query’s dataset allowed for features to be edited, a map feature could not be moved on the map.

    KO-234

    Manager

    KM:

    Konect Manager

    Exported geojson files have extension of '.geojson.json'

    When a dataset

    was

    is exported to a GeoJSON file, the

    filename had an extension of ‘.geojson.json' instead of

    file extension is now '.geojson'.

    KO-235

    Konect Manager

    KM:

    Cannot revert to 'Match Pattern' = 'None' for Text fields

    If the

    The 'Match Pattern' for a Text field

    was

    that has been changed from ‘None’  to something else,

    it could not

    can now be changed back to ‘None’.

    KO-236

    Known Faults

    Affects

    Issue

    New Behaviour

    Reference

    KO-157KM:

    Required Behaviour

    Reference

    Konect App

    'Limits' settings applied to numeric fields do not work correctly.

    • Records can be saved when out-of-limit values have been entered
    • No warning is issued to indicate that the entered values are out-of-limits
    • Out-of-limit values are replaced by the closest limit value

    All issues to be rectified.

    		KO-194

    Konect Manager Konect App

    		Field Visibility Rules based on Time, Date and Datetime fields do not work  Users are advised not to base visibility rules on Date, Time or Datetime fields as such rules may not work correctly. Future releases of Konect will support the correct visibility rule behaviour.KO-191 

    Konect Manager

    		Map labels based on List fields use
    code value
    the list Value, not
    display value 
    the list Alias The list Alias should be presented as the labelKO-157
    KO-177KM:

    Konect Manager

    		Datepicker control shows a default time of 10 am
     
     The default time should display as 0:00KO-177
    KO-178KM: Zoom setting does not apply until

    Konect Manager

    Catalogue > Datasets > Data/Queries

    Changing the Zoom Visibility values do not apply until the settings are saved using the  'Save location and visibility'

    button pressed  KO-178KO-191 KM/DEVICE: Field visibility rules based on Time, Date and Datetime fields do not work  KO-191 KO-194DEVICE: Able to save record with out-of-limit numerical field  

     Assume that an upper and lower limit has been set for the value of a numerical field in a form. Even though limits have been set, a number can still entered on the client device that is outside the limits. The problem is that when the record is saved there is no error message that the field's value is outside the set limits and the entered value is replaced by its closest limit.

    For example, if the limits are 0 to 100 and the user enters 1000 on the client device, the value stored in the field when the record is saved will be 100, the closest limit to 1000.

    KO-194KO-225KM:

    button 

    		Changing the Minimum or Maximum zoom values should apply immediately so that the settings can be tested without needing to save.KO-178

    Konect Manager

    		Cannot directly enter negative numbers for default values
    This problem applies to numerical fields. When setting the default value or upper or lower limit in the Konect Manager's form editor, a negative number cannot be directly entered into the textbox. To circumvent this fault, enter the positive number, place
    in numeric fieldsA temporary work around to this issue is to firstly enter a positive number and then place the cursor at the front of the number and
    then type KM:
    then enter the minus sign.KO-225
    KO-231

    Konect Manager

    		Mouse does not detach from
    scrollbar when editing a recordThis fault occurs when editing a record in Konect Manager where there are many fields and the scrollbar must be used to get to the fields at the bottom of the form. The mouse does not detach from the scrollbar properly when moved off the scrollbar and the form continues to move up or down.KO-231
    the scrollbar after navigating through a form and attempting to edit a new field in the formThe mouse should detach from the scrollbar after scrolling and allow selection of the required data entry field in the form.KO-231

    Konect Manager

    		When panning (left click hold) on map screens in Konect Manager the mouse remains in pan mode if the panning action is taken beyond the edge of the window.If the left mouse button is released, panning mode should be disabled irrespective of when the mouse button is released ie inside or outside the map window.KO-249