Seon plugin groups - Revision history

Admin at 13:51, 8 August 2017

2017-08-08T13:51:09Z

Admin: /* Incoming jobs when a recipient is known */

2012-08-24T06:33:20Z

‎Incoming jobs when a recipient is known

Admin: /* plugin group management */

2012-05-26T01:02:58Z

‎plugin group management

Admin: /* plugin group management */

2012-05-26T01:02:34Z

‎plugin group management

Admin: /* plugin group management */

2012-05-26T01:02:11Z

‎plugin group management

Admin: /* plugin group management */

2012-05-26T01:01:46Z

‎plugin group management

Admin: /* plugin group management */

2012-05-26T01:01:17Z

‎plugin group management

Admin at 01:00, 26 May 2012

2012-05-26T01:00:49Z

Admin: /* Plugin group usage */

2008-06-15T19:52:43Z

‎Plugin group usage

Admin at 19:46, 15 June 2008

2008-06-15T19:46:25Z

← Older revision		Revision as of 13:51, 8 August 2017
Line 79:		Line 79:

	By submitting the form, the plugin group will be deleted and all affected entities will receive a "no plugin group defined" configuration.		By submitting the form, the plugin group will be deleted and all affected entities will receive a "no plugin group defined" configuration.
		+
		+	[[Category:Seon Enterprise]]

@@ Line 24: / Line 24: @@
 *if not found: search for a receive plugin group at the configured defined recipient company
 If no receive plugin group is defined in any of these hierarchy levels, the job gets the status "''aborted''" and a log entry is added to the job (complaining about a non-configured receive plugin group for that recipient).
 The first found plugin group with its configuration (if any is set) is used for that incoming job. It's processed from the first to the last plugin of that plugin group.

← Older revision		Revision as of 01:02, 26 May 2012
Line 67:		Line 67:
	By submitting a new name, the existing plugin group will be cloned to the new name.		By submitting a new name, the existing plugin group will be cloned to the new name.

		+	==== deleting plugin group ====
		+	In order to delete a plugin group, click on the delete icon on the left side of the appropriate row: [[Image:delete.png]]

−	[[~~deleting~~ plugin group]]	+	If the plugin group is configured in any partner entity (company, location, department or recipient) or basic configuration, these entities will be displayed here:
		+
		+	[[Image:Delete plugin group.png]]
		+
		+	By submitting the form, the plugin group will be deleted and all affected entities will receive a "no plugin group defined" configuration.

← Older revision		Revision as of 01:02, 26 May 2012
Line 60:		Line 60:
	To move a selected plugin in the execution order down, click on the "''move down''" icon [[Image:Arrow down.gif]]. To move a plugin up, click on the "''move up''" icon [[Image:Arrow up.gif]].		To move a selected plugin in the execution order down, click on the "''move down''" icon [[Image:Arrow down.gif]]. To move a plugin up, click on the "''move up''" icon [[Image:Arrow up.gif]].

		+	==== cloning plugin group ====
		+	In order to clone a plugin group (which is useful if you want to create a new plugin group which will contain mostly the same plugins in the same order as the original plugin group), you may click on the "''clone plugin group''" icon [[Image:Edit-copy.gif]]. The new name has to be defined in the next step:
		+
		+	[[Image:Clone plugin group.png]]
		+
		+	By submitting a new name, the existing plugin group will be cloned to the new name.

−	~~[[cloning plugin group]]~~

	[[deleting plugin group]]		[[deleting plugin group]]

@@ Line 50: / Line 50: @@
 By submitting the form the name changes. This namechange has no influence to any configured partner since the internal ID is always used.
 [[cloning plugin group]]
 [[deleting plugin group]]

@@ Line 43: / Line 43: @@
 After submitting the form, a new plugin group has been created and will be listed in the plugin group list.
-[[editing plugin group name]]
+==== editing plugin group name ====
 [[managing plugin group]]

@@ Line 33: / Line 33: @@
 [[Image:Plugingroup list.png]]
-[[creating plugin group]]
+==== creating plugin group ====
 [[editing plugin group name]]

@@ Line 28: / Line 28: @@
 === plugin group management ===
-[[listing plugin groups]]
+==== listing plugin groups ====
 [[creating plugin group]]

@@ Line 6: / Line 6: @@
 ==== Outgoing jobs ====
 The most easiest case is the outgoing job: all job parameters are known when the job starts. In this case, a usable plugin group for sending jobs are searched. This is done in four steps:
-*search for a plugin group at the configured defined recipient
+*search for a send plugin group at the configured defined recipient
-*if not found: search for a plugin group at the configured defined recipient department
+*if not found: search for a send plugin group at the configured defined recipient department
-*if not found: search for a plugin group at the configured defined recipient location
+*if not found: search for a send plugin group at the configured defined recipient location
-*if not found: search for a plugin group at the configured defined recipient company
+*if not found: search for a send plugin group at the configured defined recipient company
-If no plugin group is defined in any of these hierarchy levels, the job gets the status "''aborted''" and s log entry is added to the job (complaining about a non-configured send plugin group for that recipient).
+If no send plugin group is defined in any of these hierarchy levels, the job gets the status "''aborted''" and a log entry is added to the job (complaining about a non-configured send plugin group for that recipient).
 The first found plugin group with its configuration (if any is set) is used for that outgoing job. It's processed from the first to the last plugin of that plugin group.
@@ Line 18: / Line 18: @@
 ==== Incoming jobs when a recipient is known ====
 === plugin group management ===

← Older revision		Revision as of 19:46, 15 June 2008
Line 1:		Line 1:
−	Defined Seon plugins can be grouped into plugin groups. These plugin groups can be administrated via web GUI.	+	Defined Seon plugins can be grouped into plugin groups. These plugin groups can be administrated via web GUI. Configured plugin groups are available for any hierarchical level (company, location, department and recipient) to be defined for incoming and outgoing jobs.
		+
		+	=== Plugin group usage ===
		+	There are three cases for plugin group using: incoming ''before a recipient is known'', incoming jobs ''when a recipient is known'' and outgoing jobs.
		+
		+	==== Outgoing jobs ====
		+	The most easiest case is the outgoing job: all job parameters are known when the job starts. In this case, a usable plugin group for sending jobs are searched. This is done in four steps:
		+	*search for a plugin group at the configured defined recipient
		+	*if not found: search for a plugin group at the configured defined recipient department
		+	*if not found: search for a plugin group at the configured defined recipient location
		+	*if not found: search for a plugin group at the configured defined recipient company
		+	If no plugin group is defined in any of these hierarchy levels, the job gets the status "''aborted''" and s log entry is added to the job (complaining about a non-configured send plugin group for that recipient).
		+
		+	The first found plugin group with its configuration (if any is set) is used for that outgoing job. It's processed from the first to the last plugin of that plugin group.
		+
		+	==== Incoming jobs before a recipient is known ====
		+	When an incoming job starts (after all files are received for that job), the globally configured [[Seon_Core_configuration#default_receive_plugin_group\| default receive plugin group]] will be executed. Its main goal should be defining the correct recipient (and optionally the sender; globally: interpreting the hopefully available ENGDAT abstract file).
		+
		+	==== Incoming jobs when a recipient is known ====
		+

	=== plugin group management ===		=== plugin group management ===