Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0023405
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Retail Modules] Web POSmajorhave not tried2013-03-26 13:122013-03-26 13:12
ReportermarvintmView Statuspublic 
Assigned Tomarvintm 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0023405: Payment methods should be extensible without having to change the application dictionary

DescriptionCurrently, to add a new payment method to the Web POS, you need to create a new entry in the Application Dictionary, specifically in the Reference/List Reference window. This is because you also need to add a preference which is linked to a list property.

This is not a nice way to do this, because payment method information is not code, it's user information which should not require development actions to be implemented.
Steps To Reproduce.
Proposed SolutionA possible way to improve this would be to load not only the preferences related to Web POS dependant modules through the property, but also preferences which follow some naming convention related to Web POS payment information.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2013-03-26 13:12 marvintm New Issue
2013-03-26 13:12 marvintm Assigned To => marvintm


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker