Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

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

249 results found

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

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

    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)
  3. Sys admins can search across workflows and tasks, but we can't search against / see connector IDs.

    Project based T2P lets you see the workflow IDs that have been updated, but there's no traceability to the connector ID when looking at a connector in wf.

    At a minimum, I'd like to see the connector ID on the connector itself. Even better if I can search against a connector list to see what was updated

    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)
  4. I've recently seen great improvements to the grantee user experience when I've utilized the Linked Record List Custom Field "Simplified Association Interface" toggle for Contact Associations, but this option is not currently available for Organization Associations as well as some other list types.

    Please consider adding the "Simplified Association Interface" option for Organization Association list types, as well as all other list types, if possible.

    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)
  5. Currently, when SmartVersioning is used, it will copy over all the fields in the Core version to the new version. It does not, however, copy over the dynamic visibility. So if the dynamic visibility changes between versions, you have to manually keep all of your dynamic visibilities updated to the newest versions. This is a pain when you have to manage dozens of dynamic visibility fields.

    It would make more sense that, if a dynamic visibility is set to the Core version, that it automatically adds the new version that is stamped from the Core. If fore some reason this…

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

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

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

    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)
  9. "Highlights" are exactly what they sound like - background color added to specific selected text.

    1. Permission L1 and L2 form types to accept highlights - application types, report types, etc.

    2. Permission highlighter function for various roles (staff, reviewer, evaluator, etc.) - Permissions should include "Create/view highlight" (user can create and see their own highlights), "View all role highlights" (enable reviewers to see each others' highlights IF this function is invoked on the highlight control menu), "View all highlights" (enable users with this role to see all highlights when invoked on the highlight control menu), and "Highlight PDF" (enable use of…

    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)
  10. A recent SmartSimple update included a change with the GuideStar Charity Check feature, where it now pulls a GuideStar Pro report versus just pulling the Charity Check report. I'm not sure if it's just us or if there are any other clients have found this to be burdensome to their processes for a couple of reasons.

    1) It now takes so much longer for the report to be pulled into the record (at least 5-10 minutes). So, it's not as immediate as it once was.

    2) We don't use all of the other information that is in the Pro report.…

    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)
  11. Support mTLS for restful API

    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. The current permissions tab for creating a new folder within a system folder is limited to View Folder and Modify Folder permissions.

    Add the "Upload and Move Files" and "Create Sub-Folder" sections under the Role Permissions settings as well.

    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)
  13. When you create a L1 list view, you can include fields from the L1 owner.
    I would like to do the same for L2 and L3 list views (i.e. include L2 owner fields in L2 list views and include L3 owner fields in L3 list views).

    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)
  14. We had a batch of outgoing 'thank you for submitting your application' emails fail because the because the PDF copy of the application exceeded the system's 10MB limit. We use file attachments across applications and grantee reporting and we like to include a PDF summary of whatever got submitted, but the 10MB attachment limit prevents us from doing so, particularly for our lengthy research applications.

    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

    Proposed Idea  ·  0 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)
  15. 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)
  16. 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.

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

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

    13 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. Problem:
    Current flat menu structure lacks information hierarchy. As feature set expands, navigation becomes cluttered and difficult to scan.

    Suggestion:
    Support Level 2 nested dropdowns in global navigation for a cleaner information architecture, to reduce cognitive load, and to improve accessibility for keyboard navigation.

    Example: Reports
    - Level 1: Track Reports
    - Level 2: Processing (Reports Pending Approval, Overdue Reports)

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