<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Magnolia Connector on ScipioERP</title><link>https://www.scipioerp.com/community/developer/magnolia-integration/</link><description>Recent content in Magnolia Connector on ScipioERP</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 26 Mar 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://www.scipioerp.com/community/developer/magnolia-integration/index.xml" rel="self" type="application/rss+xml"/><item><title>Magnolia Pages</title><link>https://www.scipioerp.com/community/developer/magnolia-integration/magnolia-pages/</link><pubDate>Thu, 19 May 2016 00:00:00 +0000</pubDate><guid>https://www.scipioerp.com/community/developer/magnolia-integration/magnolia-pages/</guid><description>&lt;p&gt;Creating a Magnolia page for rendering from Scipio ERP is a two-step process: you first write the page itself, or more specifically the template for it, using Scipio ERP-specific API facilities; then you map an Scipio ERP controller request or view to the page so it is invoked for rendering through an Scipio ERP webapp or store. Any Scipio ERP Request that falls into the Scipio ERP request flow will output the page that is specified. This gives a lot of freedom when reusing or implementing new processes in the system.&lt;/p&gt;</description></item><item><title>Magnolia Templating</title><link>https://www.scipioerp.com/community/developer/magnolia-integration/magnolia-templating/</link><pubDate>Thu, 19 May 2016 00:00:00 +0000</pubDate><guid>https://www.scipioerp.com/community/developer/magnolia-integration/magnolia-templating/</guid><description>&lt;p&gt;SCIPIO ERP templates are essentially Magnolia templates enriched with a SCIPIO-specific API and context for use in code. To get started on Magnolia templating visit: &lt;a href="http://documentation.magnolia-cms.com/display/DOCS/Introduction&amp;#43;to&amp;#43;templating" class="link-external" rel="noopener"&gt;http://documentation.magnolia-cms.com/display/DOCS/Introduction+to+templating&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;A fully written example of a very dynamic page is included in this package. Though a basic understanding of Magnolia templating is required, the CatoDemoCheckout is an excellent starting point in understanding the power of SCIPIO templating as a whole. It essentially replaces the checkout page of a modern store front-end and is compatible with the demo store “syracus” that is included in this package. The example is available within the template editor or already assigned to a page within the page editor, and as page template model “com.ilscipio.cato.magnolia.demo.model.CatoDemoCheckoutModel” and template cato-magnolia-demo/templates/pages/catoDemoCheckout.ftl.&lt;/p&gt;</description></item><item><title>Magnolia Request Mapping</title><link>https://www.scipioerp.com/community/developer/magnolia-integration/magnolia-request-mapping/</link><pubDate>Thu, 19 May 2016 00:00:00 +0000</pubDate><guid>https://www.scipioerp.com/community/developer/magnolia-integration/magnolia-request-mapping/</guid><description>&lt;p&gt;For Magnolia pages to be useful in the context of an OFBiz application, one must map OFBiz webapp controller views to pages to be rendered using the CMS (instead of the usual OFBiz screen handler).&lt;/p&gt;
&lt;p&gt;When an OFBiz webapp controller request reaches the rendering stage and the view-handler is invoked, SCIPIO ERP checks whether the current request or view matches a known CMS page mapping in its database. If such a mapping exists and all conditions for its use pass, SCIPIO ERP invokes the CMS to handle the rendering rather than the OFBiz screen view handler.&lt;/p&gt;</description></item></channel></rss>