131 results found
-
Notifications for users with locked accounts
It would be beneficial to implement a notification system for users who have attempted to log in too many times, informing them that their account is locked for a certain number of minutes. Currently, there is no way to inform them.
Perhaps a 'pop-up' message on the login page would be the most effective solution.
7 votesMonitoring Interest ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We will monitor this idea, the solution may be an email to the user to let them know they are locked and try after X minutes. Today, we have a setting (policy->account lockout) to define who received a locked out notification, typically to the admin.
-
Centralized Logging and Improved Visibility for Configuration Errors
Problem: Logs related to configuration and system behavior are currently fragmented across multiple locations, making troubleshooting slow and inefficient. There is no clear centralized view or consistent process to identify high-impact issues, and important configuration errors are often buried as generic warnings.
Key Gaps:
No single, centralized location for all relevant logs
Configuration-related errors are hard to discover and correlate
Log severity levels are not granular enough, causing critical issues to appear as low-priority warnings
Lack of guidance on whether customers should rely on platform logging or develop internal processesRequested Improvements
Centralized Log Access
Provide a single, unified location…3 votes -
Improve Advance Communication and Testing Window for Platform Upgrades
Problem: Platform upgrades often introduce breaking changes with limited advance notice. Release information typically arrives too close to the upgrade window, leaving insufficient time to assess impact, migrate customizations, and test integrations. This results in avoidable production issues and reactive support tickets.
Key Gaps:
Release notes are usually available only 2–4 weeks before upgrade
Non-prod/backup instances are upgraded too close to prod
Release notes are large and hard to filter for relevant breaking changes
Opening a support ticket is the only way to get clarificationRequested Improvements:
1. Earlier Release Notes
2. Share preliminary / upcoming release notes 2–3 months…2 votesMonitoring Interest ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We will consider options in the future including option of offer a wider window between updates.
-
Ability to modify Quick Assignment Type tool
Would like the ability to configure the Quick Assignment Type/tool so that we could select a default dropdown option for the Quick Assignment Type and Role to Assign dropdowns. It would also be nice to have the option to add a dropdown option of 'Select One' so that users are forced to select an option.
For assigning reviews, a pop-up window appears with two options - Manual User Assignment and Random user Assignment. Would be nice to have the ability to revise the tool tip language.
After using the Quick Assignment Type tool, there is no way to close out…
1 vote -
Request to make the delegation toggle button more visible
can you make this Enable Delegation toggle button more prominent that users cannot overlook easily.
refer to the attached screenshot for your reference.
1 vote -
add level 1 id , level 2 id, and level 3 ids to list views / search criteria
It is onerous to build a report to find the common name (front end name, etc) for a eventid that you find in wf history (or otherwise). I'd love to search for level 1, 2, 3 ids in list views to prevent that extra step of building report just to find a field I can search on list view
2 votes -
Update historyof function - FIELDNAME is brittle
https://wiki.smartsimple.com/wiki/HistoryOf_function
When using this function, I have to configure with status names. Example from WIKI:
@HistoryOf(Status::[Value]='Approved'::Update to [Value] by [UpdatedBy] at [UpdatedTime]::[UpdateTime]::desc::1)@
This is a brittle approach (as this is the caption / front end field name). I'd love the ability to pass the statusid as opposed to status. Even backend field (name) would be better than the caption
3 votes -
Ability to report/extract/import description field in uploaded files
Currently, descriptions for uploaded files can be added. It will be helpful to be able to report on each uploaded files, with their description and upload date/time, and user. It will be helpful for staff/reviewers to be able to have a list of files that were uploaded, with the description at hand, as filenames may not be as descriptive.
Also, since file upload is available thru autoloader, it will nice to be able to add descriptions of files when uploaded thru autoloader.4 votes -
Add Deny View Version feature in Dynamic Field Visibility Control
Add Deny View Version feature for Dynamic Field Visibility Control field (see attached file).
Currently we have to remind which DFVC fields we have and if there is a condition in version feature every time we set up a new submission manager version. This is vey annoying because we have a lot of DFVC (more than 100) and we need to check one by one to add the new version.3 votes -
Replacement of Google reCAPTCHA with a more privacy-friendly alternative
At the moment SmartSimple does use Google reCAPTCHA v2 or v3 as a security measure on the system. The use of Google reCAPCTHA however raises privacy issues since Google uses the data (IP adresses, Browser and device, user info, cookies) for own purposes. Google collects more data than is neccessary for the functioning of the reCAPTCHA. The use of Google reCPATCHA v3 raises even more privacy issues since in v3 Google continously analyses online behaviour and users are not aware anymore that their online behaviour is analyzed.
We would like to have a more privacy friendly reCAPTCHA on the system,…
2 votes -
Add two additional role permission sections for a new folder within a system SmartFolder
The current permissions tab for creating a new folder within a system folder is limited to View Folder and Modify Folder permissions.
Add the "Upload and Move Files" and "Create Sub-Folder" sections under the Role Permissions settings as well.
4 votes -
Disable formulas on end-state statuses
For each formula, we need to configure in formula syntax the statuses that the formula shouldn't run on. It would be incredibly valuable to have end-state statuses control the formula access.
Save draft (on record or triggered through batch update) will trigger formulas inadvertently on end-state statuses like "Approved", "Complete", "Finalized", "Closed", "Paid" unless configured onto each formula
3 votes -
Disable annotations from fields
Add field level configuration to allow disabling of annotations so read-only and display fields aren't annotated inadvertently
4 votes -
Bulk assignment / reassignment / removal of roles on L1s, L2s, L3s
Platform solution to support bulk CRUD updates to L1, L2, and L3 assignments and roles.
We build a report and workflow(s) for each CRUD operation we have to perform in bulk. It's a rather tedious exercise and requires someone with config experience to support
3 votes -
Version comparison report
To quickly compare field differences between two versions of fields in a UTA for a specific level (L1 or L2): Be able to generate a list/report/printout that lists only the fields where there is difference between the two versions. Bonus if it includes what the difference is. This would be kind of like the "Diff" button on custom fields, but it would provide a list only of the fields where there is a difference.
3 votes -
Managing removal of uploaded files
For 'Upload - Multiple Files Storage' where Disable Delete is toggled on, allow System Admin to delete/remove uploaded files (incorrectly uploaded by user) without needing to toggle off Disable Delete across all users.
3 votes -
Allow Group Email on Program Manager Cycles
We need to use the Group Email functionality on the Program Manager > Cycle level to easily communicate with grantees within a certain cycle.
3 votesIt appears the desire is to be able to group email from a consumer provider list view, which is not currently possible, I have changed the status.
-
Expanding Auto Archive Settings
It would be helpful for the Auto Archive feature to be configured per status that triggers it, so that there is more granular control over how records get archived.
For example, despite multiple statuses being able to trigger the archival process, if they must be unarchived, they all get the same status.
Additionally, it would be helpful to also be able to define when the auto archival process happens. For example, perhaps after a day, week, or month. Being able to define that per status add more flexibility.
2 votes -
Data Retention Policy Updates
We need the ability to upload new files after previous files have been removed through the data retention policy. To support this, it may be necessary to introduce an additional retention option—for example, an option that removes the file/data but unlocks the field for new uploads, as opposed to the current setting that simply removes the file/data.
A typical use case is annual reporting, where applicants are required to submit fresh documentation each year in the same report. In these scenarios, the field must be cleared according to retention rules, but still remain open for new uploads moving forward.
2 votes -
"Lookup - Organization and People" fields updated via workflow task
It would be helpful if "Lookup - Organization and People" field type could be updated via workflow task. Currently, If you try to add this field in an "Update custom field value task" you get a message "Not Records Found".
In a process where an organization is moved to a specific status and some fields are updated via workflow, it would be nice to also be able to update the "Lookup - Organization and People" ones.
2 votes
- Don't see your idea?