Coghead has added several new features and changes to the product. The new features are mostly around authoring the forms and providing the ability to export data in csv and xml formats. Other changes to the product are centered around usability and UI refinements for the end-user. For your reference, here is a list of these features:
A. Authoring Forms: A user with Author privileges will now have access to the following Form Authoring enhancements.
Ability to reference data from collections across applications within an account – authors can now use the relevant form widgets within one application and create dynamic links to data residing in collections across other applications that they have access to in the respective account. This feature can be accessed from the combo box or grid link form widget. In the form widget property dialog box, an authoring user can select the respective collection and data field to be linked to across applications available in that account.
Ability to set conditional visibility of fields/sections in a form to the end user – authors can now define certain sections/fields of a form to be visible to the end user depending on values of other fields populated/selected by the end user. This can be specified by using the “conditional styling” feature when setting properties for the respective form widgets in the form editor.
Ability to dynamically auto-populate the data in one field with contents from another field based on end-user input/selection and optionally make it editable – this feature is available as part of the existing “calculated field” feature. In addition, the author can also specify if the calculated field can be edited or not. This feature can be specified by using the “conditional styling” feature when setting properties for the respective form widgets. Some examples of application scenarios where this feature could be useful are in:
A form where the end user has to fill in shipping and billing information. The author can define the form to have a checkbox to indicate if the shipping and billing addresses are the same. If the end user checks the box, then the shipping fields would be auto-populated with data from the previously filled billing fields. The Author can also specify if the auto-populated shipping fields should be editable by the end user after the auto-population.
A order form where the author may define a price discount value field to be auto-populated/calculated based on the price of an item – in this case, the author would also set the calculated discount field as a non-editable field by an end-user.
Support for a picture (image) widget in the form builder – this would allow end users to upload images into a form. Currently the product can support only JPEG image formats. Authors can also specify the size of the picture widget to be used in the form (using the “height” and “width” fields in the image properties dialog box) as well as the image dimensions (using the “stretch” option). There are no restrictions on the size of the image file. An author can also add an image to the form that cannot be tampered with by the end-user.
B. Data Export – Ability to export data: From within a view, users can export the data (in that view) in CSV format. Currently, this feature is available as an action that is located in the view authoring actions dropdown UI (the cog icon for authoring views). We are working on a new UI for forms and views and once that is implemented, this feature will also be available to end users as an export data action and will be located in a dropdown list of actions available to end users (not just authors).
Note: Right now, there is a known issue with the export csv functionality with IE where none of the export functions can be invoked after the first time invocation – Engineering is working on investigating and fixing the problem. This issue/behavior is not seen on Firefox.
C. Usability & UI refinements
Prompts to save any unsaved changes – Users will always be prompted to save unsaved changes any time they navigate away from the recently updated records.
Search - A “Clear” button has been added to the search UI to clear out previous search entries. The “condition” field has been moved to the bottom of the search UI.
Refined Usability for the newly added/modified records in a form – The newly added records will be displayed in a separate pseudo tab on the grid with a dynamic count of the number of newly added records. Users can optionally click on this tab to see the newly added records or remain on the main grid view. Modified records will remain in the main grid with a yellow highlight to indicate the modified status (also implying that these records may not be in the right sort order). Users can also refresh a view manually with a refresh icon that is available on the grid – clicking on the refresh icon will absorb any newly added/modified records into the appropriate views. Once the view is refreshed, the modified records will be correctly inserted into the right sort order.
Authoring actions - Authors can now set a field to a value without having to use the "map" action. In the past, this was a 2 step process. Authors had to first map the entire collection to itself and then set the individual field value.
Gallery usability enhancements – Some UI refinements and messaging have been added to provide visual confirmation of the “Copy” application task.
UI refinements – Several UI refinements have been made to the Admin Console, Process builder and the Getting Started page. Rewording of text to better describe the intended tasks and new icons for improved usability have been added.
D. Authoring Applications : A user with Author privileges will now have access to a new Version Management feature. When an application is being promoted to production for the first time, author will now be prompted (with a dialog-box) if he wants to copy the prototype data to production along with the application. Clicking on "yes" will copy the prototype data set to the newly promoted production application. Clicking on "no" will not copy any data to the newly promoted production application.
Coghead has added several new features and changes to the product. The new features are mostly around authoring the forms and providing the ability to export data in csv and xml formats. Other changes to the product are centered around usability and UI refinements for the end-user. For your reference, here is a list of these features:
A. Authoring Forms: A user with Author privileges will now have access to the following Form Authoring enhancements.
B. Data Export – Ability to export data: From within a view, users can export the data (in that view) in CSV format. Currently, this feature is available as an action that is located in the view authoring actions dropdown UI (the cog icon for authoring views). We are working on a new UI for forms and views and once that is implemented, this feature will also be available to end users as an export data action and will be located in a dropdown list of actions available to end users (not just authors).
Note: Right now, there is a known issue with the export csv functionality with IE where none of the export functions can be invoked after the first time invocation – Engineering is working on investigating and fixing the problem. This issue/behavior is not seen on Firefox.
C. Usability & UI refinements
D. Authoring Applications : A user with Author privileges will now have access to a new Version Management feature. When an application is being promoted to production for the first time, author will now be prompted (with a dialog-box) if he wants to copy the prototype data to production along with the application. Clicking on "yes" will copy the prototype data set to the newly promoted production application. Clicking on "no" will not copy any data to the newly promoted production application.