Seon Enterprise job view configuration

From Seon
Revision as of 08:45, 20 February 2015 by Admin (talk | contribs)
Jump to: navigation, search

Seon support a mechanism where Seon Enterprise (send and receive) jobs are visible to others than the person the job is attached to. This includes access to all meta information of the job, the files if available and actions for this job, such as downloading, restart, forwarding, print etc.

This functionality, available since Seon release 2015-02-20, replaces the configuration option for "department for of Seon Webaccess jobs". If this configuration was enabled during update time, the software migration creates an entry for every department so that the department view is restored as configured. The mechanism is new, the end result is the same.

Examples

  • An Seon Enterprise sent by user A is also visible to a specific user B
  • An Seon Enterprise sent by user A is also visible to all members of a specific department C
  • An Seon Enterprise sent by user A is also visible to all members of a specific department D
  • An Seon Enterprise sent by user A is also visible to all members of a specific company E
  • All jobs for department F are visible to a specific person G
  • All jobs for location H are visible to a specific department I
  • ...

Configuration

The partner hierarchy of Seon consists of four levels:

  1. company
  2. location
  3. department
  4. recipient / end user

The configuration of such an allocation is possible at every level of hierarchy, via a button an the buttom of the configuration in the fieldset "Seon Enterprise / Plugin groups". This fieldset is only visible to already created entities, so adding entities to a company actually don't have such a functionality. Edit the entity of desire for configuring the assignment of recipients.

Configuration rules

The same as configuring plugin groups, you can define a limitation at every hierarchical level. The deepest configuration takes place, so above configurations won't be used. Example:

  • Rules configures at location level override rules configured at company level
  • Rules configures at department level override rules configured at company and location level
  • Rules configures at end user level override rules configured at company, location and department level

With this mechanism, you can define rules very exclusively.