270 results found
-
Advanced Data Table - Total Row Validation on dynamic advanced data table sections
Often times clients want to enforce a minimum or maximum amounts on certain columns such as request amount or match amount on an advanced data table total row. This currently isn't possible without passing the data to a static section. This makes validation tedious and time consuming to configure, but also more complicated for a client to edit and update later.
One should be able to use validation in the amounts in the total row only such as:
-Comparing the amount in one column to a field on the grant or linked cycle
-Comparing the amount in one total column…6 votes -
Move record locks from record level to tab or field level
Consider allowing concurrent record access as long as same field (or alternatively) same tab isn't being edited. There's good reason to have record locks for many orgs and use cases, but the whole record doesn't necessarily need to be locked.
Applicants and grantees typically wait until the deadline to submit. Suppose two staff members are collaborating simultaneously on different tabs / fields as deadline approaches. With record locks, there's a fair bit of coordination w/ applicant grantee to submit in timely fashion. If record locks were made at field or tab as opposed to record as a whole, it would…
9 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.
8 votes -
Enhance Auto Assignment Feature
It would be nice to be able to use the auto assignment feature as follows instead of having to use workflows and enable this to be used with the contacts tab instead of assigned sf:
1) When a new user is added in a particular role to the contacts tab of an L1, automatically assign them to the L2s in the contacts tab as a particular role
2) When a new L2 is created and users from the L1 are set to auto assign to the L2, the assignment is passed upon activity creation
3) When a user is removed…5 votesMonitoring Interest ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
There are multiple parts to this idea. One is that we will ensure the auto-assignment works for single users, this ticket will represent the request to support multiple contacts. We may also consider supporting deletions, but that will be after we deliver this first step of supporting multiple contacts.
-
Improve Custom Field Type: Text Box - Date
Improve the Custom Field Type "Text Box - Date" by adding the possibility to enter a range of selected dates. Today it is only possible to add a default value into the Calendar but for example it is not possible to prevent the client from selecting a date prior to the default value date. The proposition would be to have the possibility to add a range of predefined date: the client could select dates only within the specified perid of time added in the range.
10 votes -
Link Payments and Reports to support automation
We'd like to link Payments and Reports in a meaningful way to support automated Payment Status updates. We currently have a 'soft link' configured so that you can see required Reports and their approval status on a Payment record. But staff must manually update the Payment status once all associated Reports are in an Approved Status.
2 votes -
Slack Integration
Add a Slack integration for SmartSimple so teams can receive automated messages when action is needed, such as approvals, tasks, updates, or missing information. Messages could include basic details, a link to the SmartSimple record, and buttons like Approve or Reject. Users could take quick action directly from Slack, while SmartSimple saves the response. Admins could choose which workflows send Slack messages and who receives them. This would help reduce email, speed up decisions, and make it easier for users to stay on top of important SmartSimple tasks.
1 vote -
Add a schema builder feature that displays selected objects, their fields, relationships, and included workflows.
See the attached example from Salesforce.
5 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 -
Pass a Javascript variable to a ReportProperty
Allow to pass a javascript variable to a ReportProperty syntax.
It will be very useful in a SmartCheckValidation.
Example (in SCV):
var sID;
var sResults = @ReportProperty(1234,exportdata,,sID)@;2 votes -
Page to last/next page from button of list view list from My Profile
UX on list view differs from profile. From list view, the next/last page sticks to top of page as you scroll. On dashboard, it doesn't and when you scroll down through results you lose the next/back buttons.
Would be good to have similar functionality on "My Profile" that exists for list views
2 votes -
We would like to propose a feature that enables bulk (batch) translation of applicant-entered content in custom fields using SmartSimple’s e
We would like to propose a feature that enables bulk (batch) translation of applicant-entered content in custom fields using SmartSimple’s existing in-tool translation functionality. Currently, translations must be performed manually field by field by clicking the translation button, selecting a target language, and choosing the destination field for storing the translated content. We are not referring to translating field captions/labels, but rather the actual responses submitted by applicants.
1 voteIt sounds like you are currently using the Enable Field Translation Service to translate applicant‑entered content and store the translated text in separate custom fields by manually clicking the Translate button on each field.
If your goal is to translate multiple applicant‑entered fields in a single action, you may want to consider using a workflow with the task type Translate Field Values. This approach may allow you to execute the translations in batch. You could then expose this workflow through a single button on the application form, enabling on‑demand translation of all relevant fields without needing to translate each field individually.
While this is not a native bulk‑translate action within the SmartField interface itself, it might effectively achieve the desired outcome with less manual effort. I suggest escalating to Support if you’d like assistance with configuring the workflow or validating the setup.
If you are still interested in a native…
-
Reduce Configuration Requirements for Word Merge
There are clients who leverage the word merge field to consolidate data across multiple L2s (often grant reports) under a grant application and map it to a word template. The configuration for this is very syntax heavy and leverages a lot of list syntax and/or report property syntax.
The amount of effort to support clients with this functionality often warrants an RFS. It would be nice to have a UI for selecting the L2s and the fields to be included in the word template. Some HTML work will still be required but perhaps we can eliminate the need for list…
2 votes -
Rich Text Editor - Add Header option
The old Rich Text Editor had the option to add headers to text without using tags. It would be ideal if this functionality could be added back into the new Rich Text Editor. This would save our users a lot of time.
2 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.
10 votes -
Advanced Data Table Dynamic Sections Options to Hide the Plus and Minus Buttons without Scripting
Currently if columns in an XML should be updated in say a progress report, but rows shouldn't be able to be deleted or added, the +/- buttons on the dynamic section have to be hidden with custom script. Instead it would be great if there was a setting on each dynamic section to hide the +/- buttons based on status and/or role - perhaps a visibility condition like we have for edit conditions on the column? This would make initial configuration and ongoing changes easier.
5 votes -
Message when Excel Parser is still Processing
When the excel parser runs, it's always been running in the background. It would be nice if there was a message of some sort on the upload field to indicate that the parser is still working and when the parser has finished parsing. It could be a circle or something, but there needs to be a message to indicate the parser is still working. Otherwise when users try to interact with the records that have been parsed, it looks like it didn't finish even though it just needs more time.
5 votes -
Allow for accounts to be created/accessed with either a Username or Email Address
We are running into a limitation whereby applicants/users have a need to change their email addresses on a semi-regular basis. Researchers move institutions frequently enough and when doing so they will receive new email addresses.
This often leads to duplicate accounts if they need to reset their password and don't have access to their original email address at the previous institutions. Additionally, if they don't remember having created an account and then register under their new email address, this bypasses the duplicate check. Lastly, using the email address limits the ability to update the email address without making their account…
9 votes -
Navigation buttons on grant management application stage
For cost recovery applications. Currently in the desktop and mobile versions, the back and forth navigation arrow and next and back button are very small.
Application Stage:
Changing the left and right arrow navigation buttons for scrolling into bold arrows. In IOS and Android, it is very small; making it bold will help the user.
The NEXT and BACK buttons are on the bottom on both sides of the application page—changing this to bold will also be helpful for the SME.
6 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.
3 votes
- Don't see your idea?