46 results found
-
Mail Run queue limit
Could we have the option in the Mail Run queue limit to set it at 80, or to be able to manually type a number in for the number of emails to send to our SMTP server at once, rather than having a drop-down list? Or keep the drop-down but have the option of 'other', and when selected, you can type in the number of emails to release at once.
The reason for this request is our SMTP service limits sending to 100 emails at a time, but if we set the limit to be 100 and a few extras…
7 votesNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We don't see this as a high priority with the option to reduce to 50.
-
Ability to use "objemail" variable in BCC line
We often include the "objemail" variable (copied from an application record) in the To or CC line when we generate an email to a grantee from Outlook. By including the "objemail" variable in the To or CC line, the email will then be attached automatically to the application record. However, the functionality does not work if we include the "objemail" variable in the BCC line. Since the "objemail" variable is a long string of characters, we would find value in using it in the BCC line so that it is hidden from recipients to avoid any confusion on their end.
3 votes -
notes
Allow to edit the date of a note being entered - or- include date as a field when bulk importing notes via the autoloader.
2 votesNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Allowing the date and time of a note to be changed introduces tension between data integrity and operational convenience. By design, notes are currently locked to their created date, which represents a system fact rather than user intent. This approach supports auditability, compliance, and overall trustworthiness of the data.
Enabling users to change note dates could allow timelines to be manipulated and may reduce the validity and reliability of this information. That said, we understand valid scenarios such as bulk migration or backfilling historical data, where preserving the original creation date may be important. For those cases, maybe we could consider setting the created date as part of a controlled import process. Another idea would be adding an effective date within the content of the note.
-
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
-
Allow nested logic within SSlogic
Allowing an sslogic statement within another sslogic statement would be very helpful.
2 votesNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Available with if and else if today, no plans for nested logic
-
Switch Primary Dataset in Reports
Would love to switch primary dataset in reports after they have been created for simplicity and convenience when tying to wfs / Gort export
2 votesNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Not planning in the near term
-
Duplicate Role/Portal
It would be great if you could duplicate a role and therefore the portal associated to the role. Have created a role with specific permissions and access including a special portal - lots of work involved and would love to be able to duplicate and fine tune to create a similar role/portal.
2 votesNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Recommended practice is to use the common portal, however, we do plan to enhance the portal builder in the future.
-
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.
-
Create an option to automatically name folders when batch downloading files through list views.
Currently, the downloaded folders are automatically named using their application IDs.
2 votesNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
The IDs ensure uniqueness. You can change the folders after downloaded. We do not have plans to provide this additional enhancement.
-
allow DRAFT option in new support hub
(I was directed to submit this via IdeaLab regarding the support hub at supporthub.smartsimple.com )
Add the ability to save a draft of a ticket's content before submitting it
In the previous support hub environment, it was possible to save a draft of the ticket before submitting. This was helpful in multiple scenarios including, locating examples to cite, creating videos or images to be attached, and when interrupted before completing the entry.
2 votesNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
This request has been passed to Support for consideration. I have closed it on the product side.
-
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.
-
pdf generation
We would like the ability to have SmartFields pull fields into the summary PDF based on the type of application / program. Having this universal doesn't work when you have many types of applications with various needs.
1 voteSmartFields are designed to display all fields associated with a given application type. Fields that are not part of an application type will not appear in the generated summary PDF for that type.
If fields are shared across multiple application types but you need more granular control over which fields appear in the PDF for each type, there is a possible workaround. The @SmartFields(customfieldids)@ token can be used to return a subset of fields by specifying a comma‑delimited list of custom field IDs. By creating separate web page views for each application type and generating the PDF from those web page view fields, you can control which fields are included per type.
We acknowledge that this approach requires additional configuration and ongoing maintenance, and is not ideal.
While we see the value and utility in having more flexible, type‑specific SmartField behavior for PDF generation, this is not an enhancement we…
-
Gort Automation - Sync Down (Decouple config and data)
I want to decouple the configuration from the data sync. So we can move just our data to a lower environment without having the higher env config impact lower environment
1 voteWe understand the request to decouple configuration from data synchronization so that data can be moved to lower environments without affecting existing configuration, and we recognize the value in that approach.
However, data in the system is closely tied to the configuration and underlying structures it relies on. Supporting data-only synchronization without ensuring those structures align is not something we plan to pursue in the near future. That said, we appreciate the feedback and will keep it in mind as we consider longer-term improvements to environment management.
-
Remove the automatic title "New"
When an application is created, there is an automatic "New" inserted into the title such as "New Admissibility" "New subvention" and sometimes the title of the form does not make sense because of this "New". Would it be possible to change this title as we wish? Or at least have the "New" Removed ?
1 voteWhen the New Application or New Anything button is used, the system creates a new record and applies a default title beginning with “New” to indicate that the application is in an initial, unsaved state. This placeholder remains until the user updates the title and saves the record.
While we understand the concern and agree this is a valid request, the current behavior is intentional and helps ensure clarity and consistency when new records are created.
At this time, adding the ability to customize or removing the default “New” prefix is not something we are planning to address in the near future, but we appreciate the feedback. Feel free to reach out with clarity if we misunderstood anything.
-
Add “Exclude Grant Types” Option for Activity Availability
We propose adding an “Exclude Grant Types” option under Activity Permissions and Availability. Currently, the “Available to Grant Types” field allows administrators to select which grant types an activity applies to, but many of our activities are relevant to nearly all grant types except one or two. Selecting every applicable grant type individually is time-consuming and inefficient given the large number of grant types we manage. An Exclude Grant Types field would allow us to simply select the exceptions, automatically making the activity available to all other grant types. This would save time, reduce administrative effort, and improve accuracy when…
1 voteNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Add exclusion rule will create additional complexity we are not planning for.
-
Please add status and type IDs to the Archive feature
Can you please add status and type IDs to all applicable csv files included in the zip file created by the platform archive feature? For example these are both missing from the applications and activities csv files, both which only include status and type names. Having IDs would be useful for downstream use of the feature.
1 voteNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
This is not planned as we are targeting an enhancement in the June release (API Endpoint Extraction, see roadmap) which will enable a more flexible export option to support a wider range of use cases beyond just archiving to extract data from SmartSimple.
-
Group Email - Add the possibility to choose a user role or a standard field as CC
Currently when we select Group Email : for the recipient of the email we can choose a user role or a standard field such as primary contact, staff etc. but for the contacts in CC we do not have the possibility to choose a standard field or user role. I have just sent an email and I would have loved having the possibility to choose the standard field staff as CC of the recipients.
1 voteWe recognize the value of the request; however, it’s not something we would consider at this time.
-
email address change verification email time limit
Currently the verification email for email address changes has a time limit of 2 hours. This limit is very short for our organizations & staff. There is understanding that this is in place for security. We would prefer to see 24 hours or it be customizable based on an organization's risk tolerance.
In our environment 2 hours is too short so we end having to go through the process multiple times to send multiple verification emails to the user. Typically, users send an email staff requesting the change. Staff review the request withing their workload and make the update triggering…
1 voteNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
The timeline is based upon security reasons. We will have your Client Engagement Manager reach out to you to discuss the process and options.
-
Set default for single folder download
Our program area downloads pdfs of all our analyses. On the download files option, the default is set to create a folder for each grant which ends up with a complicated tree structure of folders. There is an option to choose a single folder download to dump all the pdfs together. This is the one we always want.
It would be nice to either have the single folder as the default setting or at least be able to change the default... Or perhaps make the folder structure a mandatory choice. Anything so that we don't download everything and then have…
1 voteNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We understand the value, but it isn't something we plan to consider in the next 12+ months. We may revisit if there is more interest.
-
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.
- Don't see your idea?