I’m looking for a way to update my Canvas LMS integrated external tool (LTI 1.3) with the currently active course sections.
Currently, I'm receiving each user's active sections (name and id) as a custom field defined in the developer key:
$Canvas.course.sectionIds
$com.instructure.User.sectionNames
Unfortunately, this doesn't provide any data about deleted sections.
What would be the best practice for getting the full list of sections in a course, particularly to discover if a section was deleted, from my external tool’s backend?
I want to cover a scenario where every product in the store has many distributors. In our case, a distributor is a hardware provider or a license provider. We want to be able to show what distributors are available per product, and also show information such as stock quantity, SKU and price per distributor. What would be the best approach to have this feature in Magento 2.4?
My app got bumped from the Chrome store and it looks like it needs to be moved to the g suite marketplace. I started the configuration process and right away at the top it says "your account does not belong to the same domain as this cloud project or app". This application was written under my incubator company then a new company was spun up and the app was moved over. But the operations and startup of the application for many years was under the original domain. I can't migrate the google side of the application/oauth/etc over without seriously impacting my business customers. But I own both domains. I can't seem to proceed and I'm thinking this may be why. What can I do? I need to get this app installed at several new customer's locations.
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).
I was inspired by the One-Page PRD mentioned on the Atlassian website.
How might I go about doing the same if I am using Team Services? For example, lets say I have an Epic and linked underneath that several features, user stories and acceptance criteria. Is it possible to create a "one pager" based on just this epic that summarizes all the items underneath it at a glance? (for example: lists the epic's description at the top, followed by all the user stories with description and current status, and acceptance criteria met or not met underneath?) It would be useful for distributing to non-technical product owners instead of having them wander through work item queries to get an overall picture of the project with some requirement detail, or to present to stakeholders during a meeting.
Most of the reporting options I am finding, such as the built in dashboards (and Power BI?) are mostly aggregate charting. It would be simpler to create what I need in SSRS, but my understanding is that is not available with Team Services.
As you said that the Team Services has built in dashboards and integrate with Power BI, but aren’t meet your requirement.
For your requirement, you can build a custom extension (e.g. Dashboard widget) with REST API (can call rest api with VSS sdk, check dashboard widget sample for detail) to do the report.