Multi-choice Web App closer to Mobile Version
The selection of multi-choice values is difficult on the web app, the user needs to ctrl click to select multiple without losing previous selected values. Could there be a check-box pop up similar to the web app?
Mobile App Filter Suggestion
I would love to be able to filter by record assignment in the mobile app.
Batch or Mass Editing/Delete of Records from editor
Have the ability to mass edit or delete records from within the editor.
Owners being able to see who has unsynced records
having a way for the app Owners to see if there are any unsynced records attached to a tablet/login
Apply requirement rules at the section level
Currently we have the ability to apply visibility rules to a whole section. I'd like to be able to have the ability to set requirement rules at the section level and these push to the items contained in the section.
Add SETPROJECTFILTER function to data events
I would like the ability to set a filter on the projects field like you can do with status.
Status field for repeatable/child records
Hope we could add a function that's similar to "Status Field" for repeatables
iOS split-view support
Please please add this support. I imagine it would be very useful for many of your customers. We want to be able to have fulcrumapp running on one side of our iPads in landscape mode while we have another app running on the other side. We made a big investment in this without realizing fulcrum does not support split-screen. Please help!
Ability to stop/cancel download
When downloads get stuck running, I wish there is a way for me to stop the download, cancel it, and remove it from the list so I can start a new download.
Data event for 'save as draft'
I need to be able to write validate-record or save-record (or -repeatable) code that behaves differently if a record is invalid or being saved as a draft on a mobile device. In my case, I want to be able to unset a 'this record is finished and can be locked' field so that a draft record can't be locked by accident. Because we don't always care about this distinction, I suggest: (a) a function you can call in a validate event to test whether any built-in rules have invalidated the record; or (b) an extra property on the event object for save events that can tell you whether or not the record is being saved as a draft; or (c) a new invalidate-record or -repeatable event that is triggered just after validation rules (by any method) have decided to prevent saving. Under 'C' attempting to save would always trigger two events: (1) validate; (2) save OR invalidate. This would have an impact on apps that use the save event now and need it to work even when saving as draft.