Jump to: navigation, search


Section: cview
Default Value: No default value
Valid Values: long
Changes Take Effect: Immediately

Time in seconds to wait to auto-complete the service after its last update if auto-complete-enabled = true. This option value is used if it is not explicitly provided in the Start request by setting the auto_complete_after parameter of the Service Start Event. If you do not provide a value for auto_complete_after in the configuration or in the Start request, then only an explicit API call to complete the service will be able to terminate the service.


Section: cview
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Related Feature: auto-complete

If true, enables the auto-complete feature. If a service or its states or its tasks are not updated within the period specified by the option auto-complete-after, the service (including states and tasks) is terminated.

Auto-Completing Services

Added in 8.5.111

Instead of manually completing a service, you can enable the auto-completion by setting the auto-complete-enabled option to true and by configuring an auto-complete-after time in your application configuration. In this scenario, the system will wait the given auto-complete-after time to complete the service after its last update and/or the last updated to its nested states and tasks.

For example, to auto-complete a service that is inactive more than 20 seconds, use the following configuration in your Context Services application:

auto-complete-enabled= true

Note that you can override this configuration in the REST query that starts the service.

If you modify the auto-complete-after configuration parameter at runtime, only the new services will use its new value for auto-completion. Services that were created before the value changed will keep on using the former default value.
This page was last edited on September 7, 2018, at 12:58.
Comments or questions about this documentation? Contact us for support!