# Changelog

This changelog documents material changes to the Flow Results specification. Versions of the specification adhere to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## \[Unreleased]

### Added

* Webhook block type within the Core namespace (`Core.Webhook`), for asynchronous or synchronous requests to external endpoints during Flow runs. [(#24)](https://github.com/FLOIP/flow-spec/issues/24)

## \[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. [(#53)](https://github.com/FLOIP/flow-spec/issues/53)
* Remove `config` on exits, as this seems to be unused and unecessary. Replace with `vendor_metadata` on exits. [(#57)](https://github.com/FLOIP/flow-spec/issues/57)

### Added

* [API Specification](/flow-specification/drafts-1.0.0-rc3-1/api-specification.md) for publishing, listing, and running Flows on external systems. [(#58)](https://github.com/FLOIP/flow-spec/issues/58)
* 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 [(#55)](https://github.com/FLOIP/flow-spec/issues/55)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://floip.gitbook.io/flow-specification/drafts-1.0.0-rc3-1/changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.