Ir al contenido principal

Launch a batch execution request

 

The following subprogram launches the execution of a V6 batch request from V7 native code.

Main principles of a V6 batch task

A V6 batch task is associated with an X3 function that executes an action using the Standard processing template. A criteria window with associated masks is then defined. You need to provide all the required parameters for the batch task execution by filling in all the fields for these masks.

For these reasons, calling the ASYRMNGTREQ.CRERQT subprogram requires you to define the mask fields by filling in the corresponding values.

Subprogram definition

The API is called with the corresponding funprog:

Func ASYRMNGTREQ.CRERQT(ACTX,FOLD,USER,TASK,DAT,TIM,ARYPAR,ARYVAL,NBPAR,REQUEST,MESSAGE)

The parameters are the following:
* ACTX is the current context.
* FOLD is the folder name.
* USER is the user code for execution.
* TASKis the task name.
* DATis the date of the requested execution, and TIM is a string containing the requested time with the hh:mm or hhmm format.
* ARYPAR is an array of string containing the name of the fields to be filled in the parameter mask. The value of the corresponding parameter is given in string format at the same index on the array ARYVAL. The number of parameters is given by the integer value NBPAR.

The string format for ARYVAL values is the following:
* A string containing digits for local menus (for example "12").
* A string containing a numeric representation for integer or decimals (for example "-2" or "3.1415926").
* A string containing a date in YYYYMMDD format (for example "19590529").
* If you expect a string or a clob to exceed 250 characters, you can have several successive entries in ARYPAR with the same variable name and split the string values into chunks of 250 characters or less. The different values will be concatenated to get the complete parameter value.

The value returned by this API is 0 if the request has been successfully launched. In this case, REQUEST returns the request id. If an error occurs, the value returned will be different from 0, and the MESSAGE value will return the corresponding error message.

This API can be launched from inside a running database transaction. No log file is created.

Example

# Create a request in folder X3 to revalidate the current folder today at 23:00
Funprog VALID_MY_FOLDER
Local Integer ASTATUS , NBPAR , REQUESTID
Local Char TBPAR(30)(1..10) , TBVAL(250)(1..10) , TIM(8) , MESSAGE(250) , TACHE(30) , DOSSIER(30) , USER(10)
Local Date DAT

  DAT = date$
  TIM = "23:00"
  TASKNAME = "VALDOS"
  FOLDER = "X3"
  USER = GACTX.USER
  NBPAR  = 1 : TBPAR(NBPAR) = "DOSSIER(0)" : TBVAL(NBPAR) = GACTX.AFOLDER
  NBPAR += 1 : TBPAR(NBPAR) = "NBDOS"      : TBVAL(NBPAR) = "1"
  NBPAR += 1 : TBPAR(NBPAR) = "TRADIF"     : TBVAL(NBPAR) = "1"
  NBPAR += 1 : TBPAR(NBPAR) = "VALDIF"     : TBVAL(NBPAR) = "2"
  ASTATUS = func CRERQT(GACTX,FOLDER,USER,TASKNAME,DAT,TIM,TBPAR,TBVAL,NBPAR,REQUESTID,MESSAGE)

  If ASTATUS=0
    MESSAGE="Request #"+num$(REQUESTID)+" launched successfully"
  Else
    MESSAGE="Error #"+num$(ASTATUS)+": "+MESSAGE
  Endif

End MESSAGE

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 ,  ...
Leer más

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....
Leer más

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  ...
Leer más