Ir al contenido principal

How to Automatically Email a Report in Sage Enterprise Management (Sage X3)

How to Automatically Email a Report in Sage Enterprise Management (Sage X3)
During the implementation cycle, we’re often asked if we can set it up so a company can automatically email a report in Sage Enterprise Management (Sage X3) – sales order confirmations when someone places an order, for example, or confirmation invoices when goods are shipped.

By leveraging the destination management and workflow capabilities of Enterprise Management, it’s very possible – easy, in fact – to set it up so that you can click just one button and send an automatically generated email.


As an example, we’ll try to create an environment where we can simultaneously create the invoice from the delivery screen and email the confirmation to our customer.

First, you’ll have to create the email destination and make sure that the parameters are configured to be able to email within the parameter values.

email a report in Sage Enterprise Management (Sage X3)

This is where you’ll define the email server IP or mask.


email a report in Sage Enterprise Management (Sage X3)


Second, you must define a new report code and its default values. This will allow you to specify which print destination to use.

email a report in Sage Enterprise Management (Sage X3)


Note that you can also do that using the destination by user functionality.
These are the default values under setup > destinations > default values.


email a report in Sage Enterprise Management (Sage X3)


Next, create the print code for this new report code. Please make sure that it allows for direct print, as that bypasses the print parameters screen and assumes you’ll use all the default print parameters.


email a report in Sage Enterprise Management (Sage X3)


You’ll also need to configure the workflow rule and the entry transaction to allow each action to be automated.

email a report in Sage Enterprise Management (Sage X3)


workflow rules 2.jpg


email a report in Sage Enterprise Management (Sage X3)


And the entry transaction setup as follows:

The only setup you need to worry about is the report code and the auto print flag.
To get this to work with just one click, you need to have only one entry transaction set up. Otherwise, you’ll have to pick the appropriate transaction code before it gets sent.


email a report in Sage Enterprise Management (Sage X3)


Now, as soon as you click on the invoice button from the delivery function, it will automatically pop up the print parameters as well as an email to the contact with the buyer function from this specific customer when you choose to print.


email a report in Sage Enterprise Management (Sage X3)


It will automatically attach the document to the email like this:

email a report in Sage Enterprise Management (Sage X3)


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 ,  ...

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....

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  ...