Whenever I set some hero products in a sequence in Backoffice cockpit in the Stage product catalog, after synchronization from Stage -> Online set of Hero Products in the Online catalog is not reflecting the same sequence as set in Staged.
Although "SolrHeroProductDefinition" is added in the synchronization properties, this issue is being observed.
Expectation is whenever I create or update the sequence of hero products in staged catalog, then after catalog sync, the same sequence should reflect in its online verion.
Any solution to this would be helpful.
Please note that we are facing this issue in Hybris version 5.5.
Related
​Context:
I have an organization with multiple projects. Some projects use a tag to identify Epics and Features in scope where others use a relationship to a Strategic theme to identify the scope.
ASK:
I have been asked to setup two consolidated boards in Azure Devops that can show all Epics and Features. I've tried to use the query feature, but I can only identify Epics and features based on Strategic Theme in the "Tree of work item" query type where Boards are not supported.
Based on your experience is there a workaround to create consolidated boards based on Strategic Themes showing all associated child Epics or Features? Or do I need to use tagging + querying to achieve this?
Thank you in advance
I am afraid you have to use tagging and querying. If you just need to show all the Epics and Features in a board. You can check out Query results widget on the Dashboards under Overview in Devops project UI page.
You can create queries to query all the Epics and features based on Strategic Theme or tags. And display the query result on a widget on the Dashboards.
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.
After drawing the following UC Diagram, I right click on an use case and send it to the backlog
It appears as a new activity in the product backlog, like this:
So I move it to the board and create a task and an epic underneath:
Then I go on creating the User Stories for the new topic called "Plugin Deployment":
Everything works great so far, I can even edit the conversation and confirmation items:
The problem
As soon as I activate the tab "scenario", the current story, which so far I thought I associated with the "Plugin Deployment" use case, appears under a new model "General User Stories":
What can I do to organize the stories inside my model in the proper way? What does Visual Paradigm 14.1 Professional Edition expect from me? Any ways to circumvent this problem? I don't want to end up with hundreds of user stories there.
The user stories in Visual Paradigm actually is a kind of server side model where the modifications are directly synchronized to server. They should not be showing in Model Explorer since it is only for showing the model element located within the local project file. The linkage between model element and user story are established with the User Activity in story map via the Send to Product Backlog (which you already did). You can always navigate from model elements in diagram to User Activity created to story map using the Send to Product Backlog via the Open in Scrum resource icon, and then traverse down to User Task, Epic and then to User Story.
BTW the latest patch build of v14.1 SP1 already enhanced the Model Explorer to hide out the user stories. This should to avoid confusion to user. You can contact Visual Paradigm Support Team for details about how to update the software to latest patch build.
Product , catalogs etc both staged and online we have in Hybris...If we want show online the staged one we do synchronization but why we need staged products or catalogs?
Modifications of - Content, Product, Media,... - are made first in the staged catalog.
When changes/modifications are tested/approved and you are satisfied then you publish them to be available online to your users by synchronizing staged catalog to the online catalog.
Imagine if you have one single catalog, your users will be able to see unapproved and untested changes immediately, that's will increase the amount of risks and errors significantly.
You allow the merch team to upload the proper visual, modify product texts etc... Then they can also test product pages with various device without any impact on the online website (online catalog).
It also allows to prepare seasonal catalog. For exemple you're in summer and you can start to work on the online version to be deployed on winter.
Stage catalog is the one on which you work - change the data, etc. This catalog is not displayed in the storefornt.
Online catalog is used in the storefront and should not be manually edited.
Usually there is synchronization between Stage and Online versions so that when the changes are approved for showing to the customers the synchronization is triggered and the products are available in the Online catalog (which implies storefront visibility).
Two custom entities "Detailings" and "Project Managements". The project management is the parental relationship to the detailing. I'm trying to create a workflow for when fields change in project management to update fields in detailings. However detailings is not an available related entity type in the process. What am I missing? See screen shots attached.![enter image description here][1]
You are not missing something. The OOB steps of a workflow don't permit to access to the related entities.
You need to install in your CRM a custom workflow activity, as this one:
http://crm2011distributewf.codeplex.com/
It will make you run a workflow for each related entity in order to update each single record.
The configuration requires a bit of technical knowledge, but in the bottom of the page there is also a link to download the instructions.