View source for Seon Enterprise job view configuration

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 J
*...

== Configuration ==
The partner hierarchy of Seon consists of four levels:
#company
#location
#department
#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 configured at location level override rules configured at company level
*Rules configured at department level override rules configured at company and location level
*Rules configured at end user level override rules configured at company, location and department level

With this mechanism, you can define rules very exclusively.

=== Selecting entities ===
When configuring rules, you have to selected entities in which an allowed recipient must be placed in. This done via a tree selection, which is scrollable and resizable:

[[Image:Google ChromeScreenSnapz158.png]]

If only active entities are requested, press the button "Only show active entries":

[[Image:Google ChromeScreenSnapz159.png]]

Some rules for enabling entities:
*When enabled an entity, the above entities will be deselected (since a "deeper" selection overrides the above one). This deselection is made automatically for you.
*When an entity is moved to a new location, it saves its selected state. Example: If a department is activated, and later-on moved to another location or another partner, the selected department will still be active in selection, even in the new location.
*When clicking on the button "Only show active entries", this action implies that the actual selection will be saved before a re-displaying takes place.