Seon Enterprise job view configuration - Revision history

Admin at 13:50, 8 August 2017

2017-08-08T13:50:34Z

2015-02-24T11:24:40Z

‎Selecting entities

2015-02-24T11:24:06Z

‎Configuration

2015-02-24T11:23:18Z

2015-02-24T08:55:04Z

‎Examples

2015-02-24T08:54:53Z

2015-02-20T09:08:02Z

‎Selecting entities

2015-02-20T09:07:17Z

‎Configuration rules

2015-02-20T09:06:34Z

‎Configuration

2015-02-20T09:05:08Z

← Older revision		Revision as of 13:50, 8 August 2017
Line 66:		Line 66:

	After having resetted the configuration, the reset button becomes inactive.		After having resetted the configuration, the reset button becomes inactive.
		+
		+	[[Category:Seon Enterprise]]

@@ Line 35: / Line 35: @@
 === Selecting entities ===
-When configuring rules, you have to selected entities to which the selected entity (i.e. company, location, department or end-user) has access to. This done via a tree selection, which is scrollable and resizable:
+When configuring rules, you have to selected entities to which the selected entity (i.e. company, location, department or end-user) has access to. This is done via a tree selection, which is scrollable and resizable:
 [[Image:Google ChromeScreenSnapz158.png]]

@@ Line 24: / Line 24: @@
 #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 viewable jobs.
+The configuration of such an allocation is possible at every level of hierarchy, via a button at the bottom 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 viewable jobs.
 === Configuration rules ===

@@ Line 4: / Line 4: @@
 == Examples ==
-*An Seon Enterprise sent by user A is also visible to a specific user B
+*An Seon Enterprise job 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 job 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 job 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
+*An Seon Enterprise job 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

@@ Line 15: / Line 15: @@
 *Administrative users can see jobs of all entities.
 *Members of an administrative department can see jobs of specific companies, locations, departments etc.
-*"Project" / "Teamwork" / any kind of collaboration service, so specific users gain access to pseudo-recipients of jobs, addressed as anonymous recipients from external.
+*"Project" / "teamwork" / any kind of collaboration service, so specific users gain access to pseudo-recipients of jobs, addressed as anonymous recipients from external.
 == Configuration ==

@@ Line 27: / Line 27: @@
 *Rules configured at end user level override rules configured at company, location and department level
-With this mechanism, you can define rules very exclusively.
+With this mechanism, you can define rules very precisely.
 === Selecting entities ===

@@ Line 1: / Line 1: @@
 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.
+This functionality, available since Seon release 2015-02-20, replaces the configuration option "department view 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 ==