View Source

Target release	Release name or number
Epic	Link to related JIRA epic or feature
Document status
Document owner	Unknown User (joewitt)
Designer	Lead designer
Developers	Lead developer
QA	Lead tester

Goals

Allow a dataflow manager to establish variables which map keys to values within a given process group and with transitive exposure to all groups below it.

Background and strategic fit

The value proposition of templates is harmed by the present inability to map environmentally specific things to specific values. If we allowed a given process group to have a map of variables then templates and flows can use these keys rather than specific values and thus be more portable. It also helps with DRY in configuration. With this mechanism we could automatically set the keys with empty values if not already present as a template is imported and prompt the user to set them thereby completing the configuration.

Assumptions

List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).

Requirements

#	Title	User Story	Importance	Notes
1	Short identifier for the story	Describe the user and what they are trying to achieve	Must Have	Additional considerations or noteworthy references (links, issues)
2

User interaction and design

Include any mockups, diagrams or visual designs relating to these requirements.

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome
(e.g. How we make users more aware of this feature?)	Communicate the decision reached

Not Doing

List the features discussed which are out of scope or might be revisited in a later release.