Stable Version 1.0.1 (OutSystems 11)
Published on 30 December 2018 by 
Stable Version 1.0.1 (OutSystems 11)
Published on 30 December 2018 by 
Created on 07 December 2018


Component for registering Architecture, Design or Implementation Decisions. See Documenting Architecture Decisions Application Image: Designed by Photoroyalty / Freepik
Read More

Ever wondered why a certain choiche was made? Keeping track of decisions can be a problem. With the decision register you can keep track of all the decisions that are relevant for your project, product and enterprise. 

Decision Register supports the life cycle management and disclosure of enterprise decisions.

You may define your own decision categories to classify the decisions. For example:

  • Enterprise Architecture
  • Information Systems Architecture
  • User Experience
  • Etc

There are three roles defined:

  • Decision Maker: A person who manages the decision lifecycle.
  • Decision Executer: A person who has to apply the decisions.
  • Decision Register Admin: Decision Register administrator. For configuring the Decison Register and maintaining generic data  such as Decision Categories.

Use the site property EnterpriseName to set the enterprise name.

What’s new (1.0.1)

Minor changes to the DecisionDetail to make it more clear that the CKEditor input fields are input capable.

Reviews (1)
in version 1.0.0
Good initiative, only suggestion I have is to make it visually more clear that there is an input area for  the Context, Decision and Consequences text areas.
Development tools, Architecture
Support Options
This component is not supported by OutSystems. You may use the discussion forums to leave suggestions or obtain best-effort support from the community, including from Paul Schmeddes who created this component.
See all 2 dependencies
Component Consumers
No consumers yet.
Weekly Downloads 
More from Paul Schmeddes