Sitecore user group mumbai sitecore commerce extension
Download as PPT, PDF0 likes52 views
The document discusses Sitecore Commerce (XC) customization and extension points, presenting an overview of key features such as shopping cart, inventory, and checkout, along with strategies for adding properties to commerce entities. It highlights the benefits of plug-in architectures for modular application development and details various extensibility points including entities, components, pipelines, and commands. A sample plugin scenario is provided to illustrate extending sellable entities and other functionalities within the XC framework.
Sitecore user group mumbai sitecore commerce extension
- 1. Sitecore Commerce(XC) Customization and extension points. -Jitendra Soni 26th Sep 2020
- 2. WHO ISYOUR PRESENTERTODAY? • 13 + years of IT experience. • 7+ years Sitecore. • 8 Sitecore projects. • 5 Sitecore XP and XC new project. • Search (Solr, Azure, Coveo and Fusion). • XC – Version 8.2.1, 9.1,9.2,9.3, 10.0 • Living in Sydney with family. • Awarded by President of India in 2000 • State level winner for Genius student award -1996 SOFTWARE DEVELOPMENT PERSONAL 2 • Sitecore certified • Microsoft Technology Specialist- MCPD • Coveo Certified Platform Developer • Google GTM and GA, ecommerce analytics Certified
- 3. • Sitecore Stack Exchange- http://sitecore.stackexchange.com • Sitecore Community Portal - https://community.sitecore.net/ • Community Docs - https://sitecore-community.github.io/docs/ • Sitecore User group – • Sitecore User Group Directory • http://sitecoreug.org/ • http://www.MeetUp.com • https://www.reddit.com/r/sitecore/wiki/user-groups 3 SITECORE COMMUNITY HOWYOU CAN CONNECT…..
- 4. • 10+ years and Sitecore 7+ years (Active Blogging) • Sitecore Slack and stack exchange 4 SITECORE COMMUNITY CONNECT…..
- 5. AGENDAVIEW. 5 1. Architecture Flow 2. Setup your development environment. 3. Commerce Key Features • Shopping Cart, Inventory, Orders, Checkout, Entitlement, Pricing, Shops, Fulfilment, Promotions, Catalog, Payment. 4. Adding properties to Commerce entities • Code First approach • Composer Entity. 5. How to extend XC with plugins • Plugin Architecture and benefits • Plugins in XC and extension points. • Example plugin.
- 8. TROUBLESHOOTING FOR DEVELOPMENT ENV. SETUP. 1. https://horizontal.blog/2019/02/23/site core-commerce-engine-debugging- invalid-request-line/ 2. https://www.linkedin.com/in/brijesh- patel-52b6ab6/?originalSubdomain=in
- 9. ADDING PROPERTIESTO COMMERCE ITEMS https://kb.sitecore.net/articles/083614 1. Adding properties to Commerce items 1. https://kb.sitecore.net/articles/083614 2. https://doc.sitecore.com/users/90/sitecore-experience- commerce/en/adding-properties-to-commerce-items.html 1. Sitecore Expérience Commerce 9 – Entity Composer 1. https://community.sitecore.net/technical_blogs/b/technical- marketing/posts/experience-commerce-entity-composer Démo Time!!
- 10. ABOUT PLUG-IN ARCHITECTURES 1. Plug-in architectures are an attractive solution for developers seeking to build applications that are modular, customizable, and easily extensible. What began as a clever way to allow third parties to add features to an application without access to source code has, for many developers, evolved into a full-blown methodology for application development. 2. Structuring an application as a well-designed host framework and a set of plug-ins gives you many benefits as an application developer: 3. You can implement and incorporate application features very quickly. 4. Because plug-ins are separate modules with well-defined interfaces, you can quickly isolate and solve problems. 5. You can create custom versions of an application without source code modifications. 6. Third parties can develop additional features without any effort on the part of the original application developer. 7. Plug-in interfaces can be used to wrap legacy code written in different languages. 8. End-users also benefit from using applications with a plug-in architecture: 9. They can customize feature sets to particular workflows. 10. They can disable unwanted features, potentially simplifying the application’s user interface, reducing memory footprint, and improving performance
- 11. ABOUT PLUG-IN ARCHITECTURES – CONTINUE..
- 12. EXTENSIBILITY POINT - ENTITIES 1. Sitecore.Commerce.Core.CommerceEntity 2. Can be Extended Traditionally or add Components at Runtime
- 13. ORDER- ENTITIES
- 15. EXTENSIBILITY POINT - COMPONENTS 1. Basic structure for supporting compositional extensibility 2. Only add the components you need, when you need them 3. Even add components at runtime if required. 4. Add/remove components to/from an entity as 5. required. 6. Typically used to trigger business actions 7. Only one type of component is allowed per entity.
- 16. EXTENSIBILITY POINT - PIPELINES & PIPELINE BLOCKS 1. Contain the majority of functionality for the engine 2. Bring Entities & Components together 3. Specify a contract defining arguments in & out. 4. Each Pipeline contains a series of Pipeline Blocks 5. Similar in concept to Pipelines & Processors in XP
- 17. EXTENSIBILITY POINT - POLICIES A named, versionable and variable set of data that can be used as facts within behaviors to influence the functionality of the Engine. 1. Centralized policy store using abstract entity storage. 2. Worker processes only need a link to the policy store to bootstrap. 3. Publish workflow without moving data. 4. Policies are heavily cached and rarely change. 5. Policies can have attached rules to deliver 6. personalized policies.
- 18. EXTENSIBILITY POINT - COMMAND 1. A Command represents a single executable Unit of Work 2. Commands are request/response oriented 3. Tokens used for status checking 4. Typically created in Controller to being pipeline execution 5. No Services/Managers in plugins, use commands instead.
- 19. EXTENSIBILITY POINT - MINIONS Asynchronous Task Runner Processes background tasks 1. Order processing 2. Data cleanup 3. Index update 4. Index rebuild 5. Refunds processing 6. Sales Activities processing
- 20. SAMPLE PLUGIN – CUSTOM ORDER NUMBER GENERATOR DEMO!!
- 21. SCENARIOS – A FEW SAMPLE REQUIREMENTS . 1. Extending Sellable Entity to keep additional fields. 2. Extending Order Entity to keep additional field details. 3. Extending Cart entity to keep and track additional details. 4. Inventory extension. 5. Promotion extension 6. Search Functionality – A computed field or SXA extension. 7. Wishlist Functionality. 8. Membership based discounted price. 9. Third Party Payment Integration – Zip Pay, PayUMoney etc.
- 22. PROMOTION – CUSTOM QUALIFICATION AND BENEFIT
- 23. PROMOTION – CUSTOM QUALIFICATION AND BENEFIT