Feature Requests

While it is possible to pull a diff of the record from the current active edit session on an interval or with the aid of a calculated field for storage, it would be more convenient to have a data event listener built to trigger on the deletion of a repeatable. Bonus points if it can return the deleted record's object in the event, so that information about what was deleted can be worked into other functionalities.

We would like the ability to assign the same Task to multiple users, for any of them to complete by the designated time. All users would receive a notice of a new Task, but once completed by one Member it would clear out on all other user's accounts. This would allow greater flexibility on multi-staff teams that work on shift rotations.

The Public Issue Submission template is too generic and doesn't present the public with a very professional outward looking page. There needs to be a way to customize what exactly you need in the submission as well as branding. Is there any APIs that work with Issues or Task?

Add the ability to control the visibility of the add, edit and delete buttons using DataEvents. This would give us control who can add, edit and delete items based on business logic in DataEvents. Roles (add, edit and delete) are limited to the record level, not the fields within. Suggestions: SETBUTTONVISIBLE([add, edit, delete], bool) -> Hide/Show Main level Add, Edit and Delete Button SETBUTTONVISIBLE([add, edit, delete], repeater, bool) -> Hide/Show Repeater level Add, Edit and Delete Button

KML/KMZ layers should behave the same as mbtiles layers. You should be able to import a kml/kmz direcly from your device. On my Android phone currently, my KML/KMZ layers turn off every time I close the app. Additionally, they don't permanently download to the device so I need an internet connection to reload them, which creates issues when in the field.

Suggestion for a future release. Incorporate the capability to organize apps into folders or contianers so that like apps can be grouped together. For example, i might create a folder or container called vehicle inspections. inside that folder i would have my pickup truck inspection app, line truck inspection app, etc.. Would be an easy way to keep like or similar apps organized.

When a user edits a pre-existing record and saves a draft, they sometimes need to delete the draft version but keep what was pre-existing. On the mobile, it deletes the draft AND the record. To get the record back, they have to either clear the cache on the device and sync again or update the record on the web to get the change registered.

It would be beneficial to enable workflows that use triggers in App (A) to update existing records in App (B).

It would be very helpful to have push notifications to certain users whenever a Task/Issue is created and/or completed.

For recurring tasks we would like a quarterly, semi annual and annual added. That would help our technicians stay on top of inspections.