Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

166 results found

  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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:

    1. 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.

    2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  1 comment  ·  Grant Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. When a UTA is using SmartVersioning, I would like to be able to add the @version@ information in reports (similar to what you can do in list views)

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. The list view search and filter criteria far exceeds the workflow search (which only allows 1 condition). Would love to see the functionality that is currently available in UTA searches be applied to workflow and task searches

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add an ability to train AI to recognize the document we are requesting. Applicants can then get a warning that it doesnt look like they are uploading the correct document, and flag it for reviewers.

    The next step would be to use AI to scan the uploaded documents for data and then use that data in the application without the user having to reenter information.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Communicate known issues and their statuses/schedules so clients can review as opposed to creating help desk tickets that may already exist

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Fix the left hand column in the report builder which tells you which row is the dataset, field, field ID etc. so if you add multiple columns and have to scroll to the right, you can still see what each row is for

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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?

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. It would be helpful if the left navigation menu on records can be toggled between the full width and a compact view on a record-by-record basis. This would help on smaller screens or when adjusting the size of the window. It would allow the fields on a record have more of the useable space.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. When using the batch update for a Lookup - Autocomplete custom field having the ability to search the list of options is helpful when navigating a long list of options. Currently you must scroll through the alphabetical list which is time consuming and prone to errors.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Left menu which are displayed on the Company (organization) portal, should be visible based on the roles. We cannot restrict the visibility of the tab based on the role.

    From the UTA when we enable the setting "Enable Applications list view on Organization Profile - Display List of Applications associated with the Organization under their profile.

    eg. Applications UTA setting
    Internal users should see the Applications listed on the Organizations, but the external School user should not see this tab when they view the organization.
    With the permissions set on the listview we can hide the list from school users…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. While I love the new upgraded reminder function on emails, the limited selection of reminders is frustrating. There are a lot of choices for reminders on upcoming tasks but only 1 Day After and 3 Days After for a choice on overdue email reminders. It would be really nice if we could also set up a wider selection of Overdue email reminders.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. When a static section is required in an advanced data table, clients still want to be able to query the data across records. While technically they can in a report, the only way to make this more user friendly at the moment is to create hidden fields that are populated with template formulas or try to make the section dynamic and map to L2s.

    It would be much more user friendly and make configuration easier if you could just map each applicable cell to a field on the same record level. This would reduce template formulas that have to run…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Currently, when using the @notes@ token in email templates, all formatting (such as line breaks, bullet points, etc.) is lost and the note appears as one large paragraph.

    The idea is to preserve the original formatting of the note so that it displays clearly in the email, exactly as it was entered in the system.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?