Checks the defined synchronization and waits for it.

A synchronization is defined thanks to the Synchronization property. This statement does no action but waits for the synchronizer to return.
There are four types of synchronizers, see their definitions in Synchronization property description.

Property Type Category Description
Comment String standard Describes the object comment to include in the documentation report.
This property generally contains an explanation about the object.
Is active boolean standard Defines whether the statement is active.
Synchronization TriggerXMLizer standard Defines how to synchronize the statement.
A synchronizer states how and when accessed pages are considered fully loaded. Only then are data extracted and new pages re-detected.
There are several types of synchronizers, that are described hereafter:

• Document completed: The synchronizer waits for a number of documents to be completed. Specify here how many “document completed” events Convertigo has to wait for before assuming that the page is complete. In many cases, when the target application uses HTTP META redirects or JavaScript redirects, the document is loaded several times. You can monitor
==== start parse ======
and
==== Parse end ==(XXXms )====================
traces in the Engine console (debug mode) to count the number of “document completed” events needed for the synchronizer. The Document completed synchronizer can be configured to also stop on alert messages that could pop up. Alert messages do not trigger a “document completed” event and are not detected by this synchronizer. To activate this option, check the Stop on alert checkbox.
• XPath: The synchronizer waits until a specified XPath is found. Convertigo tries to evaluate the specified XPath while receiving a web page or executing JavaScript in it. Once the XPath matches at least one node of the page, the synchronizer returns.
• Wait time: The synchronizer waits until a specified time is reached (in ms, set via the Timeout property).
• Screen Class: The synchronizer waits for one of the selected screen classes to be detected. Several screen classes can be selected to be waited for. The synchronizer returns when one of them is reached.
• Download started: The synchronizer waits for a download request. This is the perfect synchronizer to use before a Get attachment statement.
• No wait: The synchronizer doesn’t wait and execution proceeds directly.

For all synchronizer types, the maximum waiting time is set using the Timeout property.