An open API service indexing awesome lists of open source software.

https://github.com/ekoindia/interaction-framework-spec

A framework to describe financial transactions and product-flows to automate user-interfaces for financial products.
https://github.com/ekoindia/interaction-framework-spec

automation documentation eko financial-services mysql-schema

Last synced: 12 days ago
JSON representation

A framework to describe financial transactions and product-flows to automate user-interfaces for financial products.

Awesome Lists containing this project

README

        

# interaction-framework
A framework to describe financial transactions and product-flows in order to automatically generate UI for financial products.

[![GitHub issues](https://img.shields.io/github/issues/ekoindia/interaction-framework-spec)](https://github.com/ekoindia/interaction-framework-spec/issues) [![GitHub license](https://img.shields.io/github/license/ekoindia/interaction-framework-spec)](https://github.com/ekoindia/interaction-framework-spec/blob/master/LICENSE)
![Eko.in](https://img.shields.io/badge/Develop%20with-Eko.in-brightgreen)
Twitter
![Twitter Follow](https://img.shields.io/twitter/follow/ekospeaks?label=Follow&style=social)

---

## Reference
* [Schema (YAML)](https://github.com/ekoindia/interaction-framework-spec/blob/master/schema)
* [Documentation (Table Structure)](https://github.com/ekoindia/interaction-framework-spec/blob/master/doc/README.md)

## Introduction
_WIP_

## Features
* **Transactions**
* **Request**
* **Responses**
* **Parameters**
* Complex Validations
* Data Type
* Secure/Masked _(eg: password)_
* UI-agnostic Formatting: (Text-Case, Emphasised, etc)
* **Flow**: Define a user's journey for a product by chaining one or more transactions after a certain response.
* Parameter Chains: Pass data along a user-journey
* Direction: Go forward or back to a previous step in a flow.
* **Internationalization**
* **Expressions**: Enables defining of basic logic by making arithmatical or logical calculations.
* **Roles**: Map transactions (products) to roles to enable access control.
* **Reusable Components**: Components like parameters, responses, etc, can be reused
in multiple transactions.