Sage X3

Origen fuente:  http://online-help.sageerpx3.com/erp/12/wp-static-content/static-pages/en_US/v7dev/api-guide_api-asyrwebser.html A standard API is available in X3 scripts to perform calls to the platform's javascript published functions. It works on code executed from classic pages as well as on V7 (and later) code. General Web server javascript call The function is located in the ASYRWEBSER library, and its definition is the following: Funprog EXEC_JS(MODULE, FUNCTION_NAME, MODE, ARGUMENTS, ENCODINGS, CALLB, RETURNS, RETURNS_ENC, RESHEAD, RESBODY) Value Char MODULE() : # The name of the published node.js javascript module Value Char FUNCTION_NAME() : # The name of the javascript function to be called Value Char MODE() : # A mode to determine if the call is synchronous or asynchronous ('sync' or 'wait') : # This mode depends on the signature of the function Value Clbfile ARGUMENTS() : # Multiple arguments delimited by

Origen de la fuente:  http://online-help.sageerpx3.com/erp/12/wp-static-content/static-pages/en_US/v7dev/api-guide_api-pdfsignature.html The PDF signature API provides a function that signs a PDF file with a certificate stored in the Syracuse server. The function can be called from the 4GL with the code hereunder. The function name is  pdfsign . PDF signature call #** #* This function signs a PDF file using a certificate defined in the Syracuse administration. #* #* @param PDFNAME : Char : PDF name #* @param DATA : Clbfile : Content encoded in base 64 #* @param CERTNAME : Char : Name of the certificate to use defined in the Syracuse administration #* @param FUTURE : Integer : Set to 1 to be called in 'future' mode or 0 for the 'wait' mode #* @param RESHEAD : Clbfile : Response header #* @param RESBODY : Clbfile : Signed PDF content #* @return STATUSCODE : Integer : Status code returned by the javascript runner module #*! Funprog PDFSIGN(PDFNAME, DATA, CERTNAME, FUTURE,

Ultimo día del mes actual [M:CSP1]ORDDATFIN=eomonth(date$) Restar 2 meses a la fecha actual  [M:CSP1]ORDDATDEB=gdat$(01,month(addmonth(date$,-2)),year(addmonth(date$,-2)))

Fuente original: Greytrix  https://www.greytrix.com/blogs/sagex3/2013/10/28/how-to-filter-local-menu/ By  Greytrix   |   October 28, 2013 0  In In X3, we developer may come across with the requirement where we need to filter the local menu values for the fields. There are simple techniques available in X3 to filter the local menu values. Follow the below steps to filter the local menu field records: The M data type of local menu is non-modifiable however in X3 there is alternate data type is available i.e. MM whose values we can modify at the runtime. Therefore use the MM data type for the local menu which you want to filter run time as shown in the below screenshot. Add Before entry field action on that field. The GMENLOC global variable can be used to filter the local menu values. We just need to set the GMENLOC(i) variable to 1 to deactivate the local menu values. It will be more preferable to set the values to GMENLOC variable in the Before Entry field action as it gets called befo

Fuente información:  http://online-help.sageerpx3.com/erp/11/staticpost/dela/?highlight=dela Dela  is used to delete elements from single-sized arrays, from a given index. Syntax Dela START ARRAY_LIST Dela START, NUMBER ARRAY_LIST Dela START, NUMBER, LIMIT ARRAY_LIST START  is an integer expression that gives the index in the arrays from which the deletions are made. It cannot exceed the highest index or fall short of the smallest index available in the array list. NUMBER  is an integer expression that gives the number of indexes to be deleted. It must be strictly positive. If not given by the syntax, '1' will be used. LIMIT  is an integer expression that gives the index in the arrays where the deletion ends.  LIMIT  cannot exceed the highest index and the smallest index available in the array list. ARRAY_LIST  is a list of arrays variable (at least one), separated by commas. Examples: Let's imagine we have three arrays called COMPOSER(1..10), NAME(1..10), and BIRT