Ir al contenido principal

PDF signature

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, RETURNS, RESHEAD, RESBODY)
Value Char PDFNAME
Value Clbfile DATA
Value Char CERTNAME
Value Integer FUTURE
Value Char RETURNS
Variable Clbfile RESHEAD()
Variable Clbfile RESBODY()

Local Integer STATUSCODE
Local Char MODULE(100) : MODULE = '$pdf'
Local Char FONCTION(30) : FONCTION = 'sign'
Local Char MODE(10)
If (FUTURE = 1) : MODE = 'future' : Else : MODE = 'wait' : Endif

Local Clbfile ARGUMENTS(0)
ARGUMENTS = '"' + PDFNAME + '","' + DATA + '","' + CERTNAME + '", {"returnData": true, "encoding": "base64"}'
Local Clbfile RESBODY(0)
# Call 'sign' function
STATUSCODE = func ASYRWEBSER.EXEC_JS(MODULE, FONCTION, MODE, ARGUMENTS, '0,1,0,0', 0, RETURNS, '0', RESHEAD, RESBODY)

End STATUSCODE
If STATUSCODE is set to 200, RESBODY will contain the signed PDF.

For further information, consult our ASYRWEBSER API documentation.


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