Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

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

198 results found

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

    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. It would be helpful see how many records total are selected from a list we are viewing instead of having to manually count. Some of our lists span well over 100 records for different things and if we're needing to select specific records on the list to change the statuses, there is nothing at the top of the page to indicate how many as been selected.

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

    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)
  4. Contracts and collaborative documents across the grant and partnership lifecycle are currently managed primarily through Word documents shared via email. This creates challenges with version control, including multiple document versions, parallel edits, and manual consolidation of changes. Collaboration is fragmented, resulting in limited visibility into document updates, no single source of truth, and limited auditability of changes and negotiations. In addition, the process creates administrative pressure on a small legal function, and contracts are largely managed outside the SmartSimple platform, leading to duplicated documentation and limited traceability.

    To address this, improved collaboration functionality is needed. The solution should allow documents…

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

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

    14 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. Currently, descriptions for uploaded files can be added. It will be helpful to be able to report on each uploaded files, with their description and upload date/time, and user. It will be helpful for staff/reviewers to be able to have a list of files that were uploaded, with the description at hand, as filenames may not be as descriptive.
    Also, since file upload is available thru autoloader, it will nice to be able to add descriptions of files when uploaded thru autoloader.

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

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

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

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

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

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

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

    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. Communicate known issues and their statuses/schedules so clients can review as opposed to creating help desk tickets that may already exist

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

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

    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)
  19. Need the system to track field level changes for red lines, similar to Word.

    11 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. https://wiki.smartsimple.com/wiki/HistoryOf_function

    When using this function, I have to configure with status names. Example from WIKI:

    @HistoryOf(Status::[Value]='Approved'::Update to [Value] by [UpdatedBy] at [UpdatedTime]::[UpdateTime]::desc::1)@

    This is a brittle approach (as this is the caption / front end field name). I'd love the ability to pass the statusid as opposed to status. Even backend field (name) would be better than the caption

    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?