13 results found
-
Annotation replies on WPV
There's an inconsistent approach in the platform to reply to annotations. For xml tables (that are accessed through a button on UI), a user needs to reply to annotation then "Enter" the field through the annotation reply.
For wpvs (also accessed through a button on UI), the approach is different. A user must click directly on the field instead of annotation.
This creates considerable confusion for our end users and is quite difficult to train users on. They don't know the difference between WPV and XML and they shouldn't have to.
The platform needs a consistent approach for annotation replies…
3 votesWeb page views are currently designed for read-only purposes, such as displaying information and generating PDF documents. They are currently not intended for editing content, which is why an option to open them within the Annotation UI was not included like the option was withing Advanced Data tables.
While it may be possible to customize a web page view to support some level of editing, this is not available out of the box and is not a capability all clients have. Because of this, it’s unclear whether introducing a general option for all clients to open what is typically a read-only view would be well received.
At this time, there are no planned changes to this behavior. However, if web page editing is introduced in the future, or if we release new feature for budget management, we would be open to revisiting this functionality.
-
Change how field revision annotations work for XML Advanced Data Tables
The user experience for requesting and submitting annotations on Advanced Data Table fields is very challenging & unintuitive.
This comes up with every client who tries to use this feature.
- The grant manager will request an annotation on the field displaying the table. This doesn't allow editing of the displayed data.
- We will then direct the grant manager to request an annotation on the XML button itself. This does allow the data to be edited, but if the applicant clicks the button on the form itself, they will not be able to edit the data.
What needs to happen with…
1 voteNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We are not planning to enhanced the ADT; however, we are looking at a new set of budget capabilities to support the annotation.
-
Rich Text Fields: Built-in "Cleanse Formatting" button to sanitize pasted Word/third-party content
When applicants paste content from Microsoft Word or scientific journals into Rich Text fields, the editor silently injects hundreds of problematic HTML artifacts — deeply nested <span> tags with inline styles (font-family, font-size, color, border, background), Microsoft Office markup (mso-* properties, <o:p> namespace tags), Word bookmark anchors (<a name="_Hlk...">), and redundant wrapper elements.
From the applicant's perspective, the content looks fine in the editor. The problems surface downstream: PDF conversions break or produce corrupted output, field rendering becomes inconsistent, and in some cases, the Rich Text field functions themselves stop working properly. The applicant has no way to know their…
2 votesNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
we are looking at other ways to support content/format and enhanced ways to work with Word, but not natively within SmS, we have no immediate plans to support this use case
-
Can we get a "Resend" button in the Emails tab of L1 Grant records?
Occasionally we need to resend grant correspondence to a contact, and it would be a great time and effort saver to be able to do so directly from the listview in the "Emails" tab of our L1 grant records, rather than having to note the contact name/email there, and then go to the Message queue, search in the "Sent" tab, select the precise emails, and resend there.
1 voteNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
The record you see on L1 is a log, not the actual L2 email so it cannot be resent.
-
Maintain the use of collapsible sections in the New Design.
Collapsible sections using title bar are no longer a feature in the New Design. Our team finds collapsible content useful and would like to keep it as part of New Design.
1 voteNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
The collapsible title bars were removed to improve clarity, reduce user errors, and create a more predictable form‑filling experience. While they allowed some users to temporarily hide content, they often caused accidental collapsing and led to important information being overlooked. Keeping all sections visible ensures a simpler, more consistent interface where users can confidently see all required data.
-
Add Status ID as filter option in advanced search
Status Id as an option to search in advanced search would bypass issues with language translations and status name vs caption. See ticket 268653
2 votesNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Filter can be made on Status Name instead of Caption. We don't have plans to expose the status ID as a filter option.
-
Ability to delete bulk list views
Currently, if we want to delete a list view, we must open the listview first and then delete it. This process is time-consuming when handling multiple listview. It would be much more efficient if list views list included checkboxes that allow users to select one or more records directly and delete them in bulk.
2 votesNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
As an administrative action is that not frequent, we prefer to error on the side of requiring 2 clicks to delete as there is not reverting back.
-
Breadcrumb Navigation for Modal Widows
When I click on a record from a section under my portal the record opens up in a modal window. Unfortunately, the breadcrumb navigation does not display when the record in a modal window. I need to open the record in a new tab in order for the breadcrumb navigation to display.
I would like the breadcrumb navigation display of modal window as well.
1 voteNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We intentionally removed this type of navigation as the model window is designed for targeted actions, then closure.
-
Default Quick Navigation Menu to Closed
Have the quick navigation menu default to closed/minimized or remember last position.
I am often finding that I need to constantly close it for ever record that I go into because it is cover or narrowing fields unecessarily.
1 voteNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
The quick menu has been removed, so this is no longer applicable.
-
Create a way for commenters in custom fields using the 'notes entry' feature to be able to edit their comments.
Create a way for commenters in custom fields using the 'notes entry' feature to be able to edit their comments.
1 voteNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
The custom field option is designed to log activity/notes. You could use the notes and the special linked record list to achieve this.
-
Make Submit button redirects dynamic based on user role
We have two different roles doing reviews - external reviewers with the "Reviewer" role, and staff with the "System Administrator" role. Right now the review "Submit" button redirects to the Reviewer Portal accessible to external reviewers, and throws a permission error to the internal reviewer. It would be nice to be able to redirect to the internal reviewer's Staff Home portal and the Pending Reviews listview there from the same submit button. Let's not proliferate too many buttons!
1 voteNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Two different buttons are required in this scenario. We do not have plans at this time to support dynamic redirection.
-
'Save and Close' button for modals
For modals, users have to click save and then close out of the window. A "Save and Close" button would be nice so that users do not have to worry about closing out of the window after saving. This would also prevent instances of users having the modal open in multiple different windows.
1 vote -
1 vote
- Don't see your idea?