267 results found

1. Make ORCID data available in applications

   We need biographical sketch information in our applications. We do not want do deal with uploaded files - they are a pain to proof for consistency AND uploaded files are also hard to pull data from when analyzing trends on applications. All of our science applicants have ORCIDs which contain all of these data. However, there is currently no way to select ORCID data (which is already displaying on the profile) to populate fields on the application form.

   It would be great to be able to have fields on the application and allow applicants to select from ORCID records of relevant type to populate those fields.

   We need biographical sketch information in our applications. We do not want do deal with uploaded files - they are a pain to proof for consistency AND uploaded files are also hard to pull data from when analyzing trends on applications. All of our science applicants have ORCIDs which contain all of these data. However, there is currently no way to select ORCID data (which is already displaying on the profile) to populate fields on the application form.

   It would be great to be able to have fields on the application and allow applicants to select from ORCID records of… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Proposed Idea  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. New SmartConnect Trigger Workflow Method

   The old Pandora API had a method that allowed us to trigger workflows by passing the workflow id along a few other parameters. This functionality was never passed onto the SmartConnect API. Currently the only way to "trigger" a workflow via the SmartConnect API is to create a redundant record and set a status. This is obviously not an efficient workflow for us as it creates unnecessary records that we now have to clean up at some point. It would greatly appreciated if a "Trigger Workflow" method could be added to the API that could be triggered against any Level One, Two or Three, Contact, Company and Transaction in the same manner as the Pandora API allowed.

   The old Pandora API had a method that allowed us to trigger workflows by passing the workflow id along a few other parameters. This functionality was never passed onto the SmartConnect API. Currently the only way to "trigger" a workflow via the SmartConnect API is to create a redundant record and set a status. This is obviously not an efficient workflow for us as it creates unnecessary records that we now have to clean up at some point. It would greatly appreciated if a "Trigger Workflow" method could be added to the API that could be triggered against any Level… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Monitoring Interest  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Defining reply-to email address at email template level

   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

   •  

   16 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Monitoring Interest  ·  1 comment  ·  Communication  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Enable download option from listviews for Upload - Image fields

   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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Monitoring Interest  ·  0 comments  ·  Grant Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Custom Fields Permission Quick Edit - freeze top/left headers for Role and Status; add in field Caption

   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 intended field(s).

   See screenshot of a grid of checkboxes that I can't tell what they are for.

   We sometimes are adding or updating a role and want to compare with another existing role. It would be great if we could drag or reorder the roles to put the ones we want to use next to each other. Or toggle on/off or allow us to "hide" some columns for roles so we only display the role(s) we're interested in seeing at the moment. Similar functionality for Status would also be helpful.

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

   •  

   15 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Consideration  ·  1 comment  ·  Administration  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Search against connectors

   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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Monitoring Interest  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Ability to train and use AI to review uploaded files

   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.

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Artificial Intelligence  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Monitoring Interest  ·  AdminJohn Fulton (Director of Product Management, SmartSimple, Foundant Technologies) responded

   We are exploring multiple approaches to leverage external sources and documents with AI, as this capability is foundational to our overall strategy. This concept encompasses several potential AI use cases, including notifications and intelligent data consumption. We will monitor these ideas closely as we develop and iterate on new AI use cases.

8. Linked Record List Custom Fields: Enable Simplified Association Interface on the Assigned Organizations list type

   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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Consideration  ·  0 comments  ·  User Interface / User Experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Dynamic Visibility should copy over to new System Versions

   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 can't be done across the board, then at least having a toggle on the dynamic visibility fields to enable copying to new versions would help.

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

   12 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Monitoring Interest  ·  0 comments  ·  Administration  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Batch Update to Remove Assigned Contacts

    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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Monitoring Interest  ·  1 comment  ·  User Interface / User Experience  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Update historyof function - FIELDNAME is brittle

    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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Monitoring Interest  ·  0 comments  ·  Workflow  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add a "highlighter" for reviewing text in L1 applications and L2 reports

    "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 "Generate PDF" function on the Highlight menu.)

    3. Assign highlighter colors - default color for each role, but enable user-specific colors. These assignments should be visible when a user hovers over the highlighted text. ("Staff", "Reviewer", "Username One, Username Two" etc.)

    4. Make Highlighter Menu appear when permissioned users are viewing and/or editing L1 or L2 highlight-enabled Types. Menu:

    "Create highlights"
    "View Highlights"
    "Copy/Paste Highlighted Text"
    "Select All/Copy"
    "Generate Highlighted PDF"

    "Create Highlights" and "View Highlights" click on and off using the menu.

    "Copy/Paste Highlighted Text" allow user to select and copy specific highlighted text, and "Select/Copy All" copies all highlighted text, for pasting.

    "Generate PDF" generates a one-time printable/downloadable PDF showing whatever highlights the user role has permissions to view, and includes at the top a "legend" showing the highlight color(s) and who they are assigned to, and shows it in a browser tab.

    Use Case 1: Reviewer assigned application to review highlights items in text that relate to the review rubric, copy/pastes specific highlighted text into the Explain Rating fields in the Review form and uses highlighted text to explain why they rated an item as they did. When their review is completed, they generate and print out a PDF with all their highlights on it to bring to the Selection meeting. At the Selection Meeting, staff either screen-shares the application or shares a PDF showing all highlights from all Reviewers, for discussion.

    Use Case 2: Two staff assigned to review and approve a Progress report each highlight items as they view the report, and copy/paste them into the "Reviewer Comments" fields, and view each others' highlights and comments prior to determining final approval or return for revisions on the report.

    "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… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Grant Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Monitoring Interest  ·  AdminJohn Fulton (Director of Product Management, SmartSimple, Foundant Technologies) responded

    A part of a larger evaluation, we have linked this idea to the broader discussion around integration opportunities with Microsoft Word.

13. Ability to Copy/Save As SmartVersions

    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.

    14 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Monitoring Interest  ·  1 comment  ·  Administration  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Give the option to just run a Charity Check report through the GuideStar extension, rather than it pulling the entire "Pro" report

    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. We are just looking for the charity check report to confirm an organization is a 501c3 and would have to manually pull that page from the Pro report for processes.

    We have currently been doing a workaround by going directly to GuideStar and searching an organization to pull their Charity Check report, which defeats the purpose of having and paying for the Candid extension for us!

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

    11 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Consideration  ·  3 comments  ·  Administration  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. mTLS

    Support mTLS for restful API

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Monitoring Interest  ·  0 comments  ·  Communication  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Add two additional role permission sections for a new folder within a system SmartFolder

    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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Monitoring Interest  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Owner fields in list views

    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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Monitoring Interest  ·  0 comments  ·  User Interface / User Experience  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Implement a Visual Risk Indicator for Records (e.g., Grants and Engagements)

    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 also be retrievable for use in filters, logic, and reports.

    Value Assignment:
    - Risk levels can be set manually by users.
    - Alternatively, the values can be determined automatically based on predefined criteria. For example:

    A custom numeric field (e.g., "Risk Score") could be used.
    If the score is between:
    - 1–25%, set to Green (Low Risk)
    - 26–50%, set to Yellow (Medium Risk)
    - 51–100%, set to Red (High Risk)
    - No value, set to Grey (Unassessed)

    This would help support better risk assessment and decision-making across grant and engagement records.

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

    18 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Monitoring Interest  ·  2 comments  ·  User Interface / User Experience  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Managing removal of uploaded files

    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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Monitoring Interest  ·  0 comments  ·  Administration  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Trigger uta role assignment workflow when updating contacts in batch update

    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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Monitoring Interest  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating