Helical Insight

A Business Intelligence Framework
  • Differentiators
    • BI Framework
    • Canned Report
    • API Support
    • Workflow
    • Instant BI
  • Learn
    • Documentation Guide
    • Tutorial Videos
  • Demos
    • Industry specific demo
    • Job functions specific demo
    • Miscellaneous Use Cases
  • Clients
  • Forum
  • Contact Us
  • Free Download
Introducing World's First
Business Intelligence (BI)
Framework
Read more
Helical Insight Community Edition
Open Source
Github
Open Source With Lowest
Total Cost Of Ownership
And High ROI
Make Quick Informed
Decisions From Your
Complex Multiple
Data Sources
Various Data Visualization Options Like Reports, Dashboard, Geographical
Analytics, Statistical & Scientific Charts etc.

Session Variable usage in Query View

This blog describes the various attributes of the session variables that can be used in the view of the metadata of Helical Insight.

There are four session variables in Helical Insight: user, org, profile and role. The various attributes for each of these are as follows:

  1. user: These are attributes related to the users that are created.
    1. ${user}.id – This is the user id of the logged in user. This is an integer value.
    2. ${user}.enabled – This returns Boolean value. It is true when user is enabled and false when user is disabled
    3. ${user}.name – This returns the user name of the logged in user in string format.
    4. ${user}.isExternalUser – This Boolean value is true when SSO is implemented and indicates that the user is created using SSO externally and not from the Helical Insight application itself.
  2. org:
    1. ${org}.id – It is the ID of the organisation. Returns integer value
    2. ${org}.name – It returns the organisation name in String format
  3. profile:
    1. ${profile}.name – Name of the profile in String format
    2. ${profile}.id – Profile ID in integer format. It is taken in order of creation of profile
    3. ${profile}.value – Value of the profile that is there. This is in String format. There can be multiple values and hence sent in array.
  4. role:
    1. ${role}.id – Role ID in integer format
    2. ${role}.name – Name of the role in String format

    A user can have multiple roles and profiles. Hence, the attributes are in array format and query is to be used for selection from an array with IN keyword.

    Example:

    Select * from meeting_details where location in (${profile[1]}.value)
    

    Here, profile[1] indicates the second profile, i.e. , location.

For more information you can email on support@helicalinsight.com

Share with

  • Facebook
  • Twitter
  • LinkedIn
Creating Canned Report with Cascading Input Parameters
Migrate Helical Insight To Version 4.0 From Older Version

Written by Shailaja Ramchander

Shailaja

Related Posts

  • Custom VF to implement a Select2 component with Infinite scroll
  • Inter-Panel Communication on Charts
  • Migrate Helical Insight To Version 4.0 From Older Version
  • Dynamic Query View in Metadata
  • Home
  • Career
  • Downloads
  • Blog
  • Enterprise Edition
  • Community Edition
  • Learn
  • Video Guides
  • Documentation
  • Press Release

Demos

  • Industry specific demo
  • Job functions specific demo
  • Miscellaneous Use Cases
  • Partners
  • Channel Partners
  • Solution Partners
  • OEM Partners
  • Facebook
  • Twitter
  • Youtube
  • LinkedIn

WordPress Lightbox

Contact Us

✓ Valid Invalid number

Register

✓ Valid Invalid number
Refresh