When building a custom form, if there is some sort of error in the build, the error message describes the conflict, but don't identify the fields causing the error. Please, please, please map the error to the field so we can correct the error.

At the system admin level, I don't always know what a group needs for templates. In fact, I don't always have influence on those types of things. It would benefit those groups to have access to Blueprints for their own enablement.

The documented default for Proof is to send a daily summary of comments. For users managing dozens of proofs at a time, this is bogging down their email. I think there are a variety of ways to customize this experience: allow the user to set defaults for when comments come in, decisions are made, or...

I would like to be able to report on checkbox fields to count and chart selections with the same ease as any of the other field types. There are discussions going back years with this issue and the best solutions have been: Use advanced text mode for each checkbox option (poor report-building experi...

I think Sebastian's idea is basically what I'm looking for: The ability to report on checkboxes by the individual selections so we can filter, group, and chart. Currently it requires some ninja coding to count the individual checkbox selections, which can be untenable when you have more than just a ...

I came to the Innovation Lab to basically post about this. Ultimately, Calendars are visual reports and admins should be able to view all user-generated calendars just like we can with Reports and Dashboards. The hoops we have to jump through to fix a calendar when an admin is deactivated is painful...

I'd like to be able to hover over display logic codes to see what field the icon is matched to. The color matching is useless with longer forms.

Currently you have to open a custom form to find the option to deactivate. If you have any broken logic, you cannot save the form until you resolve broken links. For lengthy forms, this is insanely difficult. There should be a button to mark a custom form as inactive without having to open the custo...

Currently the license Request is locked into No Access for Portfolio and Programs. This limits their ability to use the typeahead field in a request form for those objects.

The typeahead field is a great time saver...until a user can't do anything with it. We have a request form that asks the requestor (lowercase 'r') to select the Portfolio associated with their request. However, anyone of the Requestor (capital 'R') is inherently and forever granted No Access to Port...