Ir al contenido principal

How open or print a file pdf from Sage script


To open a pdf file from an adonix program, you can use the call ETAT From AIMP3.
To indicate that the pdf must be opened on the screen, you have to indicate a destination of type PREVIEW as the print destination.
Below is an example of a program that takes the path of a pdf file as a parameter and opens it to a video.
Warning: this code has been tested for version 6.5.
Subprog APRIPDF(FILENAME)
 Value Char FILENAME()
# the following two are arrays  
# TBPAR contains the name of the print parameter 
# TBVAL contains its value
Local Char TBPAR(15)(1..6), TBVAL(200)(1..6)
 
GSILENCE = 1              # global variable that inhibits all the messages on the screen
TBPAR(1) = "docjoin"      # first and only parameter of the "ADOC" press code (attached print)
TBVAL(1) = FILENAME       # value of parameter

Call ETAT("ADOC","","",1,"",TBPAR,TBVAL) From AIMP3 

GSILENCE = 0              # restore the value of GSILENCE
End
To use this program:
#for local path
Call APRIPDF("c:\folder\sub\myfile.pdf") from YSAGEDEV
#or for network path
Call APRIPDF("\\server\folder\sub\filename.pdf") from YSAGEDEV
But let’s see the call in detail ETAT From AIMP3:
Call ETAT(CODE,DESTINATION,LANGUAGE,TRACE,MSG,TBPAR,TBVAL) From AIMP3
  • CODICE it’s the printing code that you find by going to the function GESARP
  • DESTINATION it is the printing destination (attention that depending on the type of destination the actions performed may be different)
  • LANGUAGE language to print, if it’s blank, the session language is usedWhat changes the language?
    1. title of the print (parameter X3TIT pass to a Crystal Report)
    2. il parameter X3LAN pass to Crystal Report, on which any translations can be based
    3. the folder where find the report (file .rpt), if code print is nel caso il codice di stampa is referred to as multilingual(folders ITA, ENG ecc in REPORT folder)
  • TRACE indicates if a log file should be written (1 writes it, 0 does not write it)
  • MSG contains any message to be written to the track or to be displayed interactively
  • TBPAR contains the list of print parameter names (those found in GESARP)
  • TBVAL contains the list of print parameter values, in the same order as TBPAR
It is clear that with this call you can do much more than just open a pdf!
If you have some questions or other examples, write them in the comments.

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

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...
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