on ‎2018 Feb 09 1:35 PM
IN PromotionSourceRule,conditions are represented in JSON. For an assumption,If at all, I consume a file (containing new products/conditions to be added to a new promotion) from external source , I will clone the relevant template and manipulate the JSON (conditions in PromotionSourceRuleModel), which is not appropriate solution.I would rather manipulate the condition data in database but I also found we are not persisting the conditions data separately in DB.
Basically,we want to have the flexibility of creating promotions with extensive data via external source - and not relying on creating promotions manually via backoffice.
Request clarification before answering.
Hi Raghavenda,
It may be convenient for your business managers to use hot folders - directories that are associated with predefined impexes and are processing CSV files that are put in them. This solution would work for them as long as they don’t try to create new types of promotions as this would require more programming work to define a new type. Tip: Hot folders accept CSV files without column names, process files periodically and for a file to be processed it is important for it to have a unique name - all files that were processed are placed in ‘archived’ or ‘error’ subfolder. If file lands in an error folder - rows are commented with a type of error.
See lessons: Creating hot folders: https://wiki.hybris.com/pages/viewpage.action?pageId=294094383
Best Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.