Messages

Hi again,

Scenario: I have a bundle consisting on a product with a service and the product has several options. The product cannot be bought by itself.

Is there some OOTB way of buying the bundle while choosing it's product options ? I noticed than on the OOTB Store you can't choose the bundles inner products' options.  I wouldn't want to have several bundles consisting in Service+ProductOptionA, Service+ProductOptionB, Service+ProductOptionC or have to replicate all the product options in the bundle. Both these options don't look very maintainable when you have bundles with many products with many options with many possibilities (just the extreme case..)

Just looking for some other possibilities before starting right away to use custom properties or digging on the SQL's.

Hi there,
I was getting into the API customization (via the User Guide) and some questions came up.

1) If I want to use the custom engine API, I need to explicit call the custom constructor ?

Code Select Expand

engine_ = new KKCustomEng(engineConfig);
Or I could/should just edit the properties file ? konakart_app.properties:

Code Select Expand

konakart.app.engineclass=com.konakart.app.KKCustomEng

I was hoping just to use the properties file, but couldn't make it work. It can be just some bad configuration/wrong file issue, just trying to confirm it.

2) Is the supported customization based exclusively on the Custom.java file with the custom(String a, String b) function (and it's secure relatives) ?
As you say on the User Guide, we can use the two arguments to say the function and parameters to be called, via XML or JSON or something like that, but that isn't very "pretty" when working with several parameter and return types.
Isn't it possible to add our own functions to the custom engine KKCustomEng ? We could add another interface (KKCustomEngIf) to "share" our custom functions and make KKCustomEng implement it, so that we didn't need to make modifications on the default interface KKEngIf.

Thank you.

Hi,

I recently started to work with KK trying to implement a shop-solution where the customers will be companies/business entities. Eventually, one company may have multiple employees in charge of making their orders, so I've been looking around (admin application, user guide, forum) searching for any kind of native support of having multiple user accounts belonging to a same customer. The closest thing I've found were the customer groups, but it looked like that's more fit to grouping users with some attributes, differentiating products for groups, stuff on a sales/shop perspective. 

For example, all registered employees of the same company should be able to see the company orders, only one registration for the company (address, phone, etc.) is needed, etc.

Any hints on that ?

Thank you.