FSXA / FAQs

Earlier presentations mentioned an Enterprise Delivery Service (EDS)

Why isn’t it part of the Smartliving PWA stack?

We decided, based on customer and partner feedback, that a stack based on Omnichannel-Manager (ContentCreator) provides a better experience for editors and developers. A 100% fragment-based and content-centric approach is not feasible for most projects. The “responsibilities” of the EDS have been split up between CaaS (microservice) and the FSXACaaS-API (client-side).

What about Smart Dashboards?

We received a lot of feedback regarding the Dashboards idea presented in early 2020. Overall feedback was very positive. This view helps editors and managers to organize their work. Our first iteration was tailored to a specific project and made a lot of assumptions. We’ll integrate the Smart Dashboards into the core of our clients in a more generic way. They’ll return in 2021, now with a focus on multi-site management.

When will FSXA be available?

The FirstSpirit Experience Accelerator is a set of components that have release cycles on their own. Some parts are already available, while others are in Ramp-Up or still in development. All parts will continuously be improved.

If you are interested in the FSXA you can contact the e-Spirit Success Management Team (team-csm@e-spirit.com) or get a demo online.

How can I use data sets and content projections within the PWA?

Similar to unstructured content, structured content (“datasets”) are available in CaaS as dedicated documents. In addition to pages, datasets have the attributes “schema” and “entityType”. For querying it is easier to filter on the content type (“template.uid”). For example to get all product data in the locale “en_GB” use this filter:

filter={'$and':[{'template.uid':'products.product'},{'locale.country':'GB'}]}

If the editor wants to place a dynamic selection of datasets in a page, the concept of content projections in FirstSpirit is used. A content projection determines the target content, restrictions (“query”), ordering and the distribution (“recordCountPerPage” and “maxPageCount”) of the datasets. Here is an example of such a json fragment in CaaS:

{
"fsType": "Content2Section",
"schema": "products",'
"entityType": "product",
"name": "Products",
"displayName": "Product Page",
"template": {
...,
"uid": "products.category_products"
},
"recordCountPerPage": 0,
"maxPageCount": 1,
"query": "products.produkte_nach_kategorie",
"filterParams": {
"category": "a3b87bbd-9f89-409c-8ace-9135a8e230ff"
},
"ordering": [
...
]
}

In the page document this appears at the same level as a section node. On the frontend site this is translated to a CaaS query, for this specific case a query which delivers all product documents as the filter noted above.

What is an API request?

An API request is a communication with one of our REST interfaces. Mostly these are queries (read access), but some are write access too. Technically speaking, we charge for HTTP responses. That is, the responses of our server to an HTTP request.

How many API requests (and queries) are made depends on the implementation in the project. By means of caching mechanisms that can be implemented in the project (e.g. for content elements such as headers, footers, teasers, images, etc.), the number of necessary requests can be reduced considerably.

How many API calls are triggered by one page request?

The following factors play a role in typical PWA implementations:

  • A page request generates an API call to map the requested URL to a page defined by the editor.
  • Another API call to retrieve the content and structure of the page needed for rendering in the PWA.
  • Metainformation about the images used is loaded in bulk calls via the API. Currently this means one call per 30 images.

In the best case, three API calls are made for the initial call of a PWA and two API calls are sufficient for all further page calls, if the information from the NavigationService is already available.

Will FSXA be available for on-premises?

Our product lifecycle follows a cloud first approach. New capabilities will be available in the cloud first and might become available on premise at a later date. At the moment FSXA is cloud-only, but the main components of our FSXA stack are available on premise as well (ContentCreator, FragmentCreator, OmnichannelManager, CaaS).

Cloud only components are Intelligent Content Service (ICE) and the NavigationService

© 2005 - 2021 e-Spirit AG | All rights reserved. | FirstSpirit 2021-04 | Data Privacy | Imprint | Contact us