Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

JUMP TO ANOTHER FORUM

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

166 results found

  1. Left menu which are displayed on the Company (organization) portal, should be visible based on the roles. We cannot restrict the visibility of the tab based on the role.

    From the UTA when we enable the setting "Enable Applications list view on Organization Profile - Display List of Applications associated with the Organization under their profile.

    eg. Applications UTA setting
    Internal users should see the Applications listed on the Organizations, but the external School user should not see this tab when they view the organization.
    With the permissions set on the listview we can hide the list from school users…

    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)
  2. 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. It is onerous to build a report to find the common name (front end name, etc) for a eventid that you find in wf history (or otherwise). I'd love to search for level 1, 2, 3 ids in list views to prevent that extra step of building report just to find a field I can search on list view

    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

    Proposed Idea  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. https://wiki.smartsimple.com/wiki/HistoryOf_function

    When using this function, I have to configure with status names. Example from WIKI:

    @HistoryOf(Status::[Value]='Approved'::Update to [Value] by [UpdatedBy] at [UpdatedTime]::[UpdateTime]::desc::1)@

    This is a brittle approach (as this is the caption / front end field name). I'd love the ability to pass the statusid as opposed to status. Even backend field (name) would be better than the caption

    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

    Proposed Idea  ·  0 comments  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Currently, descriptions for uploaded files can be added. It will be helpful to be able to report on each uploaded files, with their description and upload date/time, and user. It will be helpful for staff/reviewers to be able to have a list of files that were uploaded, with the description at hand, as filenames may not be as descriptive.
    Also, since file upload is available thru autoloader, it will nice to be able to add descriptions of files when uploaded thru autoloader.

    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)
  6. Add Deny View Version feature for Dynamic Field Visibility Control field (see attached file).
    Currently we have to remind which DFVC fields we have and if there is a condition in version feature every time we set up a new submission manager version. This is vey annoying because we have a lot of DFVC (more than 100) and we need to check one by one to add the new version.

    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. When you emulate a user, you lose all the tabs you had open on return. Please can user emulation be on a new browser tab or in a new window so when you end user emulation, you return to where you were e.g Support Manager. This would be very helpful when investigating an issue in the Support Manager but you want to test what the users sees before replying.

    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)
  8. At the moment SmartSimple does use Google reCAPTCHA v2 or v3 as a security measure on the system. The use of Google reCAPCTHA however raises privacy issues since Google uses the data (IP adresses, Browser and device, user info, cookies) for own purposes. Google collects more data than is neccessary for the functioning of the reCAPTCHA. The use of Google reCPATCHA v3 raises even more privacy issues since in v3 Google continously analyses online behaviour and users are not aware anymore that their online behaviour is analyzed.

    We would like to have a more privacy friendly reCAPTCHA on the system,…

    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)
  9. The current permissions tab for creating a new folder within a system folder is limited to View Folder and Modify Folder permissions.

    Add the "Upload and Move Files" and "Create Sub-Folder" sections under the Role Permissions settings as well.

    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)
  10. For each formula, we need to configure in formula syntax the statuses that the formula shouldn't run on. It would be incredibly valuable to have end-state statuses control the formula access.

    Save draft (on record or triggered through batch update) will trigger formulas inadvertently on end-state statuses like "Approved", "Complete", "Finalized", "Closed", "Paid" unless configured onto each formula

    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)
  11. Add field level configuration to allow disabling of annotations so read-only and display fields aren't annotated inadvertently

    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)
  12. Platform solution to support bulk CRUD updates to L1, L2, and L3 assignments and roles.

    We build a report and workflow(s) for each CRUD operation we have to perform in bulk. It's a rather tedious exercise and requires someone with config experience to support

    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)
  13. To quickly compare field differences between two versions of fields in a UTA for a specific level (L1 or L2): Be able to generate a list/report/printout that lists only the fields where there is difference between the two versions. Bonus if it includes what the difference is. This would be kind of like the "Diff" button on custom fields, but it would provide a list only of the fields where there is a difference.

    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)
  14. For 'Upload - Multiple Files Storage' where Disable Delete is toggled on, allow System Admin to delete/remove uploaded files (incorrectly uploaded by user) without needing to toggle off Disable Delete across all users.

    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)
  15. To improve customer service, on the note function to and from applicants, please carry the project reference number for efficiency and improved communication.

    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)
  16. It would be helpful for the Auto Archive feature to be configured per status that triggers it, so that there is more granular control over how records get archived.

    For example, despite multiple statuses being able to trigger the archival process, if they must be unarchived, they all get the same status.

    Additionally, it would be helpful to also be able to define when the auto archival process happens. For example, perhaps after a day, week, or month. Being able to define that per status add more flexibility.

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

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

    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. The font and text size used in the system-generated email with the subject “Confirm Your New Email Address” are not consistent with the formatting used in other system-generated emails. A fix related to this issue is scheduled for the February release as part of the ticket referenced below.

    Given this, could we introduce a configuration control for this email template—similar to what is currently available for password-reset and new-user emails? Having this control would allow us to adjust the text and font formatting as needed to meet branding or client requirements.

    Please refer to SmartSimple ticket #275411 for additional details.

    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)
  20. Display all data fields on Chart key. Right now, the Chart only displays 8 fields and you need to scroll to see additional fields. When you download the chart, only some of the fields are displayed.

    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)
← Previous 1 3 4 5 8 9
  • Don't see your idea?