SEND

Contents


Send is used to send a message.

Syntax

   Send id_server with param_list

Parameters

Element

Description

Restrictions

id_serveur

identification of a print server as:
machine.domain@

list_param

List of id_param separated by the character ','.

The expressions must be alphanumerical and are limited to 255.

Examples

# Sending a message to Smith and Chang, with Grey in copy
# with the possibility to start X3 in customer management
# with an attachment file1.zip
Send GSERMES With
& "__TO="+chr$(1)+"Smith;Chang",
& "__CC="+chr$(1)+"Grey",
& "__SUJET="+chr$(1)+"message title",
& "__NOTE="+chr$(1)+"message text",
& "__CONTXT="+chr$(1)+"GESBPC",
& "__JOINT="+chr$(1)+"C:\Tmp\file1.zip"

# this can also be expressed as follows:
Local Char ENVOI(64)(1..6)
ENVOI(1) = "__TO="+chr$(1)+"Smith;Chang
"
ENVOI(2) = "__CC="+chr$(1)+"
Grey"
ENVOI(3) = "__SUJET="+chr$(1)+"
message title"
ENVOI(4) = "__NOTE="+chr$(1)+"
message text"
ENVOI(5) = "__CONTXT="+chr$(1)+"GESBPC"
ENVOI(6) =
"__JOINT="+chr$(1)+"C:\Tmp\file1.zip"
Send GSERMES With ENVOI(1..6)

Description and comments

TheSend instruction is used to send a message to one or several recipients.

It is possible to enclose:

The __SUJET parameter is limited to 63 characters.
The __NOTE parameter is limited to 2,500 characters if there is no associated attachment, 1,300 characters if there is an associated attachment 

For each parameter, the expression must be alphanumerical and limite to 255 characters max. To go beyond this limit, the syntax is the following:

Send GSERMES With
& "__TO="+chr$(1)+"Smith;Chang",
& "__CC="+chr$(1)+"Grey",
& "__SUJET="+chr$(1)+"message title",
& "__NOTE="+chr$(1)+"message text",
& "__NOTE="+chr$(2)+"message text continuation 1 ",
& "__NOTE="+chr$(3)+"message text continuation 2 "

The parameters to be entered to send a message are the following:

Parameter

Description

__TO

Message recipients

__CC

Copied recipients of the message

__SUJET

Description of the message subject

__NOTE

Message content

__JOINT

Attachment

__CONTXT

Application context
attachment used to start X3 and position onself directly in a particular context

__ACKNOWLEDGE

Request for an acknowledgement of receipt
"0" or parameter missing: no request for an acknowledgement of receipt
"1": request for an acknowledgement of receipt

Remarks

In the standard message transmission process, the name of the messaging service is loaded by the SERMES parameter of the Supervisor module.

When the parameters are sent in the form of a grid, all the elements in this grid must be entered.
For instance:

Local Char ENVOI(64)(1..6)
ENVOI(1) = "__TO="+chr$(1)+"
Smith;Chang"
ENVOI(2) = "__CC="+chr$(1)+"
Grey"
ENVOI(3) = "__SUJET="+chr$(1)+"
message title"
ENVOI(4) = "__NOTE="+chr$(1)+"
message text"
ENVOI(5) = "__CONTXT="+chr$(1)+"GESBPC"
ENVOI(6) =
"__JOINT="+chr$(1)+"C:\Tmp\file1.zip"
Send GSERMES With ENVOI(1..6)

Caution! In the presence of a parameter whose part located after the chr$(1) is empty, there may be a serious Windows error. 
For instance:

# To avoid:
...
ENVOI(2) = "__CC="+chr$(1)+""
...
Send GSERMES With ENVOI(1..6)

New to version 140

Addition of the __ACKNOWLEDGE parameter. 

Associated errors

Error

Description

 

 

Associated keywords

Seldest


CONTENTS

Copyright © Sage 1999 - 2007