Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
a_f:a:send [2022/09/01 01:23] – removed - external edit (Unknown date) 127.0.0.1a_f:a:send [2023/05/09 01:45] (current) – sean
Line 1: Line 1:
 +{{tag>Index Action Action_List Service Process Business_Rule}}
 +====== SEND ======
  
 +This action allows sending a notification to a particular notification receiver. 
 +
 +===== Syntax =====
 +
 +''SEND'' Id() ''TO'' AttributeIdentifier () [ ''VIA'' ChannelName ] [ ''USING'' AttributeIdentifier () ]
 +
 +===== Example =====
 +
 +<code aim>SEND ReservationOfferEmail TO Reservation.Member </code>
 +
 +Note that the receiver of the notification must be an intelligent business object with active communication channels.
 +
 +The ''VIA'' keyword can be used to indicate the specific channel through which the notification will be sent, for example 
 +
 +<code aim>SEND ReservationOfferNotification TO Reservation.Member VIA Email </code>
 +
 +If the ''VIA'' keyword is not specified, the default channel of the business object is used.
 +
 +The ''USING'' keyword can be used to send emails using a particular email account, for example:
 +
 +<code aim>SEND ReservationOfferNotification TO Reservation.Member USING EmailAccount </code>
 +
 +Here the instance of the EmailAccount object is taken from the Context and it should contain email account values to use when sending an email (host server, port, authentication details etc). Therefore, the object representing an account must have certain attributes defined. The definition of such an object can be created in the Configuration Tool using the “Add Outgoing Email Account” command.
 +
 +When processing incoming emails (in the rules attached to the IncomingEmail notification), the reply can be sent to the predefined business object called EmailSender. 
 +
 +For example,
 +
 +<code aim>SEND Reply TO EmailSender </code>