54 results found
-
Disable annotations from fields
Add field level configuration to allow disabling of annotations so read-only and display fields aren't annotated inadvertently
7 votes -
Records per page
Options for allow for more than 100 but not all on the items per page picker. Often, even when filtered, there are hundreds of results and the option to pick more that 100 but not all is necessary.
5 votes -
Multi-Level Dropdown Support in Global Navigation
Problem:
Current flat menu structure lacks information hierarchy. As feature set expands, navigation becomes cluttered and difficult to scan.Suggestion:
Support Level 2 nested dropdowns in global navigation for a cleaner information architecture, to reduce cognitive load, and to improve accessibility for keyboard navigation.Example: Reports
- Level 1: Track Reports
- Level 2: Processing (Reports Pending Approval, Overdue Reports)2 votes -
Allowing address field's caption customized when 'Enable Multiple Address' is enabled
Currently: When 'Enable Multiple Address' is enabled (on org or user profile), the Address field's caption remains locked to "Primary Address"; updating the standard field caption for Address or Address Type doesn't change it.
Use Case: Client might set a different default address type, such as "Mailing Address" (which they can configure in Address Types), and they want the caption to display as Mailing Address.
Request: To allow the address field caption to be customized when using the Multiple Address feature.
4 votes -
Add reports to SmartCards
If you have some reports you are using all the time you should be able to star them to your SmartCards.
4 votesMonitoring Interest ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Good suggestion, we have linked this to the report builder workshop sessions occurring over these next few months in order to evaluate the priority against the larger report improvement opportunities.
-
Status Colours
In SmartSimple, list views apply defined status colours to a field showing that dataset's own status, but when a list references a status field from a parent or related dataset (as seen with "Application Status" pulled onto the Activities list), the colour formatting doesn't carry over, the field just renders as plain text regardless of its assigned colour. This creates an inconsistency where the native "Status" column is colour coded but a referenced status from a related record isn't, even though both represent the same type of field.
The ask is for referenced status fields to inherit the same colour…
1 vote -
Enable other users to delete from the Message Queue without making them Global Administrators
SmartSimple should allow to enable other user roles to delete from the Message Queue without making them Global Administrators. This way other users will be able to delete emails that they accidentally triggered so that they won't be mistakenly sent out.
8 votes -
French punctuation spacing
In French, there should be a space between a preceding word and a colon. For example, "Last name:" in English would be translated as "Nom de famille :"
However, when I add a space after "famille" in the translation field, the system does not save it and places the colon right beside the word famille, e.g., "Nom de famille:".
How do I get the correct punctuation in French with a blank space before a colon?
Support suggested I raise this issue in the Idea Lab.2 votes -
Expand popup for annotation replies
The annotation reply is quite small if you had a multi paragraph write-up that needs to be edited/annotated.
We would greatly value for an ability to expand annotation reply size (field value specifically). Yes, you can change the field length from bottom right corner, but that's quite restrictive for a multi paragraph reply
4 votes -
Grant ID numbers sticking at the top of activity forms
In the old version, our grant ID numbers would stay at the top of the screen as we scrolled down activity forms. Now they do not. I'd like this one feature to go back to the way it was. In the new look grant ID numbers should stay at the top of the screen as we scroll down the page.
8 votesMonitoring Interest ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
The new design is intended to maximize the screen space when scrolling. We see the value of freezing the top. We will monitor interest to see if others have the same concern.
-
Batch Update to Remove Assigned Contacts
Please allow Batch Update to handle removal of Assigned Contacts based on role. The way it functions now, a name is required in order for Assigned Contacts to be removed. Doing a bulk removal via batch update based on role alone does not seem to work.
18 votes -
Owner fields in list views
When you create a L1 list view, you can include fields from the L1 owner.
I would like to do the same for L2 and L3 list views (i.e. include L2 owner fields in L2 list views and include L3 owner fields in L3 list views).2 votes -
Implement a Visual Risk Indicator for Records (e.g., Grants and Engagements)
Introduce a visual indicator, similar to a stoplight system, to represent the risk level associated with records such as grants or other engagements. This would allow users to quickly assess the likelihood of success by viewing the associated risk level at a glance:
- Green – Low Risk
- Yellow – Medium Risk
- Red – High Risk
- Grey – No Value/Not Assessed
Key Features:
Display Locations: The indicator should be visible on the individual record, within list views, and be accessible for reporting purposes.
Data Representation: In addition to the color-coded indicator, the corresponding textual value (High, Medium, Low, or None) must…
18 votes -
Ability to change information in the invitation window on an application once an invited person has accepted
Once a person has been invited to an application and has accepted the invitation, it would be helpful if system administrators had the ability to edit information in the invitation window—such as correcting the spelling of a name or email address. It's common for the person sending the invitation to make small mistakes, and they often reach out to us for corrections after the invitee has accepted. Currently, the only way to fix these errors is to delete the invitation and re-invite the person, which is inefficient.
13 votes -
Ability to Hide/Sort/Freeze columns in the Assignment Grid (Reviewer Assignment Grid)
When using the Assignment Grid—specifically the Reviewer Assignment Grid—it would be helpful to have features similar to Excel, such as the ability to hide columns or freeze panes. This would make it easier to scroll horizontally on smaller screens without losing track of which application you're viewing. It would also be useful to have the option to sort by specific columns, such as Application ID#.
15 votes -
Make it possible to restore the little "building" icon to the portal header to change the active organization association for selected roles
We have many external users who are associated with more than one organization, and we have spent three years training them (including designing training materials, slide decks, and videos) to use the 'building' icon in the portal header bar to manage their active organization association.
The new version is not 'intuitive' or 'easy' for our users to catch on to how to chance associations. Please make it possible for us to restore the building icon and its function.
12 votes -
Toggle Left-Hand Navigtion list between full width and icons
It would be helpful if the left navigation menu on records can be toggled between the full width and a compact view on a record-by-record basis. This would help on smaller screens or when adjusting the size of the window. It would allow the fields on a record have more of the useable space.
5 votes -
Batch allocation
It would be useful to have a drag and drop type interface for allocating tasks or people where high volumes are involved. Examples include sharing hundreds to applications between a number of committee meetings or hundreds of review tasks between a number of reviewers
2 votesMonitoring Interest ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We see the challenge you have highlighted and the opportunity to improve. We suspect a solution would involve revisiting the design/approach to using assignment grid. Let' see the interest to drive future consideration,
-
Make the duplication check functionality separate form the record merge functionality
Right now, any users that have access to the duplicate organization check also have the ability to merge organization records. It's too risky to give all of our end users the ability to merge records, but we do want the duplication check functionality. Right now we required them to manually search for an organization before making a new record, but they often forget to do that. If we could split the duplication check from the merge record functionality and assign the access separately, it could make things much easier for us.
8 votes -
Floating widget integration for contextual support and ticket submission
A system-wide floating support widget in SmartSimple to let users access help, knowledge bases and ticket forms (e.g. Zendesk, FreshDesk, Zoho) from anywhere in the platform.
Support requests would automatically include contextual data such as the grant, application or workflow step the user is viewing, dramatically improving ticket quality and resolution time.
This would create a smoother user experience, reduce email-based support burden and provide SmartSimple with a modern, flexible integration point that many customers can benefit from—especially now that SmartSimple is adopting Zendesk.4 votes
- Don't see your idea?