65 results found
-
Type Specific Captions for a Custom Field
The platform was enhanced in recent years to support different display order numbers on a single custom field by Application Type. This allowed us to finally be able position a single field in different positions on different forms. It would be great if we could also support different captions for that one field by Application Type. The only way to do this today is to create multiple fields for the same purpose and then use the value storage setting to store each discrete field to a master field for reporting purposes.
21 votes -
Strip HTML from Rich Text Fields on List View or Report Export
When exporting a reporting that includes rich text fields, the export includes unrendered HTML. This HTML then needs to be stripped out to make the content of the report readable.
Suggest to add an option on the report and list view export to strip html from the export. Include a tooltip to advise that this will impact formatting.
15 votes -
SmartFields - change default to Exclude (or allow us to choose our preferred default for our system)
Can there be a way to choose your system's preferred default for SmartField inclusion? Currently it defaults to Include. Ideally we'd much rather it default to Exclude, or at least give us the option to choose our default.
The issue is that with numerous system admins making changes or adding fields over time, we inevitably are forgetting to toggle this to Exclude and errant fields then show up in our exported pdf files - that we often are completely unaware of. This could cause a file to being shared with users who should not have access to some of the…
10 votes -
AI-Powered Configuration Assistant
Enhance the SmartSimple platform with an AI-driven assistant that supports developers during configuration by offering real-time suggestions such as field types, AI tools, syntax guidance, and automated script generation. This assistant would analyze existing configurations and scripts to recommend improvements, flag potential issues, and answer natual language questions (e.g., “How do I call an OpenAI function in web page view?”).
Together, these features would create a smarter, more supportive configuration environment that reduces the time and effort for developers to research on resolutions, improves code accuracy, and accelerates development.
10 votes -
Expand options for Dynamic Field Visibility Builder
The Dynamic Field Visibility Builder could be expanded to include the following:
• a larger window
• an expandable window that scrolls
• auto-zoom that allows the text on the screen to be readable at all times
• Save As functionality
• Restore option if a condition is accidentally deleted9 votes -
Record Lock Override Notification
When a user is being kicked out of a record, it would be great if they were notified that they were being kicked out.
11 votes -
Create new field type for URLs, which will display as active links
Our applicants and grantees have asked for this. They can type in a URL into a text box, but the link will display as a static link. It would great to have a field type like the Web Site field from the organization profile page that displays the link as a clickable URL.
6 votes -
Defining reply-to email address at email template level
All our emails are sent from "no-reply@smartsimple.eu"
However, even if this is a "no-reply" email address and we describe in the email body the one to use to reply, users continue to use the "reply" button of their email client. So, we would like to define, at the email template level, the reply email address to use (can't be a global parameter as multiple internal teams are involved).
For now, we try to use the "(reply-to)" feature in cc (see screenshot - do not remove it!) but this is not very practical8 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…
10 votes -
Permission Quick Edit: Security Matrix checkboxes for Fields
It would be really helpful to have the option in the various Security Matrix sections to toggle all the checkboxes on or off across for a particular field, not just down for a Role or Status.
And as we can do with the 3 dots in the header row to "Copy Row Settings", I'd like to be able to "Copy Field Settings".
Use Case: I have a similar update I'd like to make to a large number of new fields to remove all the current permissions and replace with updated permissions and need to go through each field and each…
6 votesMonitoring Interest ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We will monitor interest for future consideration.
-
Fiscal Year
Many clients have fiscal years that are not calendar years. We need an easy way to set the fiscal year (e.g. 10/1-9/30) and be able to use this to filter list views.
4 votes -
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.
8 votes -
Give the option to just run a Charity Check report through the GuideStar extension, rather than it pulling the entire "Pro" report
A recent SmartSimple update included a change with the GuideStar Charity Check feature, where it now pulls a GuideStar Pro report versus just pulling the Charity Check report. I'm not sure if it's just us or if there are any other clients have found this to be burdensome to their processes for a couple of reasons.
1) It now takes so much longer for the report to be pulled into the record (at least 5-10 minutes). So, it's not as immediate as it once was.
2) We don't use all of the other information that is in the Pro report.…
5 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#.
7 votes -
Advanced Data Table - Column Width Control
The columns on advanced data tables, and other sections of SmartSimple, are limited to Small Medium Large XLarge (or equivalent). This isn't great, and they also regularly don't work because the text fields become the adjustable ones anyway. It would be better to be percentages and all fields in a column/row to follow on from their header. The boxes could then still be adjustable, but start at the relevant size. The aesthetic is quite poor currently.
4 votesMonitoring Interest ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We see this as a usability improvement opportunity and will monitor interest to determine if the priority becomes higher.
-
On Full Flow Diagrams, the jumbled boxes showing Status, Workflow, and Buttons relationships should start in an initial arranged order
Full Flow diagrams start out as a jumbled mess which have to be sorted manually to get an idea of the overall picture. Can you present this diagram in an arranged order that shows the overall relationships clearly? A before and after example has been uploaded to show how it could be ordered. Statuses and buttons are aligned columnwise with buttons between statuses.
5 votes -
Add alternative signatory to sign while using Adobe e-sign
In Adobe e-sign, a user is able to assign a signatory and an alternative signatory (proxy signatory) to the same signature spot, but only one can sign. Would it be possible to do the same in the Smart Simple platform, as Adobe eSign is used as the interface?
6 votes -
Field Change History and Workflow History
Currently, on a Level One record, the Logs button includes two separate items: Field Change History and Workflow History. Our developer has proposed consolidating Field Change History into Workflow History to streamline the debugging process.
This would allow developers to view data changes—such as values passed to custom fields—directly within the workflow history. If a workflow fails, this visibility would make it easier to trace what data was modified at each step, improving troubleshooting efficiency without the need to switch between tabs.
6 votes -
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.
4 votes -
Dynamic Visibility should copy over to new System Versions
Currently, when SmartVersioning is used, it will copy over all the fields in the Core version to the new version. It does not, however, copy over the dynamic visibility. So if the dynamic visibility changes between versions, you have to manually keep all of your dynamic visibilities updated to the newest versions. This is a pain when you have to manage dozens of dynamic visibility fields.
It would make more sense that, if a dynamic visibility is set to the Core version, that it automatically adds the new version that is stamped from the Core. If fore some reason this…
4 votes
- Don't see your idea?