I have to implement product configurator in hybris platform that allowing users customization front office interface (product details).
Like changing color of product, size, make text and managing prices.
I'm looking actually for open source product desinger.
Anyone has an experience with any integrated framework or any other recommendations ?
Kind regards,
Soufiane
If you are not using SAP CPQ which is integrated with Hybris out of the box, you can have a look at openCPQ
Managing the sizes, prices etc of products is performed via the productcockpit. Changes you make here will be reflected in the Accelerator storefront. This is also extensible and customisable.
Related
I am looking for a Hybris OOTB extension that gives users manage categories at ease.
Category creation or update
Expand and lookup for super and subcategories and its products (Basic tree view in BackOffice is extremely slow and not friendly)
Basic export functionality
Is there any cockpit or BackOffice extensions you recommend that I should take a look at.
In the newer Hybris version you only have the backoffice. There aro no other cockpits anymore.
When you login in the backoffice you can choose a 'mask' at the top of the backoffice (for example the Product-Cockpit). But the masks are still in the backoffice.
You could implement your own Category-Cockpit mask where you can handle your use-cases.
Keep in mind that for the backoffice there is a own Solr Config for Backoffice index which is created to handle the belonging data in the backoffice fast. So maybe in your case it makes sense to add the categories here as well for faster access.
Try adding the platformbackoffice and pcmbackoffice extensions. The Products view and Assortment view should be useful.
We have a custom solution made up of several screens that are packaged as a customization package. We'd like to be able to lock that down so that users need to purchase a license key to use these screens. I don't want to re-invent the wheel, so I'm wondering if there are standard examples (if this has been done before) on how to integrate this with Acumatica's license system.
It is not possible to integrate with the Acumatica licensing system. We implemented our own licensing and required the license when the Acumatica license has been applied. This is indicated by PXLicenseHelper.License.Licensed
I should point out I did spend a good amount of time on this very question before we implemented licensing for our product.
Recently i've started learning hybris and come across these two terms.I feel both are same because they both are related to User Interface.
somebody please help me understand how backoffice and cockpit are different.
Since Hybris 6, Backoffice is the new more generic UI for managing your Hybris Store. This is the successor of HMC. (Hybris Management Console) Cockpits will become deprecated in a few versions. Using them, you have to handle several different extensions (Product Cockpit, Customer Service Cockpit, CMS Cockpit etc..), which use different frameworks and styles.
The main idea of having different cockpits is to separate different dedicated teams and concerns. Also they have some customizations, which are much more usable, than HMC. With Backoffice, you can create the same functionality with different modules.
In general, if you start a new shop, i would recommend using the Backoffice. This is the new way to administrate you shop.
backoffice is a new framework which is a replacement for old cockpits.
backoffice advantages:
the new architecture allows developer to focus and spend more time on important things (application logic) instead of all secondary tasks (e.g. security - authentication and authorization, notifications etc.)
it offers a lot of standard reusable components so you can create new applications faster (from ready blocks):
actions: create, delete, search etc.
editors: decimal editor, text editor, reference editor etc.
widgets: collection browser, border layout, explorer tree etc.
your applications will be more consistent and intuitive, because they use the same components
it groups applications in one place, so the client does not need to know many URLs (he can open one application and everything will be in one place)
Hi I am looking for a CMS, that would allow me to add/view items based on categories. Just like a shopping cart but much simpler than that. I am working on a project which requires to categorize Movies based on their genre. So, there will be categories like Action, Romance,etc. Under each category, I need to display an image/video and some text regarding the movie. Which CMS would allow me do this?. Thanks in advance
I suggest you to use Joomla for your requirement. Joomla have lot of components and modules for your requirments.
Better you go with Joomla.. :)
This Joomla plugin has all privileges to fulfill your requirement.
Click here
Our company already has a CMS that facilitates this. One of clients is an video/games and entertainment company with an online e-commerce site.
You can contact us via our website www.monadel.com.
However, we are B2B and you may be looking for freeware - which we are not currently offering.
Wishing you success in your endeavours.
Let's assume that you've created a SharePoint solution - a WebPart, a feature for a List Template, whatever - that you are planning to sell as a product.
How would you go about handling licensing of your solution?
I'm looking for some input in at least the following areas:
Code-wise:
1.1. Where do you keep the license itself? as a file somewhere? (then what happens in farms?) as a property in the property bag of the farm?
1.2. Do you implement "home-calling" - where your solution validate the license every now and then against your company's servers?
1.3. Any other best practice in this area will be welcome...
Business wise: How do you license - per user? per server? per instance (in case of WebParts or List Templates)?
Thanks.
I could tell you what we do:
We have a separate farm solution that handles trial/registration support for all our products
The license is eventually stored in the farm property bag (you have to support multiple servers)
We have a page to enter license key under the central admin solution's page
We license by front-end, you can know the number of front-end in the farm in code.
All products have a product name and the license key is a one-way encryption containing the product name. the trial support solution handles key validation.
1.1 You have to put in in the documentation and in the distribution files.
1.2 I would not do that for a sharepoint web part.
1.3 Invest in layout, documentation, support... Not just in the product itself.
Nobody will be able to answer that without knowing detailed information about your product, your market, your competitors, the alternatives, etc. Consider this book if you are serious about pricing.