Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Help

Listen Activity

The Listen Activity is very similar to the Event Handling Scope Activity except it contains multiple parallel instances of Event Driven Activities. Which event is realized first decides which Event Driven Activity sequence is executed. All other Event Driven Activities are then cancelled. Using this mechanism a workflow can effectively listen for one or more events consecutively. Below is an example Listen Activity with equivalent pseudo-code:



WHILE TRUE
    
    
    IF EVENT timeout
    
        [Message Not Received...]
        
        BREAK
        
        
    IF EVENT message
    
        [Message Received...]
        
        BREAK
        
        
ENDWHILE
   

The example shows a simple timeout mechanism where if a message is not received within the time delay, execution will continue regardless.

For more information see Workflow Basics – Event Handling.