Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

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

245 results found

  1. Allow to pass a javascript variable to a ReportProperty syntax.
    It will be very useful in a SmartCheckValidation.
    Example (in SCV):
    var sID;
    var sResults = @ReportProperty(1234,exportdata,,sID)@;

    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)
  2. Would be really useful to be able to report on whether or not annotations are resolved, as then you could use the report property to create SmartCheck validations and/or have fields display conditionally based on if there are any unresolved annotations or not.

    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)
  3. UX on list view differs from profile. From list view, the next/last page sticks to top of page as you scroll. On dashboard, it doesn't and when you scroll down through results you lose the next/back buttons.

    Would be good to have similar functionality on "My Profile" that exists for 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)
  4. (Re ticket #277463 - Tracking processing times)

    We have been asked to report on the length of time in review for monitoring the workload and efficacy of our staff.

    We have created a status duration report but it will not calculate the length of time in the current grant status. Yet, when we click on the status history for an individual file, it lists the length of time in each grant status including the current status.

    We basically want the numbers listed on the graph in the individual status history but in a table with all the other files.

    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. We would like to propose a feature that enables bulk (batch) translation of applicant-entered content in custom fields using SmartSimple’s existing in-tool translation functionality. Currently, translations must be performed manually field by field by clicking the translation button, selecting a target language, and choosing the destination field for storing the translated content. We are not referring to translating field captions/labels, but rather the actual responses submitted by applicants.

    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)

    It sounds like you are currently using the Enable Field Translation Service to translate applicant‑entered content and store the translated text in separate custom fields by manually clicking the Translate button on each field.


    If your goal is to translate multiple applicant‑entered fields in a single action, you may want to consider using a workflow with the task type Translate Field Values. This approach may allow you to execute the translations in batch. You could then expose this workflow through a single button on the application form, enabling on‑demand translation of all relevant fields without needing to translate each field individually.


    While this is not a native bulk‑translate action within the SmartField interface itself, it might effectively achieve the desired outcome with less manual effort. I suggest escalating to Support if you’d like assistance with configuring the workflow or validating the setup.


    If you are still interested in a native…

  6. There are clients who leverage the word merge field to consolidate data across multiple L2s (often grant reports) under a grant application and map it to a word template. The configuration for this is very syntax heavy and leverages a lot of list syntax and/or report property syntax.

    The amount of effort to support clients with this functionality often warrants an RFS. It would be nice to have a UI for selecting the L2s and the fields to be included in the word template. Some HTML work will still be required but perhaps we can eliminate the need for list…

    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)
  7. The old Rich Text Editor had the option to add headers to text without using tags. It would be ideal if this functionality could be added back into the new Rich Text Editor. This would save our users a lot of time.

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

    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)
  9. We need to use the Group Email functionality on the Program Manager > Cycle level to easily communicate with grantees within a certain cycle.

    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)
  10. While I love the new upgraded reminder function on emails, the limited selection of reminders is frustrating. There are a lot of choices for reminders on upcoming tasks but only 1 Day After and 3 Days After for a choice on overdue email reminders. It would be really nice if we could also set up a wider selection of Overdue email reminders.

    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)
  11. Currently if columns in an XML should be updated in say a progress report, but rows shouldn't be able to be deleted or added, the +/- buttons on the dynamic section have to be hidden with custom script. Instead it would be great if there was a setting on each dynamic section to hide the +/- buttons based on status and/or role - perhaps a visibility condition like we have for edit conditions on the column? This would make initial configuration and ongoing changes easier.

    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. 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)
  13. 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)
  14. 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)
  15. 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)
  16. 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)
  17. 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.

    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. 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)
  19. 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)
  20. We have a multi-upload field with media library enabled. That field can only accept images and videos, not documents. Please allow us the ability to accept more file types, including documents, to fields of this type.

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