194 results found
-
Enable download option from listviews for Upload - Image fields
The current functionality within listviews allows the user, if the option is enabled, to request the download of the files in a specific Upload - Multiple file storage field to a ZIP file.
This functionality is not currently available for the field type Upload - Image. We would like to have this option available, as the current workaround requires the configuration of 2 API services and short script to get the same result.
9 votes -
The ability to batch update Notes
It is possible to batch update for status, institutions, associated contacts (etc), but it is not possible to do it on Notes.
Is there something I am overlooking? :)
5 votesFeedback Needed ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
@Emil - sorry for the delay, can you provide examples of use cases where you need to batch update notes? Thanks
-
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 practical14 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
4 votes -
Disable annotations from fields
Add field level configuration to allow disabling of annotations so read-only and display fields aren't annotated inadvertently
5 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
4 votes -
Custom Fields Permission Quick Edit - freeze top/left headers for Role and Status; add in field Caption
When we need to update the custom field permissions, the Permission Quick Edit is often unusable. Once you scroll down a small amount, you lose the header row and can't tell what role or status you're changing. Same for when you scroll to the right, you lose the Custom Field column on the far left and have no idea what field you're editing.
We also usually don't really know the field's name as well as we know the Caption. It would be so helpful to include both the name and caption for reference so you know you're really updating the…
13 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.
16 votes -
Org and Contact Profile Verifications
Currently to have any sort of verification process on org profiles and contact profiles being up to date one has to use statuses and workflows to push them back and forth and this is the best practice for verifying these are up to date when submitting an application.
Many clients request the ability to check whether these have been updated recently by the applicant as part of the application submission process. It would be nice if there was a way to enforce that applicants confirm their org/contact profiles are up to date without having to configure statuses. Similarly with the…
7 votes -
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.
6 votes -
Tracking Recent Actions of Users
We’re wondering if there’s a setting or feature we could enable that would allow a user to see their own recent activity in SmartSimple.
This could be somewhat general (e.g., modified grant ID X on X date/time, modified Organization X on X date/time, etc.) or more granular (e.g., updated field X on grant ID X on X date/time, created a note on grant ID X on X date/time, etc.).
This would be helpful for internal staff members who are adding Notes or making changes to many grant records and want to look back at which grants they've recently edited.
3 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…
17 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 -
Ability to Copy/Save As SmartVersions
We build funding applications using SmartVersions. Sometimes we have a minor update to a SmartVersion we would like to make for a future competition but want to keep the original SmartVersion as well. It would be great if we could Copy or Save As a SmartVersion the same way you can Copy or Save As a Custom Field so we don't have to start from scratch each time.
12 votes -
Red Lining/Track Changes
Need the system to track field level changes for red lines, similar to Word.
11 votes -
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
3 votes -
T2P Project Based Tool Improvements Needed
Prior to promoting changes in the Target environment, we see a comparison log that is similar to what we see in the desktop T2P tool. However, it was not clear that all the changes were represented in the Export package. The comparison log could also include additional information that could make it more useful like Date Changed, Time Changed, User, etc. Additionally, there is no way to export or save the comparison log, and after promoting changes, it is no longer accessible.
After promoting changes to the target environment, we can see the Import Log, which in some cases, will…
5 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 -
Add a "highlighter" for reviewing text in L1 applications and L2 reports
"Highlights" are exactly what they sound like - background color added to specific selected text.
Permission L1 and L2 form types to accept highlights - application types, report types, etc.
Permission highlighter function for various roles (staff, reviewer, evaluator, etc.) - Permissions should include "Create/view highlight" (user can create and see their own highlights), "View all role highlights" (enable reviewers to see each others' highlights IF this function is invoked on the highlight control menu), "View all highlights" (enable users with this role to see all highlights when invoked on the highlight control menu), and "Highlight PDF" (enable use of…
1 voteMonitoring Interest ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
A part of a larger evaluation, we have linked this idea to the broader discussion around integration opportunities with Microsoft Word.
-
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…
9 votes
- Don't see your idea?