Managent menu > Group

This menu is used in conjunction with the Group Management window. See Admintool. If some of the buttons are grayed out, it means that you need to select a group in the Group Management window.

Groups Properties

When we create or modify a group, we have access to all its properties:

Global

Name

Name of the group, knowing that the default group cannot be renamed.

User type

there are 2 possible types of users.

  • Vigilens Viewer / Web: only consultation of existing queries
  • Vigilens Designer: possibility to create new queries.

The available types depend on the license.

Windows connexion

Allows to launch Vigilens without the login window being displayed, if the Windows user name corresponds to the Vigilens user name.

Setup for emailing

You can also assign a different mail server and/or a different sender name for this group than the default server.

The mail server can be set at the user level, in which case it takes precedence over what is set at the group level.

Specifying mail settings at the user level allows you to have a personalized return address.

Unchecking one or both checkboxes opens the entry to the parameters specific to this group.

Rights restrictions

This is where you define which Vigilens applications a group can access. You can see that for each right, there is a contextual help in the top right corner.

If one of these boxes is checked at the group level, it will also be checked at the group user level and will not be uncheckable.

Restriction

  • Import only shared data source
    • Disable use of data source that has not been shared by administrator : User cannot create or modify data source.
  • Disable queries publishing
    • User cannot publish queries he created.
  • Restricted rights in query modification
    • User is not able to modify datasource, tables and joinsin existing queries.\nUser is not able to create new queries. He is only able to change data selection, extracted fields and output.

Autorization

  • Unable changes to shared queries folder
    • Unable user to make changes within the shared queries folder : add, change or delete folders or queries.
  • Enable use of data dictionay decimals instead of currency ones even if JD Edwards database is in multi currency mode
    • Enable user to choose data dictionary setup for amount decimals instead of currency setup (and so to avoid to manage data related to amount fieds).
  • Enable deletion of all result files.
    • User has the rigt to delete result files from other users.
  • Authorize creation of user defined standard join that can be used by creator only
    • Authorize creation of user defined standard join that can be used by other users
  • Authorize creation of user defined standard currency relationship that can be used by creator only
    • Authorize creation of user defined standard currency relationship that can be used by other users
  • Enable build of query type 'SQL Entry'
    • Enable user to build query type 'SQL Entry'.

Output

  • Disable data export
    • User cannot export data from its queries.
  • Authorize the output to user named files
    • Authorize user to set path and file name for results output.
  • Disable printer output
    • User cannot extract data to printer.
  • Disable email output
    • User cannot extract data to email.
  • Enable export to a database
    • Enable use of query type ““Export to database”” which allows user to insert query results as records in a table of a selected database
  • Enable table creation when exporting to a database
    • Enable user to create a target table when using export to database
  • Enable table purge when exporting to a database
    • Enable user to request purge of target table before insert when using export to database.

Access to applications

  • Authorize the use of OPManage
    • Authorize user to run OPManage in order to create, change or delete user functions.\nRemark : This application does not allow changes to standard functions.
  • Authorize the use of DMManage
    • Authorize the use of DMManage in order to rename tables and fields.
  • Authorize the use of LogManage
    • Authorize user to run LogManage in order to manage logged users.
  • Enable use of application Vigilens Monitor“!
    • Enable user to run application Vigilens Monitor which allows creation of web pages that includes scheduled Vigilens queries.
  • Enable use for application WebConfig
    • Enable user to run application WebConfig in order to manage setup for Vigilens Web.
  • Disable interactive use of Vigilens
    • Disable interactive use of Vigilens.\nThis user can be used only for connection through command line or URL.

Miscellaneous

  • Display only the header in the query summary
    • Enable the display of data source and query description in the summary instead of all the query sections

Time Out

There are 2 times out:

  • the first one is purely relative to the database: it is the maximum time between the submission by Vigilens of the request to the SQL server and the end of the execution. This time out is managed by the database itself.
  • the second one is managed by Vigilens: compared to the first one, it also takes into account the data extraction time.

These notions of time-out can be defined at different levels:

  • group
  • user
  • query

These times must necessarily be smaller and smaller when switching from group to user and then user to query.

Because SQL time out is managed at the database system level, it is not available on all platforms.

Data access restriction

It may be useful to block certain groups from accessing certain sensitive company information. It is possible to prohibit the use of a data source by unchecking it in the list. For each datasource, Vigilens can impose restrictions on :

  • Environments
  • Tables (for JDE/World type sources)
  • Aliases (for JDE/World sources)
  • Fields
  • Values

The button Default restrictions… gives you access to settings that are valid for all data sources that do not have specific settings. The sequence of the screens is similar in every way to the settings for a particular data source.

Generally speaking, all of the following restrictions work on either as black list or white list system: either you make explicit which items are prohibited and everything else is allowed, or you make explicit which items are allowed and everything else is prohibited. Black list/White list operation is defined at group level and cannot be changed at user level.

you can:

  • prevent/allow access to environments, for JDE/World data sources

  • prevent/allow consultation of a particular table

  • prevent/allow access to an alias (JDE/World)

  • prevent/allow access to define table column

  • prevent/allow the display of certain table rows according to criteria on a table column. The criterion can be a single value, a range of values, or a list of values.

If the data source is JDE/World, we have in addition the choice to use the JDE security associated with a user and one of his roles (or all roles with the value “*ALL”).

Shared Queries

This setting allows you to :

  • Define the place(s) where the user can deposit the queries he wants to share. The user has access to the entire tree structure of the specified directories.
  • Define the shared queries it can use

  • Publish queries: list of shared folders accessible when publishing queries
    • Default folder: proposed by default when publishing queries
  • Use of shared queries: list of shared folders accessible via the web interface

Change Language

Allows you to change the languages (of the interface and of the descriptions coming from the database) of all the users present in the group.