Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

JUMP TO ANOTHER FORUM

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

14 results found

  1. Have the quick navigation menu default to closed/minimized or remember last position.

    I am often finding that I need to constantly close it for ever record that I go into because it is cover or narrowing fields unecessarily.

    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

  2. Currently, if we want to delete a list view, we must open the listview first and then delete it. This process is time-consuming when handling multiple listview. It would be much more efficient if list views list included checkboxes that allow users to select one or more records directly and delete them in bulk.

    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

  3. Create a way for commenters in custom fields using the 'notes entry' feature to be able to edit their comments.

    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

  4. As part of our application process, candidates must provide 3 reference letters. Since we need to ensure the letters are legitimate and undoctored, they must be sent in directly by the reference and not uploaded by the applicant.

    To facilitate this, we currently use the invitation functionality to allow our applicants to send invitations to the reference's email addresses. The references then create an account in SmartSimple and submit a reference form with the letter from within their portal.

    Unfortunately, this adds a significant workload as we need to manage three additional users for every applicant. The bulk of support…

    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

  5. It would make a big difference if we could use GPT 5 or another more recent thinking model as part of our integration.

    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. Some of our fields can have long values. I want to include them in listviews, but the text automatically wraps so that you can see everything. That sometimes makes a single record take up an entire page.

    I'd like the ability to opt out of text wrapping for some columns- completely understand that that means I may not be able to see all the text in the column. Sometimes it's enough to see that it is filled out, or the first few words.

    This would be similar to excel or google sheets, where you can determine how wide each column…

    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. Over time our system has become cluttered with custom fields (for ex. multiple fields called something similar) which makes it difficult for end-users to determine which fields are relevant, unless they have access to configuration mode to identify the ID of the field.

    It could be useful to have the option to mark a field whether it should be reportable or not, minimizing the list of available fields that can be used.

    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

    Thank you for the suggestion—while the idea does have merit, it's not something we plan to pursue at this time. However, within the Report Builder, you can use the custom field search to filter the list of custom fields by caption, field name, or ID, which may help achieve a similar outcome.

  8. We have two different roles doing reviews - external reviewers with the "Reviewer" role, and staff with the "System Administrator" role. Right now the review "Submit" button redirects to the Reviewer Portal accessible to external reviewers, and throws a permission error to the internal reviewer. It would be nice to be able to redirect to the internal reviewer's Staff Home portal and the Pending Reviews listview there from the same submit button. Let's not proliferate too many buttons!

    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

  9. Sys admins can override one another's changes without knowing it simply because each is editing the same field, workflow, or report at the same time. If sys admin saves config, report, or workflow task/connector and it has changed since they accessed it, show merge conflicts so they can resolve

    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. We use custom web page views to perform CRUD operations on L2 records. We also have an HTML grid that shows those L2 records on the L1. There's a platform limitation with this approach.

    Suppose I have three fields on my L1:
    1: Title
    2: WPV (allowing edit access to my L2s)
    3: HTML display of L2s for everyone else who isn't clicking on the WPV and for PDF output

    If user enters title, clicks on WPV, enters L2s, saves L2s wpv, then submits, the HTML display doesn't show the grid (because a save draft didn't occur to refresh that…

    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

    Not Planned  ·  0 comments  ·  Admin →
  11. For modals, users have to click save and then close out of the window. A "Save and Close" button would be nice so that users do not have to worry about closing out of the window after saving. This would also prevent instances of users having the modal open in multiple different windows.

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

  14. We often include the "objemail" variable (copied from an application record) in the To or CC line when we generate an email to a grantee from Outlook. By including the "objemail" variable in the To or CC line, the email will then be attached automatically to the application record. However, the functionality does not work if we include the "objemail" variable in the BCC line. Since the "objemail" variable is a long string of characters, we would find value in using it in the BCC line so that it is hidden from recipients to avoid any confusion on their end.

    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

  • Don't see your idea?