135 results found

1. Fix the Advanced Search feature

   Fix the Advanced Search feature with the following improvements:
   - open the search in a modal window so we can see all the criteria in the search
   - provide functionality to change the order of criteria
   - Include previously used queries dropdown (either customizable or most recent X queries)
   - return the closing parenthesis
   - add a "power user" option for people to include their own SQL queries

   9 votes

   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

   1 comment  ·  Reporting and Analytics  ·  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

   Good usability suggestions, the only item not under consideration is the last one with the ability to leverage a user's SQL

2. Improvement to the API services

   The current API services offered by SmartSimple are confusing in the response our team receives when calling them. For example:
   - If there are missing variables in the call, it will respond a 200 - OK in almost all circumtances.
   - If there is an incorrect variable (for example, report instead of reportid), the API will reply a 401 error in the body of the response - which indicates the user does not have authorization to that report, when the error is that the variable was incorrectly parsed in the URL.

   As our system becomes more connected with other platforms, these issues are becoming a problem with the suppliers that need to connect to SmartSimple.

   The current API services offered by SmartSimple are confusing in the response our team receives when calling them. For example:
   - If there are missing variables in the call, it will respond a 200 - OK in almost all circumtances.
   - If there is an incorrect variable (for example, report instead of reportid), the API will reply a 401 error in the body of the response - which indicates the user does not have authorization to that report, when the error is that the variable was incorrectly parsed in the URL.

   As our system becomes more connected with other platforms,… more

   8 votes

   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  ·  Reporting and Analytics  ·  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. 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

   •  

   12 votes

   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

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

   14 votes

   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

5. Rich Text Editor - Resizable Window

   With the Smart Simple October 2025 Update to the Rich Text Editor, the window is no longer resizable.

   The specific field type for the Rich Text Editor is: Special - Rich Text. It would be ideal if the window has the ability to be resized both vertically and horizontally.

   An example of text windows that are fully adjustable are those with the "Text Box - Text Multiple Lines" field type, and the Width is set to "Full" under the display options (Width), allows for both horizontal and vertical adjustment

   6 votes

   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

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

   15 votes

   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

7. Enhancements to the T2P Tool

   After our first experience with the new T2P tool, we would like to suggest the implementation of the following enhancements:

   1. Pagination in "Changes Logged Against This Project"

   The current page to view, select and manage the changes lacks pagination. This makes navigating large sets of changes difficult, especially when we need to manually select or unselect hundreds of changes.

   Pagination would significantly improve usability and efficiency.

   1. Promoted indicator should be tied to ENVIRONMENT

   We have noted several that the current behaviour is not ideal. The main suggestions would be:
   --> The Promoted field should reflect the status of that change in regards to the environment to which could be exported. If a T2P project can promote changes to TEST and LIVE, for example, the field should reflect whether the specific change has been promoted to the environment to which the export would be made to.
   --> Though not consistent, we have seen that the Promoted field will reset between sessions - therefore, we are unsure of whether a change has been promoted already -. For now, our workaround is to export all changes linked to the project every time, but it is inefficient.

   1. Filters for visible columns

   We would like to be able to filter the changes by Exported and User fields at least... Though ideally we should be able to filter with any of the fields offered.
   Also, we would like to have the option to apply advanced filters, as we can do in listviews.

   This would help manage large change sets more easily.

   1. UI improvement: move the delete (trash) icon

   Currently the button is placed on the left, close to the "Select all" checkbox. Though unlikely, this could lead to someone deleting changes.
   The suggestion is to move this to the right, where there are no user-interactive elements to work with (right now, if we added filters as mentioned in the previous suggestion, it wouldn't so necessary :D).

   1. Include UTA version activation as a logged project change

   We changed the Version in which new Applications would be created in our Submission Manager. However, the change did not appear in the list of changes to apply in the T2P tool. This means this change needs to be done manually for every environment - which is not ideal -.

   After our first experience with the new T2P tool, we would like to suggest the implementation of the following enhancements:

   1. Pagination in "Changes Logged Against This Project"

   The current page to view, select and manage the changes lacks pagination. This makes navigating large sets of changes difficult, especially when we need to manually select or unselect hundreds of changes.

   Pagination would significantly improve usability and efficiency.

   1. Promoted indicator should be tied to ENVIRONMENT

   We have noted several that the current behaviour is not ideal. The main suggestions would be:
   --> The Promoted field should reflect the status of that change… more

   5 votes

   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  ·  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
   Under Consideration  ·  AdminMark Bridger (Product Owner, Foundant Technologies) responded

   We plan to review pagination, search, and filtering capabilities within the T2P tool. If versioning is not being promoted, it should be reported as a defect to support.

8. Red Lining/Track Changes

   Need the system to track field level changes for red lines, similar to Word.

   10 votes

   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

   Feedback Needed  ·  2 comments  ·  Documentation  ·  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. Allow users to copy a system list view without needing edit access

   I would like to be able to give users the ability to copy an existing system listview and save it as a personal listview.

   Currently, a system list view can only be copied if a user has EDIT access to it. This access is only granted if you are a UTA Admin or a Global Admin.

   My users are not system admins or UTA admins for Grant Manager, so they do not have the ability to EDIT or copy a system list view.

   So, I would like users to be allowed to copy a system list view without needing edit access.

   I would like to be able to give users the ability to copy an existing system listview and save it as a personal listview.

   Currently, a system list view can only be copied if a user has EDIT access to it. This access is only granted if you are a UTA Admin or a Global Admin.

   My users are not system admins or UTA admins for Grant Manager, so they do not have the ability to EDIT or copy a system list view.

   So, I would like users to be allowed to copy a system list view without needing edit… more

   5 votes

   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

10. Versioning

    Currently, SmartVersioning does not allow you to copy versions you create. You can only create new versions that pull in the base core fields.

    This makes it very difficult to iterate on yearly application form changes.

    The best practice from SmartSimple is to make changes at the Core Field level until it matches what you want, then save those changes as a version. However, this makes it very difficult to manage versions in practice.

    For instance, my foundation has three Level 1 Grant Types and every year we make revisions to the application forms. Last year I created Scholarship Application 2024, but because the application period is very busy we occasionally had to make corrections quickly and it takes much more time to change a record to the Core Fields version, make the change, then push that field forward to the correct version, and change the record back.

    Some changes inevitably ended up just being made in the current version itself and this year for the 2025 version we had to manually ensure all the core fields matched the current version before we could start iterating for this year.

    If we could have simply copied the Scholarship 2024 Version as the 2025 version and made the changes directly within it, it would have saved hours of time.

    Allowing copying of versions would also simplify building across our three grant types.

    Because you can remove fields that are not in use in particular versions, we could have 3 versions that only include the relevant fields for that grant type, reducing confusion and making it a much easier to manager process. This goes double at Level 2 where we have over 10 disparate activities and it can be confusing to know what fields are relevant. Yes, this can be managed with careful planning and numbering on the forms, but with some fields overlapping it is still difficult.

    This would simply require two changes. The ability to copy a version, and an addition that allows you to create new fields within a version that automatically save as core fields and also prompt you on what other versions they should be pushed to (rather than having to switch to the core fields, create the field, then push it to the relevant version(s).

    Currently, SmartVersioning does not allow you to copy versions you create. You can only create new versions that pull in the base core fields.

    This makes it very difficult to iterate on yearly application form changes.

    The best practice from SmartSimple is to make changes at the Core Field level until it matches what you want, then save those changes as a version. However, this makes it very difficult to manage versions in practice.

    For instance, my foundation has three Level 1 Grant Types and every year we make revisions to the application forms. Last year I created Scholarship Application… more

    8 votes

    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

11. Ability to Hide/Sort/Freeze columns in the Assignment Grid (Reviewer Assignment Grid)

    When using the Assignment Grid—specifically the Reviewer Assignment Grid—it would be helpful to have features similar to Excel, such as the ability to hide columns or freeze panes. This would make it easier to scroll horizontally on smaller screens without losing track of which application you're viewing. It would also be useful to have the option to sort by specific columns, such as Application ID#.

    •  

    12 votes

    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

12. List Display : freeze the first row

    Improve Lists display by adding the possibility to freeze the first row of column titles
    Such as in Excel : add the prossibility to freze the first row of a list to keep the right column title on top when we scroll down

    5 votes

    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  ·  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
    Under Consideration  ·  AdminJohn Fulton (Director of Product Management, SmartSimple, Foundant Technologies) responded

    We are looking at a number of user experience improvements with list views and will include this idea too

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

    8 votes

    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

14. Enhance Auto Assignment Feature

    It would be nice to be able to use the auto assignment feature as follows instead of having to use workflows and enable this to be used with the contacts tab instead of assigned sf:

    1) When a new user is added in a particular role to the contacts tab of an L1, automatically assign them to the L2s in the contacts tab as a particular role
    2) When a new L2 is created and users from the L1 are set to auto assign to the L2, the assignment is passed upon activity creation
    3) When a user is removed from an L1 in a particular role, automatically remove them from all L2s in the contacts tab as that particular role (unless they should still remain there from another auto assignment role definition

    On a similar strand, if users are assigned in a record on a provider UTA, there should also be auto assignment features that are configurable in the same way to the consumer UTA records (new record, addition of new user, deletion of user)

    It would be nice to be able to use the auto assignment feature as follows instead of having to use workflows and enable this to be used with the contacts tab instead of assigned sf:

    1) When a new user is added in a particular role to the contacts tab of an L1, automatically assign them to the L2s in the contacts tab as a particular role
    2) When a new L2 is created and users from the L1 are set to auto assign to the L2, the assignment is passed upon activity creation
    3) When a user is removed… more

    5 votes

    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

    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
    Monitoring Interest  ·  AdminJohn Fulton (Director of Product Management, SmartSimple, Foundant Technologies) responded

    There are multiple parts to this idea. One is that we will ensure the auto-assignment works for single users, this ticket will represent the request to support multiple contacts. We may also consider supporting deletions, but that will be after we deliver this first step of supporting multiple contacts.

15. Export custom field list with visibility permission settings

    The ability to export the custom field list from L1, L2 or L3, users, orgs or any system object, with settings such as mandatory toggle, description, select values, and including the role, status, and type permission settings, into Excel, or the ability to build a report builder report where you can customize the settings to be exported. The system design summary pulls some of this data into a word table format, which can be copied into Excel, but it is cumbersome and only copies from the core fieldset. Being able to export directly and easily from the custom field list in Excel format, AND include the visibility permissions, would be ideal for system documentation purposes. We are currently maintaining a separate Excel spreadsheet that has to be manually updated when changes are made to field configurations.

    The ability to export the custom field list from L1, L2 or L3, users, orgs or any system object, with settings such as mandatory toggle, description, select values, and including the role, status, and type permission settings, into Excel, or the ability to build a report builder report where you can customize the settings to be exported. The system design summary pulls some of this data into a word table format, which can be copied into Excel, but it is cumbersome and only copies from the core fieldset. Being able to export directly and easily from the custom field list… more

    5 votes

    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  ·  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
    Monitoring Interest  ·  AdminJohn Fulton (Director of Product Management, SmartSimple, Foundant Technologies) responded

    We see the value and need to provide a way for customers to have a documented view of their system. We will monitor to see how much others are interested.

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

    •  

    6 votes

    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

17. Ability to change information in the invitation window on an application once an invited person has accepted

    Once a person has been invited to an application and has accepted the invitation, it would be helpful if system administrators had the ability to edit information in the invitation window—such as correcting the spelling of a name or email address. It's common for the person sending the invitation to make small mistakes, and they often reach out to us for corrections after the invitee has accepted. Currently, the only way to fix these errors is to delete the invitation and re-invite the person, which is inefficient.

    •  

    10 votes

    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

    Feedback Needed  ·  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

18. Bottom scroll bar

    On the L2 view within the L1, there are two scroll bars on the right and then a bottom scroll bar below all the L2s. if there are many L2s on the list, one would have to scroll all the way down to move the scroll bar to the right. It would be nice to have the bottom scroll bar be static on the page.

    4 votes

    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

    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
    Under Consideration  ·  AdminJohn Fulton (Director of Product Management, SmartSimple, Foundant Technologies) responded

    We agree this should be considered. We will look at this in an upcoming release.

19. Preview Subject in Communication Center

    When preparing an email in the Communication Center, the "Preview" button previews only the body, not the subject. It would be great to include the subject in the preview as it contains often variables or sslogic statements

    8 votes

    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

    Planned  ·  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

20. Permission Quick Edit: Security Matrix checkboxes for Fields

    It would be really helpful to have the option in the various Security Matrix sections to toggle all the checkboxes on or off across for a particular field, not just down for a Role or Status.

    And as we can do with the 3 dots in the header row to "Copy Row Settings", I'd like to be able to "Copy Field Settings".

    Use Case: I have a similar update I'd like to make to a large number of new fields to remove all the current permissions and replace with updated permissions and need to go through each field and each Status and Role manually. Would be so helpful to just be able to "select all" and delete everything back to a blank slate, and then copy/paste the settings we've updated for a related field.

    It would be really helpful to have the option in the various Security Matrix sections to toggle all the checkboxes on or off across for a particular field, not just down for a Role or Status.

    And as we can do with the 3 dots in the header row to "Copy Row Settings", I'd like to be able to "Copy Field Settings".

    Use Case: I have a similar update I'd like to make to a large number of new fields to remove all the current permissions and replace with updated permissions and need to go through each field and each… more

    7 votes

    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

    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
    Monitoring Interest  ·  AdminJohn Fulton (Director of Product Management, SmartSimple, Foundant Technologies) responded

    We will monitor interest for future consideration.