Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

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

221 results found

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

    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. Batch update of contacts using "update" feature doesn’t run UTA assignment workflow, but “add” does. We’ve reverted to a two-step process to make personnel changes (e.g. new person filling in for old person) to add then remove as opposed to one-step update process for personnel changes because of the unintended consequences with UTA assignment workflow. Is this a platform bug? Or was it never built to trigger wf for updates

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

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

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

    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. Improve the dynamic visuals: Many organisations use filtered data fields — for example, choosing a centre should limit the available team options to those within that centre. At the moment, the dynamic visuals don’t respect these filters. Instead of narrowing the list to relevant teams, they display every team from all centres. A more precise way to filter visuals would be valuable for many organisations.

    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)
  9. In our Grants and Fellowships programmes, we require our candidates to link their application to publicly available publications, papers, etc. as to build the State of Art, Methodology, etc. of their project.

    Currently SmartSimple supports some Publication search engines natively (Scopus, Web of Science and PubMed as far as we are aware). These are all good resources, but there is a new source which is becoming more popular - OpenAlex -. As it stands, we are building a custom integration with their API for the Fellowships instance, but we would like to suggest that SmartSimple builds a native integration with…

    1 vote

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

    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)
  11. Currently, some categories (e.g., "Sub-Organisations") appear in the left-hand side menu even when they are not used. For instance, when adding organisations, the "Sub-Organisations" category is not relevant, yet it cannot be removed. The system should allow administrators to hide or delete categories that are not applicable to improve usability and reduce menu clutter.

    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)
  12. 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)
  13. Flagged notes are helpful if they're brief. However, when a flagged note has replies, every part of the thread is posted on the Application. I want to enable flagged notes to minimize or hide their replies to reduce the space they would take up on the Application.

    1 vote

    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. 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)
  15. 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)
  16. 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)
  17. Stacked bar charts are often requested by clients as part of portal design and aren't currently an option with built in portal charts. A common ask is for something such as stacking charts and displays from the budget manager such as committed, paid and remaining amounts. While this can be done with a custom report, The ability to do it off of a list view in a portal would make this much easier from a configuration and client perspective. Often clients want a full list of budgets with these fields along with a portal chart, so it would be nice…

    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. Introduce a rollback feature in the new project-based T2P tool to allow reverting configuration changes promoted to test or production environments.

    Use Case:
    After promoting changes to a test environment, testing revealed issues, and a decision was made to not proceed with those configuration changes. In this case, the rollback feature would allow reverting specific changes within the current environment to its prior state. Similarly, if changes have been promoted to production and need to be temporarily undone, the rollback function would enable this.

    Implementation:
    On the Import tab of the T2P tool, capture the pre-change state before applying any…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Often review forms are configured with a conflict of interest status. In the conflict of interest status, reviewers should be able to see a few fields from the application, but not have access to the full application. Currently the only way to configure this is to disable the reviewer from viewing the parent record and configuring a custom field to be used to view the grant in split screen. It would be nice if instead of having to configure a specific field that the view parent/split screen option could be configured to only be visible in specific statuses as built…

    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. I have a couple of clients that are using the person to person relationship in SmartSimple. This is an older feature that hasn't gotten a lot of love/updates and it would be nice if we could update the UI to match the UI we have for Associations. Right now the UI is pretty out dated and it feels clunky to navigate.

    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)
  • Don't see your idea?