Calendars, Schedules, Tasks, and Triggers › Administer Triggers › How File and Mail Triggers Work › XML Content Format for File and Mail Triggers

XML Content Format for File and Mail Triggers

External applications that use file or mail triggers to start CA Process Automation processes must create input in a valid XML format. XML content can be written to the body of an email or sent as an attachment. If the XML is copied to the email body, it can contain no more than what is required to trigger a process. For file triggers, the triggering file must include the entire content.

An example of valid XML format follows:

<c2oflow version="1.0">
	<flow name="/Test/RunNotepad" action="start">  <!-- Full path of the process -->
	CA AuthMinder
		<user>pamadmin</user>         <!-- CA Process Automation Username  -->
		<password>pamadmin</password> <!-- CA Process Automation Password  -->
	</auth>
	<options>                       <!-- Optional parameters  for delayed execution -->
		<startDate></startDate>  <!—Start Date in [MM/dd/yyyy] format  -->
		<startTime></startTime>  <!-- Start Time in [HH:mm] format; HH in 24 hrs  -->
	</options>
	<params>                      <!-- Process initialization parameters, if needed  -->
		<param name="ParamOne">Using file trigger</param>
		<param name="ParamTwo">Second parameter from file trigger</param>
	</params>
	</flow>
</c2oflow>