KEMBAR78
The Wait For File Change Activity | PDF
Scribd
Upload
50 views2 pages

The Wait For File Change Activity

The Render XML activity takes an XML schema element and renders it as an XML stream or string based on the specified XSD file. The Wait for File Change activity suspends process execution until a file creation, modification, or deletion event occurs that matches the specified key. The expression built for the Candidate Event Key should evaluate to a string and match the activity's input key, accepting the file change event.

Uploaded by

RameshCh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
50 views2 pages

The Wait For File Change Activity

The Render XML activity takes an XML schema element and renders it as an XML stream or string based on the specified XSD file. The Wait for File Change activity suspends process execution until a file creation, modification, or deletion event occurs that matches the specified key. The expression built for the Candidate Event Key should evaluate to a string and match the activity's input key, accepting the file change event.

Uploaded by

RameshCh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

The Render XML activity takes an instance of an XML schema element and renders it as a stream of bytes containing XML

or an XML string. The schema is


processed based on the XSD file specified

The Wait for File Change activity waits for a file creation, modification, or deletion event to occur during process execution.
When this activity is executed, the process instance suspends and waits for the specified change to occur before resuming.
Candidate Event Key:Expression built from the data of the incoming file change event. This expression should evaluate to
a string and it is compared to the "key" field of the activitys input. If the Candidate Event Key and the activitys key match,
then the process accepts the incoming file change event.
You should specify the contains(pfx2:EventSourceOuputTextClass/fileContent/textContent,
"approved") or contains(pfx2:EventSourceOuputTextClass/fileContent/textContent,
"delayed")for the Candidate Event Key field, and you should specify "true" for the "key" field on the Input tab.

concat($Parse-new-order-file/order/customer_name, ",&lf;Your order has been ", $Wait-for-Approval-FileChange/pfx2:EventSourceOuputTextClass/fileContent/textContent,"&lf;The cost is as follows, &lf;Purchase cost
: $", $Parse-new-order-file/order/total_price, "&lf;Shipping costs : $", $Calculate-Shipping-cost/shipping_costs,
"&lf;Total Cost : $", $Parse-new-order-file/order/total_price + $Calculate-Shipping-cost/shipping_costs)
T

You might also like