Difference between revisions of "Memo Alert"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Functional team)
(Functional team)
Line 13: Line 13:
 
==Functional Requirements==
 
==Functional Requirements==
 
== Functional team  ==
 
== Functional team  ==
*Volunteers for analyzing:
+
*Volunteers for reviewing:
 
** [[User:mar_cal_westf|Mario Calderon]] 12:00, 24 June 2013 (UTC) - Functional Review
 
** [[User:mar_cal_westf|Mario Calderon]] 12:00, 24 June 2013 (UTC) - Functional Review
 
===Result of review by Mario Calderon, June 22th, 2013===
 
===Result of review by Mario Calderon, June 22th, 2013===

Revision as of 11:19, 24 June 2013

Status

Contributors

still gathering info .. pls leave for later

Overview

Purpose

References

Design Considerations

Assumptions

Dependencies

Constraints

Glossary

Functional Requirements

Functional team

  • Volunteers for reviewing:

Result of review by Mario Calderon, June 22th, 2013

  • This contribution allows to issue an alert text when selecting a Business Partner in any window
  • Configuration (in Application dictionary)
    • Select window and column of field (e.g. Sales Order, Business Parter)
    • In Reference Key, check Alert
  • Configuration (as GardenAdmin)
    • Open Business Partner window
    • Go to Tab Memo
    • Check Alert check box, type in alert text in field Comments
  • Usage (as GardenAdmin)
    • Create a Sales Order
    • select a Business Partner
    • Alert text pops up
  • Questions
    • Does it only work for Business Partners? Or can the Memo tab be attached to any object, like Warehouse, Product, etc?
    • Does it only works for reference Table direct reference keys? What if I use Search?
    • How do the other fields of the Memo (User, Product, Campaign, Activity, Project) influence the functionality?

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:

Data Requirements

Non-Functional Requirements

Open Discussion Items

Closed Discussion Items