From 3e5f8bd346f2f1766d2bcbe848bced81918b13cc Mon Sep 17 00:00:00 2001 From: duongtq Date: Wed, 10 Jul 2024 12:14:22 +0700 Subject: [PATCH] [IMP] edi_oca: update docs for EDI Jobs --- edi_oca/README.rst | 9 --------- edi_oca/readme/CONFIGURE.rst | 9 +++++++++ 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/edi_oca/README.rst b/edi_oca/README.rst index f2f941c7e..4ff12ead2 100644 --- a/edi_oca/README.rst +++ b/edi_oca/README.rst @@ -59,15 +59,6 @@ In order to define a new Exchange Record, we need to configure: * Backend * Components -Component definition -~~~~~~~~~~~~~~~~~~~~ - -The component usage must be defined like `edi.{direction}.{kind}.{code}` where: - -* direction is `output` or `input` -* kind can be: `generate`, `send`, `check`, `process`, `receive` -* code is the `{backend type code}` or `{backend type code}.{exchange type code}` - User EDI generation ~~~~~~~~~~~~~~~~~~~ diff --git a/edi_oca/readme/CONFIGURE.rst b/edi_oca/readme/CONFIGURE.rst index acf6a0d28..24a1cede1 100644 --- a/edi_oca/readme/CONFIGURE.rst +++ b/edi_oca/readme/CONFIGURE.rst @@ -10,6 +10,15 @@ In order to define a new Exchange Record, we need to configure: * Backend * Components +Jobs +~~~~~~~~~~~~~~~~~~~~ + +* (1) **Internal User**: might be an EDI user without even knowing about it, triggering EDI flows by some of his actions on business records; does not need access to related queue jobs. + +* (2) **EDI User**: more conscious EDI user that might sometimes need to debug things a bit further and thus needs access to related queue jobs. + +* (3) **EDI Manager**: full configuration access. + Component definition ~~~~~~~~~~~~~~~~~~~~