ONYX:9.0:Utilisation:Guide de prise en main ONYX Server/en - Historique des versions

Alestoquoi le 30 août 2019 à 08:16

2019-08-30T08:16:40Z

2019-08-30T07:57:46Z

2019-08-29T14:42:28Z

2019-08-29T14:31:52Z

2019-08-29T12:52:07Z

2019-08-29T12:51:45Z

2019-08-29T12:43:31Z

2019-08-29T12:42:56Z

2019-08-29T12:40:11Z

2019-08-29T11:37:51Z

@@ Ligne 1 071 : / Ligne 1 071 : @@
 ===Clearing logs===
-The <code>map_cron</code> command clears the files corresponding to ONYX Server logs. Options can be set to keep archives of the logs before they are deleted, to keep history.
+The <code>map_cron</code> command clears the files corresponding to ONYX Server logs. Options can be set to keep archives of the logs before they are deleted, to keep them as history.
 *'''Creating an archive (ZIP) of the logs before deleting them:'''

@@ Ligne 965 : / Ligne 965 : @@
 ===Managing printers===
-In this previous view, only the queue which contain jobs are displayed in the results. The "Printers" tab lists all the queues declared in the Spooler:
+In this previous view, only the queues which contain jobs are displayed in the results. The "Printers" tab lists all the queues declared in the Spooler:
 [[Fichier:OX S printers.png|alt=|centré]]

@@ Ligne 783 : / Ligne 783 : @@
 <li><p>equal to / different from: strict alphanumerical comparison between 2 values</p></li>
 <li><p>contains / does not contain: alphanumerical research of a value in another value</p></li>
-<li><p>is empty / is not empty: does the the parameter have a value?</p></li>
+<li><p>is empty / is not empty: does the parameter have a value?</p></li>
 <li><p>greater than / greater than or equal to: numerical comparison</p></li>
 <li><p>less than/ less than or equal to: numerical comparison</p></li></ul><p></p>A condition can be defined by multiple condition filters. The [[Fichier:OX S iconeajoutcdt.png|C:\MAPPING\MappingWindows\MapHTTPServer\JS_Common\workflow\img\button_add_elt.png]] button allows you to add a new condition filter. The logic between these filters is defined graphically using the boxes to tick before each filter and the [[Fichier:OX S operateurAND.png|C:\MAPPING\MappingWindows\MapHTTPServer\JS_Common\workflow\img\button_and_elt.png]] and [[Fichier:OX S operateurOR.png|C:\MAPPING\MappingWindows\MapHTTPServer\JS_Common\workflow\img\button_or_elt.png]] tools. In this example, the condition logic is defined by: filter A and (filter B or filter C). The [[Fichier:OX S deletecdt.png|C:\MAPPING\MappingWindows\MapHTTPServer\JS_Common\workflow\img\button_del_elt.png]] button allows you to delete a selected condition filter, or a selected condition logic (and the associated filters).

@@ Ligne 712 : / Ligne 712 : @@
 |Retrieval of a command line
 |[[Fichier:OX S cmdIcon.png|C:\Program Files\MappingWindows\MapHTTPServer\JS_Common\workflow\img\button_cmd.png]]
-|cmd: chemincomplet...
+|cmd: completepath...
 |-
 |SQL

@@ Ligne 655 : / Ligne 655 : @@
 To create a new parameter, select the box after which the new parameter must be added, then, click on the [[Fichier:OX S iconewrkflwParam.jpg|but_set.jpg]] icon. To edit an existing parameter, double-click on the corresponding box.
-The editing window for a parameter opens to define the different fields:
+The editing window of the parameter opens to define the different fields:
 [[Fichier:OX S workflowSetParam.png|alt=|centré]]
 <br />

@@ Ligne 605 : / Ligne 605 : @@
 On the ONYX Server web interface, the administration and configuration of Workflows is accessed through the Administration Menu, Managing Workflows.
-<u>Advice:</u> Firefox is recommended as browser for better user experience.
+<u>Tips:</u> Firefox is recommended as browser for better user experience.
 ===Toolbar===

@@ Ligne 599 : / Ligne 599 : @@
 *Defines a parameter by reading information in the input file
 *Defines a condition by comparing the value of this parameter with a keyword
-*Defines two processings, if the condition is true or false
+*Defines two processings, depending on the condition being true or false
 Workflows are saved on disk in XML files, in the "workflow" sub-folder of the rules folder which is pointed by the RULES_PATH configuration variable.

@@ Ligne 589 : / Ligne 589 : @@
 ===Introduction===
-Workflows make the ONYX Server execution engine. A Workflow is defined as a set of configurable conditions and commands, executed when a new file is received on an input connector (Scanfolder robot, listening server, input point, or by Web Service request). Commands are processed one by one: the second command is processed after the first one was processed properly, and so on until the end of the Workflow.
+Workflows make the ONYX Server execution engine. A Workflow is defined as a set of configurable conditions and commands, executed when a new file is received on an input connector (Scanfolder robot, listening server, entry point, or by Web Service request). Commands are processed one by one: the second command is processed after the first one was processed properly, and so on until the end of the Workflow.
 A Workflow is defined graphically by linking different types of objects: commands, conditions and parameters. Its name must be unique and it must be linked to at least one connector to be active.

@@ Ligne 510 : / Ligne 510 : @@
 **default or stop: the current processing stops in error status, the device stops in error status.
 **continue: the current processing stops in error status, the device continues to process the next queries.
-**ignore: the current processing is considered as done, the device continues to process the next queries. <span class="underline">This value is not recommended</span>, except for very specific values.
+**ignore: the current processing is considered as done, the device continues to process the next queries. <span class="underline">This value is not recommended</span>, except for very specific cases.
 *(13) Automatic recovery: if activated, an error inducing print job is relaunched
-**Timeout: maximum time during which the print job in error status is relaunched before it is actually considered as being in error. The behaviour of the device upon error is the n taken into account.
+**Timeout: maximum time during which the print job in error status is relaunched before it is actually considered as being in error. The behaviour of the device upon error is then taken into account.
 **Recovery mode: in its entirety or per page