4 results found

1. Map Cycle onto L1 Record without manually creating a Custom Field to Display it

   We need to be able to automatically map the Cycle Name from the Program Manager onto the L1 Record in a way that we can sort by, filter by, and search by the Cycle in the Submission Manager. Currently, to do this, we have to create a Single Line Text Custom Field, map the Cycle Name contents into it through a Template Formula on the L1 settings, and use Deny Modify: Everyone settings with detailed documentation to support the usage.

   (This is a request from multiple clients/SmartSimple System Admin teams.)

   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

   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. Annotation Mode - Button Captions (Reply / Message)

   When Annotations were overhauled a couple of years ago, we were told that we could not change the Button Captions. Specifically the button that reads "Reply," for our external users does not make any sense in our SmartSimple instance.

   We have had numerous applicants that have had difficulty figuring out how to make the changes we've requested at every deadline since this update was implemented, as users want to make the update, not send a message. The button caption being "Reply" is not intuitive at all. Even if it was "Update," or something similar that captures the actual function of the button would be so much clearer for our applicants and users.

   Also, the Message text field is mandatory for them to fill in, but usually there isn't a lot for them to say if the request is clear. It also implies (to our external users) that someone is notified when the Message is Saved/Sent and that isn't the case. So they may have questions or have put in other information as a reply to the annotation but isn't monitored. In our case, it doesn't function as a messaging system in any way that's helpful.

   When Annotations were overhauled a couple of years ago, we were told that we could not change the Button Captions. Specifically the button that reads "Reply," for our external users does not make any sense in our SmartSimple instance.

   We have had numerous applicants that have had difficulty figuring out how to make the changes we've requested at every deadline since this update was implemented, as users want to make the update, not send a message. The button caption being "Reply" is not intuitive at all. Even if it was "Update," or something similar that captures the actual function 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

   Proposed Idea  ·  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

3. New AI Analysis Compare Question X on the Level 1 (grant) with Question Y on the Level 2 (report)

   For the new AI Analysis Tool, can we ask it to run Level 2 analysis based on Level 1 objectives and deliverables? For example, compare Question X on Level 1 (grant) with Questions Y, Z, etc. on Level 2 (report) and tell us whether the grantee has met their deliverables over the course of 4 quarters? The returning answer could be valuable as yes/no, but it will need to give us details about the evidence behind its selection.

   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  ·  Edit…  ·  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. Media Library - Sub-Fields

   We had been using Sub-Fields to add / edit Properties of material uploaded into the Media Library, and these fields are available to the applicant to enter using the "Edit Properties" button. These fields are commonly missed as there is no true way to make it mandatory. As such, we frequently would annotate the field and send it back to the applicant for them to complete.

   After the June 2026 release, the applicant is no longer able to Edit Properties under the "Revision" application status, as they had previously, they can only edit these fields under the "Draft" application status, which is problematic as we do not want to re-open the entire application following the deadline.

   We would like to see this fixed as we have now been using this function for years. Or, ideally, there would be a way to add fillable fields that 1. we can enforce it being mandatory and 2. can be added to a specific file that is uploaded into the media library in a more intuitive way.

   I understand that there is the annotation feature and we can add different annotation types that may help with this, however, that type of function change takes years to "train" our users and isn't super intuitive.

   Use case e.g. a photo or video is uploaded to the media library and the Sub-Fields or Properties, can enter text for a Title and a Description in these Sub-Fields.

   It added direct context and was helpful for the external reviewer to better understand what the applicant was providing for their Supporting Material and how it was related to the applicant's application or project that was being assessed.

   (Also, can you make this specific text field [where we post our idea] expandable?)

   We had been using Sub-Fields to add / edit Properties of material uploaded into the Media Library, and these fields are available to the applicant to enter using the "Edit Properties" button. These fields are commonly missed as there is no true way to make it mandatory. As such, we frequently would annotate the field and send it back to the applicant for them to complete.

   After the June 2026 release, the applicant is no longer able to Edit Properties under the "Revision" application status, as they had previously, they can only edit these fields under the "Draft" application status,… 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