Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

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

46 results found

  1. Allow to edit the date of a note being entered - or- include date as a field when bulk importing notes via the autoloader.

    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

    Allowing the date and time of a note to be changed introduces tension between data integrity and operational convenience. By design, notes are currently locked to their created date, which represents a system fact rather than user intent. This approach supports auditability, compliance, and overall trustworthiness of the data.

    Enabling users to change note dates could allow timelines to be manipulated and may reduce the validity and reliability of this information. That said, we understand valid scenarios such as bulk migration or backfilling historical data, where preserving the original creation date may be important. For those cases, maybe we could consider setting the created date as part of a controlled import process. Another idea would be adding an effective date within the content of the note.

  2. We would like the ability to have SmartFields pull fields into the summary PDF based on the type of application / program. Having this universal doesn't work when you have many types of applications with various needs.

    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

    SmartFields are designed to display all fields associated with a given application type. Fields that are not part of an application type will not appear in the generated summary PDF for that type.


    If fields are shared across multiple application types but you need more granular control over which fields appear in the PDF for each type, there is a possible workaround. The @SmartFields(customfieldids)@ token can be used to return a subset of fields by specifying a comma‑delimited list of custom field IDs. By creating separate web page views for each application type and generating the PDF from those web page view fields, you can control which fields are included per type.


    We acknowledge that this approach requires additional configuration and ongoing maintenance, and is not ideal.


    While we see the value and utility in having more flexible, type‑specific SmartField behavior for PDF generation, this is not an enhancement we…

  3. I want to decouple the configuration from the data sync. So we can move just our data to a lower environment without having the higher env config impact lower environment

    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

    We understand the request to decouple configuration from data synchronization so that data can be moved to lower environments without affecting existing configuration, and we recognize the value in that approach.


    However, data in the system is closely tied to the configuration and underlying structures it relies on. Supporting data-only synchronization without ensuring those structures align is not something we plan to pursue in the near future. That said, we appreciate the feedback and will keep it in mind as we consider longer-term improvements to environment management.

  4. When an application is created, there is an automatic "New" inserted into the title such as "New Admissibility" "New subvention" and sometimes the title of the form does not make sense because of this "New". Would it be possible to change this title as we wish? Or at least have the "New" Removed ?

    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

    When the New Application or New Anything button is used, the system creates a new record and applies a default title beginning with “New” to indicate that the application is in an initial, unsaved state. This placeholder remains until the user updates the title and saves the record.


    While we understand the concern and agree this is a valid request, the current behavior is intentional and helps ensure clarity and consistency when new records are created.


    At this time, adding the ability to customize or removing the default “New” prefix is not something we are planning to address in the near future, but we appreciate the feedback. Feel free to reach out with clarity if we misunderstood anything.

  5. We propose adding an “Exclude Grant Types” option under Activity Permissions and Availability. Currently, the “Available to Grant Types” field allows administrators to select which grant types an activity applies to, but many of our activities are relevant to nearly all grant types except one or two. Selecting every applicable grant type individually is time-consuming and inefficient given the large number of grant types we manage. An Exclude Grant Types field would allow us to simply select the exceptions, automatically making the activity available to all other grant types. This would save time, reduce administrative effort, and improve accuracy when…

    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

  6. Can you please add status and type IDs to all applicable csv files included in the zip file created by the platform archive feature? For example these are both missing from the applications and activities csv files, both which only include status and type names. Having IDs would be useful for downstream use of the feature.

    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

  7. When applicants paste content from Microsoft Word or scientific journals into Rich Text fields, the editor silently injects hundreds of problematic HTML artifacts — deeply nested <span> tags with inline styles (font-family, font-size, color, border, background), Microsoft Office markup (mso-* properties, <o:p> namespace tags), Word bookmark anchors (<a name="_Hlk...">), and redundant wrapper elements.

    From the applicant's perspective, the content looks fine in the editor. The problems surface downstream: PDF conversions break or produce corrupted output, field rendering becomes inconsistent, and in some cases, the Rich Text field functions themselves stop working properly. The applicant has no way to know their…

    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

  8. Allowing an sslogic statement within another sslogic statement 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

  9. Currently when we select Group Email : for the recipient of the email we can choose a user role or a standard field such as primary contact, staff etc. but for the contacts in CC we do not have the possibility to choose a standard field or user role. I have just sent an email and I would have loved having the possibility to choose the standard field staff as CC of the recipients.

    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

  10. Would love to switch primary dataset in reports after they have been created for simplicity and convenience when tying to wfs / Gort export

    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

  11. Currently the verification email for email address changes has a time limit of 2 hours. This limit is very short for our organizations & staff. There is understanding that this is in place for security. We would prefer to see 24 hours or it be customizable based on an organization's risk tolerance.

    In our environment 2 hours is too short so we end having to go through the process multiple times to send multiple verification emails to the user. Typically, users send an email staff requesting the change. Staff review the request withing their workload and make the update triggering…

    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

  12. Our program area downloads pdfs of all our analyses. On the download files option, the default is set to create a folder for each grant which ends up with a complicated tree structure of folders. There is an option to choose a single folder download to dump all the pdfs together. This is the one we always want.

    It would be nice to either have the single folder as the default setting or at least be able to change the default... Or perhaps make the folder structure a mandatory choice. Anything so that we don't download everything and then have…

    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

  13. Collapsible sections using title bar are no longer a feature in the New Design. Our team finds collapsible content useful and would like to keep it as part of New Design.

    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

    The collapsible title bars were removed to improve clarity, reduce user errors, and create a more predictable form‑filling experience. While they allowed some users to temporarily hide content, they often caused accidental collapsing and led to important information being overlooked. Keeping all sections visible ensures a simpler, more consistent interface where users can confidently see all required data.

  14. Allow binary responses from "Web Service - RESTful Request" workflow tasks to be stored as a single or multiple file upload.

    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

    0 comments  ·  Workflow  ·  Admin →
  15. Occasionally we need to resend grant correspondence to a contact, and it would be a great time and effort saver to be able to do so directly from the listview in the "Emails" tab of our L1 grant records, rather than having to note the contact name/email there, and then go to the Message queue, search in the "Sent" tab, select the precise emails, and resend there.

    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

  16. When a UTA is configured to enable the email activity type, the standard fields “@From Addresssfsffromaddress@” and “@To Addresssfsftoaddress@” that are configurable in list views do not seem to appear in the archive data created by archive feature or the meta data API functions. Can these fields please be added to both the archive feature and the Meta Data SmartConnnect API functions?

    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

    0 comments  ·  Other  ·  Admin →
  17. Let's integrate +AI with SmartCheck Validation; namely the [Source] tab. The idea is that if any validation errors exist, +AI can automatically parse the JS and reformat it, with a suggested update to the syntax available. Basically, integrate a validation-trained +AI Assistant into SmartCheck Validation.

    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

  18. For a scheduled report, there is already an option to "Do not export file when no record is found".
    However, if you have also configured your scheduled report to send an email notification on completion, the email will still be sent in all circumstances, even if there was no exported file because there was no data.
    This issue is particularly noticeable if you have a report that runs daily, but in practice there might only be a few occasions a year where the exported file contains any data. This means there will be possibly hundreds of emails generated each year…

    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

    We recommend a default template that includes the record count. We don't feel a configurable option is the best approach. If you agree, please submit another idea with the ask to provide more details on the results in the email so the user knows the report results. In addition, if you are attending the Unite event, we are having a brainstorming session on how to improve the report builder.

  19. Problem:
    Forms currently do not support embedding custom PDFs in a way that allows users to fill them out directly. This limits the ability to reuse standardized documents and forces teams to recreate PDFs as native forms or rely on external tools.

    Requested Improvement
    Allow custom PDFs to be embedded directly into forms
    Enable PDFs to be fillable within the platform (field mapping, validation, save/submit)
    Support common use cases:
    Regulatory and compliance documents
    Customer-facing forms
    • Internal approval workflows

    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

  20. If we could use Autoloader functionality to build reports within the Report Builder instead of having to build them field-by-field, it would greatly improve our ability to create reports on the fly (and save so much time!).

    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

← Previous 1 3
  • Don't see your idea?