...
New Features | ||||
Affects | Description | Details | Reference | |
Konect App | 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 Projects (KPK packages) are now available | Konect Manager provides access to example 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 | |
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 means that in a linked child dataset, a list parented by a ‘Copy 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 | 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:
| KO-182 | |
Konect Manager | 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 Konect App | Yes/No fields in selection 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 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 are now presented as green ticks (yes) and red crosses (no). For example, in a form called 'House Renovation' there are two selection fields called 'Room' and 'Renovated' and 'Renovated' 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.
| KO-220 | |
Konect Manager | Visibility rule depending on List field does not honour rules no longer the ‘not equal to’ operator | Version 3.70 of Konect did not honour the abandoned 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 conditional field visibility based on list values. The ‘not equal to’ operator for visibility rules based on List fields.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 App | Deleting photo a photo in offline an 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'. problem is now rectified. Photos are saved correctly when operating in offline mode. | KO-223 | |
Konect Manager | Missing .CSV file extension is used as a folder during export of data | When a dataset was exported to a CSV file and the extension ‘.CSV’ was missing, a folder rather than a file was created | Export of CSV files without the file extension is not allowed. | KO-226 |
Konect ManagerSelect 'Primary Form' tab when new form created | 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 | |
Konect App | Unable to move map feature in query in offline projectIf 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(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 | 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 | 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 | |
Konect Manager | Map labels based on List fields use code value, not display value | KO-157 | ||
Konect Manager | Datepicker control shows a default time of 10 am | KO-177 | ||
Konect Manager | Zoom setting does not apply until 'Save location and visibility' button pressed | KO-178 | ||
Konect Manager Konect App | Field visibility rules based on Time, Date and Datetime fields do not work | KO-191 | ||
| Konect App | 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-194 | |
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 the cursor at the front of the number and then type the minus sign. | KO-225 | |
Konect Manager | Mouse does not detach from scrollbar when editing a record | This 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 | |
...