I have gone through all the formal definitions of these terms. But still, i have tough luck understanding them. I am a beginner in hybris. So Can somebody explain these concepts as simple as possible?
You must first understand the catalog concept in hybris.
The catalog in hybris, or anywhere in the world contains items for business. Therefore, Catalog in general, is the container of the commodities which are sellable entities (product) and which can be referred by the end users for transactions.
The catalog is not limited to just list of items, but how they are arranged also. Just an example, if you go to food restaurants, you can refer to their menu (that is actually a generalized catalog). You would notice that different restaurants, though serve the same food, but have different arrangement of items (products) in their menu - sometimes with different names, sometimes under different sections (categories). This is very similar to the hybris product catalog.
Now, taking the restaurant example further, Again two restaurants might serve the same food, but will have different ambience. This means the theme of the restaurant, the uniform of the waiters, the logos etc. This is similar to the hybris content catalog
Therefore, summarizing the above explanations, hybris has two catalogs - Product Catalog responsible for arrangement of the product hierarchy and the other as Content Catalog responsible for the layout (or the e-ambience) of the website.
Hybris Catalog has two versions - Offline (Staged) and Online. The business users work on the Staged version and push it (to) Online once the item under work (product or content) is suitable to go live. They do this via a process called Synchronization.
This process picks the items from Staged version, checks for some rules (which indicate that the item is ready to go live), and creates (or updates if already created) a copy of the item with Online as the version. Hybris system understands that only Online needs to go live, picks the item, and displays it on the website (storefront).
Now, there are some entities which should have two copies in the system, so that Business users (like content managers or product managers) can make appropriate changes to make it look suitable on the website before it actually appears there. E.g. - Product, Images etc.
But there are certain items which need not to have to copies of them, E.g. - Price, Stock etc. because they would be same for both copies of the item (Product in this case) and creating another copy would be an overhead on the system.
Therefore, the items that (should) take part in the synchronization process like Product, CMS Pages, Components etc. are called Catalog Aware.
The items which do (or should) not take part in synchronization process are called Catalog Unaware
Hope this helps!
In hybris one catalog can have different catalog versions. Product catalog has mainly 2 catalog versions — Staged and Online.
Staged Catalog — this catalog version is a test catalog version. Modifications 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.
Online Catalog — this catalog version is is the one which will be used to display on the storefront(the active one).
Related
Azure Devops Server Test plans: Is there any way to record manual Test case work items for the same product on separate projects to make them easier to relate/query?
I could modify the test case work item to include a product name, thus enabling creation of a query over all projects for a single product. Is the better way to handle this problem?
You can try the following methods:
Similar to as you have mentioned, you can add a same tag to all the of the Test cases for the same product. For example, you can use the product name as the tag. Then you can create a query to filter these Test cases across projects. For more details, see "Query across or within projects".
Another method you can try is to link all these Test cases for the same product with a same parent work item (such as an User Story). Then you can track and view all these Test cases under this parent. For more details, see "Link user stories, issues, bugs, and other work items".
We are working on implementing an architecture review which affects a specific subset of work items. I created the following query:
The result includes the downstream work items, which is what I want. However, it also includes the work items marked as with the Architect Decision, which I don't want. My ultimate goal is to see on a dashboard how many work items are blocked by architect decisions which are pending.
AzDO does not support that. If you want to see a plain list, you should use a flat query. As workaround, you may write your own job through REST API (as example):
Find epics, features, stories, and bugs without the Blocked by Architect Decision tag and with open work items contain the Architect Decision. Add to these work items the Blocked by Architect Decision tag.
Find epics, features, stories, and bugs with the Blocked by Architect Decision tag and without open work items contain the Architect Decision. Remove from these work items the Blocked by Architect Decision tag.
Then you can search your blocked work items with a flat query and the Blocked by Architect Decision tag.
The Rest Api methods:
Query By Wiql.
Update a work item tag.
Additionally, you`ll receive a notification when your work items are unblocked.
I am creating a website form my enterprise and I wonder how/how many snippets I should use on my homepage.
I know they are separate into multiple categories such as
local business or more generic organization, events, product etc.
I have read this post:
Homepage Rich Snippets
And this one:
Multiple Schema.org Product items & how will it look like in search engine result?
In my case on my homepage (let's say index.html) I want to present my activity, put some links to the services/products I propose, and show incoming events.
Which snippet(s) should I use?
1) Only one such as organization? (my services are not available directly so I suppose it is not a local business category)
2) Or should I put several snippets: organization + event + products
because all three categories are described/present on my homepage?
According to a Google employee, Google Search won’t show Rich Snippets for homepages. But this is not documented, and it might change anytime.
From the perspective of Schema.org, it’s fine to provide as much data as possible. If you have multiple entities on your homepage, you can use multiple Schema.org types to describe them.
If one of these entities can be considered the primary entity (for example, on an organization’s website it would typically be the entity for the organization itself), you can use the mainEntity property for it.
Domains are virtual view of a data source that presents the data in business terms, allows for localization, and provides data-level security. ADomain is a metadata layer that provides a business view of the data accessed through a data source
this is domain definition as in Jaspersoft reporting tool.
I am currently given the task to build or come with a design to create some domains in tableau.. (like in jaspersoft)
examples of domains in jaspersoft
In jaspersoft when you click on a domain : ex customer domain: you will see the list of tables (that are selected)
How to do the same in tableau?
Please guide me on this..
The meta data layers in Tableau are quite lightweight compared to other BI tools, which is ofter a plus, but seems to fight against your assigned task.
Usually the best approach in Tableau is to learn to use the tool well, build visualizations for your business domain, test and refine them, and then later focus on factoring out common meta-data as your Tableau projects grow. That tends to work better than insisting on a big meta data design up front approach.
Still as you learn to use Tableau, the features that you'll want to understand related to your question are everything about data connections (which define how to connect to a data source, and the fields, data types, calculations, groups, sets, field roles etc). You can start with a data connection in a single workbook and then save the connection separately (typically on the server) so that it can be shared among multiple workbooks (to reduce duplication). You can also use Tableau Server like a proxy for your database.
For security, you can look into the groups and access controls provided by Tableau Server, along with user filters.
Some of the features you ask about might be more properly relegated to the database server, such as by defining common views visible to different users.
I had a question on in-store pickup. I see that there is support for it in the CRS module (it has GeoLocatorService, GeoLocatorDroplet etc), but don't see any buttons or JSPs that display or let you use it out of the box. On the other hand, commerce service center has this functionality fully exposed, with in-store pickup buttons, popup widgets to search for stores and shopping carts showing store pickup line items etc. Looks like the web stores would need this functionality exclusively coded, which would involve creating JSPs and components as required.
Is there something I can copy over from CSC (commerce service center) that will enable store pickup in web module (store US or home US etc?) very quickly? Please let me know. Thanks for your response!
Not sure if you want to capture payment and collect from store , or reserve in store and pay when you pick up the item.
In both the cases your DOM (distributed Order Management) and WMS (warehouse management system) has important role to play. ATG can lookup the selected store inventory , both locally (location repository) or using realtime webservice interface to the system that manages your global inventory.
In all cases ATG will be able to capture the order, but this order has to be handled by DOM in such a way that its routed to local store for fulfillment. If by any chance this order is not available in local store, your DOM/ WMS system should be able to send order item to local store from warehouse or from another store.
Walmart has both the functionality available (click to collect and reserve and pay at store) , walmart has proprietary software DOM3 which eventually addresses these interfaces.
Please realize ATG is just your online order capture system, Click to Collect and any 'commerce anywhere' functionality must be offered by your DOM. if this is offered by your DOM , all you need to do is exchange messages with DOM to achieve this.
I am not sure if this answers your question, but its not recommended to over engineer ATG , and ATG should follow the heart beat of your DOM.
In Store Pickup - often called Click & Collect - has not been implemented as a feature in the CRS. It is also not in CSC either.
You will need to do quite a bit of customisation to support it.
The feature that is part of CRS is Store Locator. This allows you to find and view details of physical stores.
You can use this as a basis to build Click & Collect functionality.
Assuming that other back-end systems can handle it, and your business is set up to consider things like promotions, pricing etc. for a Click & Collect proposition...
Basically, you will need to implement a new Shipping Method, a New subtype of Hardgood Shipping Group that can use a Store Code instead of a Customer Address, as well as the UI to support choosing a store during checkout.
Depending on how sophisticated your multi channel requirements are, you may need to modify the Inventory Manager to accommodate knowing local stock in store as well as central stock.
Other shipping related entities may need to change to represent any new statuses such as Arrived in Store or Ready for Collection.
If you are using ATG Fulfilment, you may need to change messaging there to accommodate, say, conveying a store code instead of a delivery address to fulfillers and carriers.