Flow Specification
drafts/1.0.0-rc3
drafts/1.0.0-rc3
  • Introduction
  • Changelog
  • Glossary and Definitions
  • Flow Fundamentals
  • Expressions
  • Layers
    • Layer 1: Core
    • Layer 2: Console IO
    • Layer 3: Mobile Primitives
    • Layer 4: Smart Devices
  • API Specification
Powered by GitBook
On this page
  • [Unreleased]
  • Added
  • [1.0.0-rc3] - 2021-07-30 (proposed)
  • Changed
  • Added
  • [1.0.0-rc2] - 2020-06-30
  • Added
  • Changed

Was this helpful?

Changelog

PreviousIntroductionNextGlossary and Definitions

Last updated 3 years ago

Was this helpful?

This changelog documents material changes to the Flow Results specification. Versions of the specification adhere to .

[Unreleased]

Added

  • Webhook block type within the Core namespace (Core.Webhook), for asynchronous or synchronous requests to external endpoints during Flow runs.

[1.0.0-rc3] - 2021-07-30 (proposed)

Changed

  • SelectOneResponse and SelectManyResponse block types: Introduce a test-based system for mapping responses received via text, IVR, and other channels to choices in a standard way. Restructure choice definitions from a map of [{choice-name: resources}] to a structure that is easier to work with in Javascript.

  • Remove config on exits, as this seems to be unused and unecessary. Replace with vendor_metadata on exits.

Added

  • for publishing, listing, and running Flows on external systems.

  • Add additional "test" functions for interoperability with RapidPro

[1.0.0-rc2] - 2020-06-30

Added

  • Added tags to blocks for semantic categorization

  • Positions (x,y) of Blocks on the canvas added in a standard part of the spec (ui_metadata instead of vendor_metadata)

Changed

  • exit.tag renamed to exit.name for consistency with Flows and Blocks

Remove exit.label as there is no need for a translated resource of exit names

Semantic Versioning
(#24)
(#53)
(#57)
API Specification
(#58)
(#55)