Ir al contenido principal

Sage X3 Job with dynamics parameters


In Sage X3 we can setting execution scheduling of a command using the SYSTEME Sage x3 job.
You can manage the Sage x3 jobs with Usage\Batch Server\Task management menu (GESABT function).
As parameter we pass it the system command to execute, for example “C:\temp\command.bat par1 par2″,  and that’s it.
If by chance we need to move this scheduling from a Sage X3 folder to another,
to pass the name Sage x3 folder as dynamic parameter can be useful,
so we do not have to modify the command to pass to the job SYSTEME every time.
To do this just create a job SYSTEME wrapper.
The SYSTEME job call the homonym SYSTEME action, which has as unique parameter the command string to execute;
to reach our target so we will create a YSYSTEME job and a YSYSTEME action.
But this EXESYS action what do it do precisely? It call a subprog of ORDSYS.
Here an example: the following code line executes the batch command Command.bat
that is present in the directory c:\DIR\SUB\
Call SYSTEME ("","C:\DIR\SUB\Command.bat","b",YSTAT) From ORDSYS
So, we duplicate the EXESYS action renaming it as YEXESYS.
We leave everything as it is, except for specific script box where we insert YEXESYS.
(at the place of YXEXESYS: this source file doesn’t exist, you can check the correspondant adx file is not present).
Remember to insert the Activity code.
Then duplicate the SYSTEME function SYSTEME giving it YSYSTEME name; we can remove value at “Parent menu” box
and as action we set YEXESYS.
Good, now we duplicate also the SYSTEME job setting the new job with name YSYSTEME and with function YSYSTEME.
At this point we just have to write the source code YEXESYS,
so that we can pass a parameter to evalue at runtime enclosed in two “%”:

###############################################################
$ACTION
Case ACTION
 When "CONTROLE" : Gosub CONTROLE
 When Default
Endcase
Return
###############################################################

###############################################################
#NB: [M:EXS]ORDSYS is the field that contains the command
###############################################################
$CONTROLE
Local Integer I1,I2
Local Char YPARAM(30)
Local Char YVALUE(30)
 I1=0
 I2=0
 I1=instr(1,[M:EXS]ORDSYS,"%")
 If I1
   I2=instr(I1+1,[M:EXS]ORDSYS,"%")
   If I2
   YPARAM = seg$([M:EXS]ORDSYS,I1+1,I2-1)
   YVALUE = evalue (YPARAM)
   [M:EXS]ORDSYS = func YSAGEDEV.REPLACE([M:EXS]ORDSYS, "%"+YPARAM+"%", YVALUE)
   Endif
 Endif
End
###############################################################
Very good, now in scheduling we could pass as parameter, for instance,
c:\Sage\folders\%nomap(0)%\YIMPORT\filename.txt %nomap(0)%
that will be transformed into (in the case that Sage X3 folder name is TEST)
c:\Sage\folders\TEST\YIMPORT\filename.txt TEST
In this way we can pass as dynamic parameters anything can be interpreted by evalue.
Note that with this code we can insert nomap(0) twice, but we can not insert nomap(0) and also nomap(1).
Attention, the program is not for production environment.
In the case of syntax error the command will be executed anyway, with unforeseeable consequences.
I help this help you,
and if you use it in a original way, write it in the comments!

If you wish a complete version of the program, with
  1. syntax control and errors management
  2. evalue function errors management
  3. multiple different parameters management
  4. a batch file that manages the FOLDER parameter without having to worry about the parameters already present
subscribe and you will receive it for free with all other additional contents!

Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...

How to create an additional line text (ACLOB) on purchase orders for internal notes

Sin conexión Kyle Klinger hace 1 día Origen:  https://www.sagecity.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/143870/how-to-create-an-additional-line-text-aclob-on-purchase-orders-for-internal-notes I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to.  If you have a better way, please share.     Add column to PORDERQ; YLINTEX2, Type TXC   Save and validate table This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX  On screen POH2 Add column YLINTEX2, to Block 1. Most likely you will want this field to be hidden. On column NBLIG add a button action ACLOB2, description "Text internal" This button action will require an action parameter "CODE2", it will not be available until after save. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added....

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  ...