Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

JUMP TO ANOTHER FORUM

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

177 results found

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

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

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

    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

    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)
  4. In the old version, our grant ID numbers would stay at the top of the screen as we scrolled down activity forms. Now they do not. I'd like this one feature to go back to the way it was. In the new look grant ID numbers should stay at the top of the screen as we scroll down the page.

    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)
  5. 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)
  6. The ability to select multiple item in a list view by clicking the first item and shift clicking the last item to select a range of records instead of individually clicking each one would be very helpful.

    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)
  7. 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)
  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. 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)
  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. 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 clarification

    Requested Improvements:
    1. Earlier Release Notes
    2. Share preliminary / upcoming release notes 2–3 months…

    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)
  12. 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…

    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)
  13. 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…

    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. 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)
  15. 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)
  16. 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)
  17. Just like when creating a workflow task allows updating multiple custom fields at once, the same functionality should apply to standard fields. Currently, updating each standard field requires a separate task. So, if I need to update 5 standard fields, I have to create 5 different tasks — whereas for custom fields, all changes can be made within a single task.

    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)
  18. 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)
  19. Full Flow diagrams start out as a jumbled mess which have to be sorted manually to get an idea of the overall picture. Can you present this diagram in an arranged order that shows the overall relationships clearly? A before and after example has been uploaded to show how it could be ordered. Statuses and buttons are aligned columnwise with buttons between statuses.

    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)
  20. When you create a listview that includes advanced data table displays, they are nested into a single excel cell. It would be great if there was an easy way to export out data from advanced data tables so they are parsed into individual cells.

    7 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

    2 comments  ·  Other  ·  Admin →
    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?