We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
The little question mark bubble in the bottom right hand corner blocks the revisions in the markup area of the content section and you can't get rid of it. Can it be changed that you can x that out so it's not it the way of reading the changes?
Mark Fields Mandatory at Field Settings (instead of on templates, workflows)
Some of our fields are designed to capture business-critical data and must be completed every time they are used. Setting the mandatory fields up at the template and/or workflow level is cumbersome. We'd like to be able to set a field as mandatory...
Sometimes, when I make edits to fields or want to remove them, I would need to adjust logic on templates, routing rules, etc. It would be great if we could have a column in the fields area that would note where the field is in use across templates...