Difference between revisions of "Process Gear in Window"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→Contributors) |
(→Status) |
||
| (17 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
== Status == | == Status == | ||
In Production use | In Production use | ||
| + | |||
| + | * JIRA: https://adempiere.atlassian.net/browse/ADEMPIERE-190 | ||
| + | * Mercurial branch: https://hg.code.sf.net/p/adempiere/code branch ADEMPIERE-190 | ||
== Contributors == | == Contributors == | ||
| Line 6: | Line 9: | ||
== Overview == | == Overview == | ||
| + | * Possibility to define and call processes from Process Gear Icon for each Window. | ||
| + | * Icon is displayed in each generic window. If a process is defined for the window, then the Process is displayed behind Process Gear Icon automatically and can be used from there. | ||
| + | * This Functionality was implemented to avoid time consuming creation of Buttons in each window where certain processes shall be provided. | ||
| + | '''An example of how to assign:'''<br> | ||
| + | <br> | ||
| + | [[File:ADEMPIERE-190 Window.png]] | ||
| + | <br> | ||
| + | <br> | ||
| + | <br> | ||
| + | [[File:ADEMPIERE-190 Assign Process.png]] | ||
| + | <br> | ||
| + | <br> | ||
| + | '''And the result:''' | ||
| + | <br> | ||
| + | <br> | ||
| + | [[File:SuperUser_(System_Administrator)_@_System.png]] | ||
| + | <br> | ||
| + | <br> | ||
| + | For testing this, We assigned the process "Copy Window Tabs" to the table Window. This can now be run from the gear.<br> | ||
| + | <br> | ||
| + | <br> | ||
| + | [[File:Window,_Tab_%26_Field_Window,_Tab_%26_Field_SuperUser_(System_Administrator)_@_Sys_2013-06-28_16-19-28.png]] | ||
| + | <br> | ||
| + | <br> | ||
| + | |||
== Purpose == | == Purpose == | ||
== References == | == References == | ||
| Line 14: | Line 42: | ||
== Glossary == | == Glossary == | ||
==Functional Requirements== | ==Functional Requirements== | ||
| + | == Functional team == | ||
| + | *Volunteers for analyzing: | ||
| + | *Result of analysis: | ||
===User roles & profiles=== | ===User roles & profiles=== | ||
===Business process definition=== | ===Business process definition=== | ||
| Line 19: | Line 50: | ||
===Functional requirements based on business processes=== | ===Functional requirements based on business processes=== | ||
====User Interface Mockups==== | ====User Interface Mockups==== | ||
| + | |||
== Acceptance criteria == | == Acceptance criteria == | ||
== QA and test cases == | == QA and test cases == | ||
== Development infrastructure == | == Development infrastructure == | ||
== Technical Requirements == | == Technical Requirements == | ||
| + | == Technical team == | ||
| + | *Volunteers for analyzing: | ||
| + | *Result of analysis: | ||
| + | |||
== Data Requirements == | == Data Requirements == | ||
==Non-Functional Requirements== | ==Non-Functional Requirements== | ||
==Open Discussion Items== | ==Open Discussion Items== | ||
==Closed Discussion Items== | ==Closed Discussion Items== | ||
Latest revision as of 13:31, 17 September 2013
Contents
- 1 Status
- 2 Contributors
- 3 Overview
- 4 Purpose
- 5 References
- 6 Design Considerations
- 7 Glossary
- 8 Functional Requirements
- 9 Functional team
- 10 Acceptance criteria
- 11 QA and test cases
- 12 Development infrastructure
- 13 Technical Requirements
- 14 Technical team
- 15 Data Requirements
- 16 Non-Functional Requirements
- 17 Open Discussion Items
- 18 Closed Discussion Items
Status
In Production use
- JIRA: https://adempiere.atlassian.net/browse/ADEMPIERE-190
- Mercurial branch: https://hg.code.sf.net/p/adempiere/code branch ADEMPIERE-190
Contributors
Overview
- Possibility to define and call processes from Process Gear Icon for each Window.
- Icon is displayed in each generic window. If a process is defined for the window, then the Process is displayed behind Process Gear Icon automatically and can be used from there.
- This Functionality was implemented to avoid time consuming creation of Buttons in each window where certain processes shall be provided.
An example of how to assign:
And the result:
_@_System.png)
For testing this, We assigned the process "Copy Window Tabs" to the table Window. This can now be run from the gear.
_@_Sys_2013-06-28_16-19-28.png)
Purpose
References
Design Considerations
Assumptions
Dependencies
Constraints
Glossary
Functional Requirements
Functional team
- Volunteers for analyzing:
- Result of analysis:
User roles & profiles
Business process definition
User stories
Functional requirements based on business processes
User Interface Mockups
Acceptance criteria
QA and test cases
Development infrastructure
Technical Requirements
Technical team
- Volunteers for analyzing:
- Result of analysis:
