merkalt:business_process_of_application
This is an old revision of the document!
- Load Instance setup
- load configuration for instance = profile (currency, motifs, colors, etc)
- load localization data - messages.xml
- load Products set.
- load additional product options - colors, background colors, sizes used
- load coupons discount
- setup available payments data
- Operations with labels
- Order Processing
multitabs problems
- currently we have a list of labels for order indexed as 1, …, n. This should be somehow saved as it is used for non - empty checkout before order process. Also this procedure should be modernized to use different profiles for checkout
- Label rendering uses currently only current profile. There should be support for multi-profiles usage
- products/orders to profile relations. Different instances have different setups of ordering data handling
- coupons/discounts schema, Currently it only applies to the certain instance
Suggestions
The main problem is that current approach is instance-based. All logic is processed inside one instance. Multi-tabs process assumes that we have global setup with variations between instances. We have no such setup at this time. Global setup assumes at least such changes
- Linking of product to instance before the order
- Linking of order to instance before the order
- Ability to change profile “on-the-fly” with js AJAX
- Global schema for coupons
merkalt/business_process_of_application.1355147084.txt.gz · Last modified: (external edit)
