Ir al contenido principal

Sage X3 How to send an e-mail


Sometimes X3 developers needs to send e-mail messages at the end of a batch procedure or from a custom form.
To facilitate these tasks I’ve written a simple Subprog that can be use where you need.
That’s the Subprog
For Sage X3 version 1.4.x
  1. Subprog SEND_MAIL(PTO,PCC,PSUBJECT,PTEXT,PJOIFIC)
  2. Value Char PSUBJECT
  3. Value Char PTEXT
  4. Value Char PJOIFIC
  6. Local Integer PNUMLIN : PNUMLIN = dim(XMSG)
  7. Local Integer XTOTDIM : XTOTDIM = 3+PNUMLIN
  8. Local Integer XCONTA
  10. If PCC <> "" Then
  11. XTOTDIM += 1
  12. Endif
  14. Local Char ENVOI(250)(1..XTOTDIM)
  15. Local Integer XN : XN = 0
  17. XN += 1
  18. ENVOI(XN) = "__TO="+chr$(1)+PTO
  19. If PCC <> "" Then
  20. XN += 1
  21. ENVOI(XN) = "__CC="+chr$(1)+PCC
  22. Endif
  23. XN += 1
  24. ENVOI(XN) = "__SUJET="+chr$(1)+PSUBJECT
  26. For XCONTA = 0 To PNUMLIN - 1
  27. ENVOI(XCONTA+XN+1) = "__NOTE="+chr$(XCONTA+1)+PTEXT(XCONTA)
  28. If XCONTA < PNUMLIN - 1 Then
  29. ENVOI(XCONTA+XN+1)+=chr$(10)
  30. Endif
  31. Next
  33. XN = XN + PNUMLIN
  35. If PJOIFIC <> "" Then
  36. XN += 1
  37. ENVOI(XN) = "__JOINT="+chr$(1)+PJOIFIC
  38. Endif
  40. Call SEND_MESS(2,ENVOI(1..XN)) From SUBAMSC
  42. End

For Sage X3 version 5, 6 and 9
  1. Subprog SEND_MAIL(PTO,PCC,PSUBJECT,PTEXT,PJOINFIC)
  2. Value Char PTO
  3. Value Char PCC
  4. Value Char PSUBJECT
  5. Value Char PTEXT
  6. Value Char PJOINFIC
  8. #YTYPMES: 1 = use the global parameter GTYPMES, 2 = sent by server, 3 = sent by client
  9. Local Integer YTYPMES : YTYPMES = 1
  11. #2 = Retrun receipt
  12. Local Integer YREQREC : YREQREC = 2
  14. #Importance 1=Low 3=High
  15. Local Integer YREQIMP : YREQIMP = 2
  17. Local Char YUSER(20) : YUSER = GUSER
  18. Local Char YMAIL(250) : YMAIL = ""
  19. Local Char YOBJJOI(250) : YOBJJOI = ""
  20. Local Char YCLEOBJ(250) : YCLEOBJ = ""
  21. Local Char YCHRONO(250) : YCHRONO = ""
  23. # 0 -> No detailed trace. >0 -> Write detailed trace
  24. Local Integer YERD
  25. YERD = val(func AFNC.PARAMDOS(nomap,"TRAMEL"))-1 #Read the dossier's param
  27. Local Char YUSR_EMAIL(250)(0..999)
  28. Local Integer YUSR_ENVOI(0..999)
  29. Local Integer YUSR_SUIVI(0..999)
  30. Local Integer YUSR_NB
  31. Local Clbfile YTEXCLB
  32. Local Char YTEXOBJ(250) : YTEXOBJ = PSUBJECT
  33. Local Char YPCEJOI(250)(1..99)
  34. Local Integer YNBJOI
  35. Local Char YTYPJOI(250) : YTYPJOI(0) = ""
  36. Local Integer YCATJOI : YCATJOI = 0
  37. Local Char YCONTXT(250) : YCONTXT(0) = ""
  39. #
  40. #Recipients
  41. #
  43. YUSR_NB = 0
  45. Local Integer I
  46. For I = 0 To dim(PTO) - 1
  47. If vireblc(PTO(I),2) <> "" Then
  48. YUSR_EMAIL(YUSR_NB) = vireblc(PTO(I),2)
  49. YUSR_ENVOI(YUSR_NB) = 2
  50. YUSR_NB += 1
  51. Endif
  52. Next
  54. For I = 0 To dim(PCC) - 1
  55. If vireblc(PCC(I), 2) <> "" Then
  56. YUSR_EMAIL(YUSR_NB) = vireblc(PCC(I), 2)
  57. YUSR_ENVOI(YUSR_NB) = 3
  58. YUSR_NB += 1
  59. Endif
  60. Next
  63. #
  64. # Attachment
  65. #
  67. YNBJOI = 0
  68. For I = 0 To dim(PJOINFIC) - 1
  69. If vireblc(PJOINFIC(I),2) <> "" Then
  70. YNBJOI += 1
  71. YPCEJOI(YNBJOI) = vireblc(PJOINFIC(I),2)
  72. Endif
  73. Next
  75. Setlob YTEXCLB With PTEXT
  77. Call ENVOI_MAIL(YTYPMES,YREQREC,YREQIMP,YUSER,YMAIL,YOBJJOI,YCLEOBJ
  78. & ,YCHRONO,YERD,YUSR_EMAIL,YUSR_ENVOI,YUSR_SUIVI,YUSR_NB
  79. & ,YTEXCLB,YTEXOBJ
  80. & ,YPCEJOI,YNBJOI,YTYPJOI,YCATJOI,YCONTXT) From AWRKMEL
  82. End
Here an example of how to call the Subprog
  1. Local Char XMSG(250)(8)
  2. Local Char XSUJET(250)
  3. Local Integer XXCONTA : XXCONTA = 0
  5. XXCONTA += 1: XMSG(XXCONTA) = "Test email body, row1" + num$(XXCONTA)
  6. XXCONTA += 1: XMSG(XXCONTA) = "row 2 " + num$(XXCONTA)
  7. XSUJET = "E-mail subject"
  9. Call SEND_MAIL("xxx.xxx@xxxxx.xxx","",XSUJET,XMSG,"")
Here how to send the current trace
  1. Local Char XMSG(250)(6)
  2. Local Char XSUJET(250)
  3. Local Integer XXCONTA : XXCONTA = 0
  5. XXCONTA += 1: XMSG(XXCONTA) = "Test email body, row1" + num$(XXCONTA)
  6. XXCONTA += 1: XMSG(XXCONTA) = "row 2 " + num$(XXCONTA)
  7. XSUJET = "E-mail subject"
  8. If GTRACE <> "" Then
  9. XFTRACE = func F_FIC_TRACE(GTRACE)
  10. XMSG(6) = "----------"
  11. XMSG(7) = XFTRACE
  12. Endif
  14. Call SEND_MAIL("xxx.xxxxx@xxxxx.xx","xxxx_cc@xxxxx.xx",XSUJET,XMSG,XFTRACE)
The F_FIC_TRACE it’s a function tha return the full path of the trace
  1. Funprog F_FIC_TRACE(XGTRACE)
  2. Value Char XGTRACE
  4. Local Char WNAME(250)
  5. If left$(XGTRACE,2)="#@" & (GBROWS | GSERVEUR)
  6. WNAME = ""
  7. Elsif max(instr(1,XGTRACE,"/"),instr(1,XGTRACE,"\"),instr(1,XGTRACE,"@"))
  8. WNAME = XGTRACE
  9. Else
  10. WNAME = filpath("TRA",XGTRACE,"tra")
  11. Endif
  12. If filinfo(WNAME,0)=0
  13. WNAME = ""
  14. Endif
  16. End WNAME

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