Feature Requests

Giving Pitchly admins or approved users/roles the ability to create charts, reports, & dashboards based on their underlying Pitchly data. Graph types may include: Line, Bar, Pie. Create user-facing, shareable reports that are dynamically drawn off live data. Printing and export (PDF, PNG, PPT) capabilities.

* Incremental ID - Non-editable field that would display to the user, and be usable in filters, an auto-generated identification for the record. Perhaps make it configurable to the admin at the time of table setup (let them choose the format and starting ID for the field, prior to records being created) * Timestamp - Non-editable field that would display to the user, and be useable in filters, when the record was created. Perhaps distinguish between "Create" and "Update" timestamp, and offer them both if desired. * Priority/Severity - Perhaps give admin configurability for scale (e.g. 1-5 or 0-10) and presentation to end-users (e.g. stars, dots, sliding scale). Could be done w/ an ENUM field on the back-end * Boolean upgrade - Give admin ability to configure a new boolean field to present to the user as: Yes/No, Done/Incomplete, or a simple Checkbox * Data validation for Single Line Text fields - To give admins the ability to set up specific data types, such as Email, Phone number, Postal code, & other alphanumeric checks * File Multiple - Ability to store multiple files in a single field. Would we let admins enforce a file type (e.g. only PDFs)? Would we enforce size limits or a limit to the number of files? Advanced Types * Formulas * Aggregation

A global library of table templates for specific industry+business purposes (e.g. Legal Matters), or for common scenarios (e.g. a table for all US States for use as a Reference field). Ability for customers to submit their own for inclusion in the gallery.

The most popular Kanban board app is Trello. A standalone Pitchly app that would leverage our underlying database platform. Set up Boards, Lists, & Cards that would be modeled & stored in Pitchly. To model cross-functional workflows, a Workspace owner could create a board and assign (Assuming pending V4 functionality, esp. Workspaces & Teams)

Multi-page forms that can load subsequent pages based on conditional logic checks on submitted responses. (e.g. If the user checks "Yes" on a dropdown, load Page 2 of Form, load Page 3 of Form)

Send a rejected form back to the sender with the details saved so they don't have to start over. Approver/admin could note why the submission is being rejected, so the submitter knows what to fix for resubmission.

For attorney at a lunch when asked if the firm has experience with a specific matter, being able to search off platform.

When someone fills out forms, check if the data is already in the database

This is to help them always access forms that they use regularly

The ability to save a "snapshot" of database information, by not only a filter, but also by saving the hidden fields and sort order.