Changes

Workflows Overview

16 bytes removed, 18:24, 13 March 2018

→‎Task Type: Web Service – SOAP Message

* '''Message Template: Custom Field ID for Response''' - The Custom Field ID of an XML custom field on the object that the Workflow was triggered against that the response returned by the external server.

* '''Message Template: Email Message Header''' - The email header can be modified using the following syntax, with the arguments separated by semicolon:

:** X-Priority={1,2,3,4,5}:** Priority={normal,urgent,non-urgent}:** Importance={high,normal,low}:** Sensitivity={personal,private,company,confidential}::: e.g. Priority=urgent;Importance=high

:** '''Message Template: Endpoint''' - The URL or IP address of the destination server:** '''Message Template: Envelope Template''' - The content of the Web Service message to be sent to the external service. This can contain variables related to the object the workflow is triggered against.:** '''Message Template: Attach Object''' - Attaches the details of the object to the message. In the case of a SmartSimple object, such as a company, person, or application, the textual details of the object will be added. If the object is a file, then the file will be attached to an e-mail message, but not an instant message.:** '''Message Template: Attachment File IDs''' - Attach additional default files when triggered from a Smart Folder. See the Determining the File ID article for instructions.:** '''Message Template: Save as Event''' - Email will be saved as an event.

If the content from the custom fields being included within the SOAP message contains certain special characters it will disrupt the XML structure, making the message unreadable by the receiving server.

@system.xml.''fieldname''.''nodename''.nodevalue@

 

===Task Type: Translate Field Value===

• ← Older edit
• Newer edit →

Ciaran Donnelly

Smartstaff, administrator

4,478

edits