ONYX:9.0:Utilisation:Les bonnes pratiques/en - Historique des versions

Alestoquoi le 28 août 2019 à 13:37

2019-08-28T13:37:40Z

Alestoquoi le 9 août 2019 à 12:38

2019-08-09T12:38:55Z

Alestoquoi le 31 juillet 2019 à 08:24

2019-07-31T08:24:37Z

Alestoquoi le 30 juillet 2019 à 13:21

2019-07-30T13:21:47Z

FuzzyBot : Mise à jour pour être en accord avec la nouvelle version de la source de la page

2019-07-30T09:50:30Z

Mise à jour pour être en accord avec la nouvelle version de la source de la page

Alestoquoi : Page créée avec « ===Sending e-mails=== * '''Separate splitting and sending''': Do not use tools to split, print files and send e-mails all in the same processing. Prefer splitting in PDF i... »

2019-07-30T09:47:38Z

Page créée avec « ===Sending e-mails=== * '''Separate splitting and sending''': Do not use tools to split, print files and send e-mails all in the same processing. Prefer splitting in PDF i... »

Alestoquoi : Page créée avec « * '''Transfer integrity''': Establishing a coherent deposit strategy is essential so that Mapping cannot retrieve truncated files being transferred (ftp, sftp, cft or othe... »

2019-07-30T09:33:24Z

Page créée avec « * '''Transfer integrity''': Establishing a coherent deposit strategy is essential so that Mapping cannot retrieve truncated files being transferred (ftp, sftp, cft or othe... »

Alestoquoi : Page créée avec « * '''Local folders only''': Setting a Scan folder robot to output in a remote folder on a remote server is not recommended. »

2019-07-30T09:22:31Z

Page créée avec « * '''Local folders only''': Setting a Scan folder robot to output in a remote folder on a remote server is not recommended. »

Alestoquoi : Page créée avec « ===Scan Folder Robots=== * '''Automatic queue assignment''': Except in special cases, you should NEVER associate a scanfolder robot with a "complex" workflow. The only pro... »

2019-07-30T09:15:53Z

Page créée avec « ===Scan Folder Robots=== * '''Automatic queue assignment''': Except in special cases, you should NEVER associate a scanfolder robot with a "complex" workflow. The only pro... »

Alestoquoi : Page créée avec « * '''Log level''': For performance reasons, do not leave the '''LOG_LEVEL''' setting set to 4 in production. You could leave it the way it is if performance is not one of... »

2019-07-30T09:08:32Z

Page créée avec « * '''Log level''': For performance reasons, do not leave the '''LOG_LEVEL''' setting set to 4 in production. You could leave it the way it is if performance is not one of... »

← Version précédente		Version du 28 août 2019 à 13:37
Ligne 30 :		Ligne 30 :
	* '''MAPPING_DATASTREAM=XML''': To generate an XML file, you must create the '''DB.MAPPING_DATASTREAM''' variable and associate the "XML" value to it.		* '''MAPPING_DATASTREAM=XML''': To generate an XML file, you must create the '''DB.MAPPING_DATASTREAM''' variable and associate the "XML" value to it.

−	* '''Generating XML projects automatically''': Using the feature to generate projects automatically while supporting XML input ~~file~~ is not recommended. The code which is generated is difficult to maintain. It can however be used to understand CONNECT operating principles on XML files reading.	+	* '''Generating XML projects automatically''': Using the feature to generate projects automatically while supporting XML input files is not recommended. The code which is generated is difficult to maintain. It can however be used to understand CONNECT operating principles on XML files reading.

@@ Ligne 51 : / Ligne 51 : @@
 * '''Automatic queue assignment''': Except in special cases, you should NEVER associate a scanfolder robot with a "complex" workflow. The only processing the workflow can execute is assigning a job to the spooler queue, and potentially initiate variables to add meta data to this job. The aim is to track jobs and benefit from proper exception management.
-* '''Local folders only''': Setting a Scan folder robot to output in a remote folder on a remote server is not recommended.
+* '''Local folders only''': Setting a Scan folder robot to point in a remote folder on a remote server is not recommended.
 * '''Transfer integrity''': Establishing a coherent deposit strategy is essential so that Mapping cannot retrieve truncated files being transferred (ftp, sftp, cft or other protocoles). For example, use a temporary name for the time of the deposit, use a "cookie" file or move the file (in the same FS) once the transfer is finished. Do not use the "CHECK_FTP_FILE_ACCESS" setting and its timeout as it does not insure the integrity of the file retrieved.

@@ Ligne 55 : / Ligne 55 : @@
 * '''Transfer integrity''': Establishing a coherent deposit strategy is essential so that Mapping cannot retrieve truncated files being transferred (ftp, sftp, cft or other protocoles). For example, use a temporary name for the time of the deposit, use a "cookie" file or move the file (in the same FS) once the transfer is finished. Do not use the "CHECK_FTP_FILE_ACCESS" setting and its timeout as it does not insure the integrity of the file retrieved.
 ===Sending e-mails===
 * '''Separate splitting and sending''': Do not use tools to split, print files and send e-mails all in the same processing. Prefer splitting in PDF into a dedicated e-mailing queue first, then in turn let this queue manage e-mail delivery, one e-mail at a time.<br/>
 :Otherwise, no tracking is possible and if, for example, an email address is inaccurate (syntax error), the job can be interrupted during processing even though some of the e-mails have already been sent. Relaunching the job properly is then impossible without generating duplicate e-mails.

@@ Ligne 22 : / Ligne 22 : @@
 * '''TEXT memory zones''': If no calculations are required, "Memory" type zones must always have a '''"Text Memory"''' sub-type, never an "Entire Memory" nor "Floating Memory" (even if the fields handled are numerical)
-* '''FRONT Spacing''': when creating groups, manage line breaks with the '''FRONT spacing'''. AFTER spacing should only be used to add an empty space before the next line. Do not ever write in a space dedicated to an other line (i.e the previous or next line), each line has its own dedicated space defined by <u><i>"FRONT Spacing + AFTER Spacing"</i></u>.
+* '''Space BEFORE''': when creating groups, manage line breaks with '''Space BEFORE'''. AFTER spacing should only be used to add an empty space before the next line. Do not ever write in a space dedicated to an other line (i.e the previous or next line), each line has its own dedicated space defined by <u><i>"Space BEFORE + Space AFTER"</i></u>.
 * '''Automatic page break''': Do not ever use more than one group to generate a page break in a project (even with execution conditions).

@@ Ligne 55 : / Ligne 55 : @@
 * '''Transfer integrity''': Establishing a coherent deposit strategy is essential so that Mapping cannot retrieve truncated files being transferred (ftp, sftp, cft or other protocoles). For example, use a temporary name for the time of the deposit, use a "cookie" file or move the file (in the same FS) once the transfer is finished. Do not use the "CHECK_FTP_FILE_ACCESS" setting and its timeout as it does not insure the integrity of the file retrieved.
 ===Sending e-mails===
 * '''Separate splitting and sending''': Do not use tools to split, print files and send e-mails all in the same processing. Prefer splitting in PDF into a dedicated e-mailing queue first, then in turn let this queue manage e-mail delivery, one e-mail at a time.<br/>
 :Otherwise, no tracking is possible and if, for example, an email address is inaccurate (syntax error), the job can be interrupted during processing even though some of the e-mails have already been sent. Relaunching the job properly is then impossible without generating duplicate e-mails.
+</div>

@@ Ligne 53 : / Ligne 53 : @@
 * '''Local folders only''': Setting a Scan folder robot to output in a remote folder on a remote server is not recommended.
-* '''Intégrité de transfert''' : Il est primordial de mettre en place une stratégie de dépôt cohérente afin que Mapping ne puisse pas récupérer des fichiers tronqués car en cours de transfert (ftp, sftp, cft ou autres protocoles). Par exemple avec un nom temporaire pendant le dépôt, avec un fichier "témoin" ou en déplaçant le fichier (dans le même FS) une fois le transfert terminé. Ne pas utiliser le paramètre "CHECK_FTP_FILE_ACCESS" et son timeout qui ne permet en aucun cas de garantir l'intégrité du fichier récupéré.
+* '''Transfer integrity''': Establishing a coherent deposit strategy is essential so that Mapping cannot retrieve truncated files being transferred (ftp, sftp, cft or other protocoles). For example, use a temporary name for the time of the deposit, use a "cookie" file or move the file (in the same FS) once the transfer is finished. Do not use the "CHECK_FTP_FILE_ACCESS" setting and its timeout as it does not insure the integrity of the file retrieved.
 ===Envoi d'emails===

@@ Ligne 48 : / Ligne 48 : @@
-===Robots Scan Folder===
+===Scan Folder Robots===
-* '''Injection systématique dans une file d'attente''' : Sauf cas particuliers, il ne faut JAMAIS associer un robot scanfolder à un workflow "complexe". Le seul traitement pouvant être exécuté par le workflow est l'injection du travail dans une file d'attente du spooler, et éventuellement des initialisions de variables permettant d'ajouter des méta données à ce travail. Ceci pour des raisons de suivi des travaux ainsi que pour bénéficier d'une gestion correcte des exceptions.
+* '''Automatic queue assignment''': Except in special cases, you should NEVER associate a scanfolder robot with a "complex" workflow. The only processing the workflow can execute is assigning a job to the spooler queue, and potentially initiate variables to add meta data to this job. The aim is to track jobs and benefit from proper exception management.
 * '''Répertoires locaux seulement''' : Il est vivement déconseillé de faire pointer un robot Scan folder sur un répertoire distant situé sur un serveur distant.

← Version précédente		Version du 30 juillet 2019 à 09:08
Ligne 45 :		Ligne 45 :
	* '''Save jobs:''' Do not forget to "Save" the jobs sent to the queues for debugging purposes.		* '''Save jobs:''' Do not forget to "Save" the jobs sent to the queues for debugging purposes.

−	* '''~~Niveau de log~~''' : ~~Pour des raisons de performances de traitements des travaux~~, ~~ne jamais laisser le paramètre~~ '''LOG_LEVEL''' à 4 en production. ~~Sauf éventuellement si les performances ne sont pas un besoin majeur~~. ~~Ce paramètre a énormément d'~~impacts ~~sur les performances s'il y a beaucoup de~~ "~~petits~~" ~~travaux" à traiter~~. ~~Dans ce cas, le niveau~~ 3 ~~peut également être trop élevé~~, ~~et le niveau~~ 2 ~~peut s'avérer suffisant~~ (~~uniquement erreurs et~~ warnings).	+	* '''Log level''': For performance reasons, do not leave the '''LOG_LEVEL''' setting set to 4 in production. You could leave it the way it is if performance is not one of your major concerns. This setting has huge impacts on performance if many "small" jobs are processed. In this case the log level 3 can also be too high, level 2 can be enough (only for errors and warnings).