Install and Configure SMTP in IIS 6 by using GMAIL Account

You can use your gmail as relay server to allow email to be sending out from X3 workflow. To enable it, you need to turn on 'Allow less secure apps' in your gmail account setting.

In order to use SMTP relay server Windows Server 2012 , you need to enable SMTP server and Telnet Client in Add roles and features wizard.

Once SMTP installed, go to IIS6.0 Manager, select the IP Address.

Go to Delivery tab, click on outbound security button. Enter your gmail account and password. Tick TLS encrytion.

On same Delivery tab, click on outbound connection button, change the port to 587.

Click on Advance button, change the smart host to smtp.gmail.com. You may reset IIS and start SMTP virtual server once it's done.

To use Sage X3 workflow emailing, you have to login X3, set up parameters value, configure workflow rules and user assignment.
Go to parameter values, select Supervisor > Folder, select Workflow and click Detail in action menu. Assign server name for SERMES value, and create a new folder for workflow link directory WRKRMTDIR (this folder is to keep the approve or reject item for workflow process).

You need to turn on workflow signature in parameter values also in order for the workflow to be working. Example below are the workflow for purchase request and purchase order.

To take purchase request as example, you need to make surePR Signature Management PSHSIG workflow is active. In User Assignment, assign requester = ERP, and user 1 recipient = ADMIN.

Create new administration user 'ERP' to link it to to ERP endpoint user.

Assign a valid email to ADMIN endpoint user.

Add remote signature task into recurring task management. Make sure server task is activated.

Create a new purchase request record.

You should able to see the sender is ERP and recipient from Signature History at right panel.

Email will be sending out to recipient email as screenshot below.

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

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

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