Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

JUMP TO ANOTHER FORUM

(thinking…)

How can we improve SmartSimple? Search and Submit your ideas below.

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

4 results found

  1. Role based left menu visibility on Organization portal

    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…

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Proposed Idea  ·  0 comments  ·  User Interface / User Experience  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Update historyof function - FIELDNAME is brittle

    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)
    Close
    Close

    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)
    Close
    Close

  3. Add a new search feature to the “All Columns” dropdown in List View to help users quickly find and select columns without scrolling through

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Proposed Idea  ·  0 comments  ·  User Interface / User Experience  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. add level 1 id , level 2 id, and level 3 ids to list views / search criteria

    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)
    Close
    Close

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