The Single-line text field is another data type of Content. Learn how to create, update, and execute GraphQL queries. Adobe Experience Manager as a Cloud Service uses AEM Publish Dispatcher filters to ensure only requests that should reach AEM do reach AEM. For example, a URL such as:Learn how to configure AEM Publish Dispatcher filters for use with AEM GraphQL. Above the Strings and Translations table, click Add. Overview; Single-page app; Web Component; Mobile; Server-to-server; Configurations. The AEM Headless quick setup gets you hands-on with AEM Headless using content from the WKND Site sample project, and a React App that consumes the content over AEM Headless GraphQL APIs. In this chapter, you persist the queries to AEM and learn how to use cache control on persisted queries. In this video you will: Learn how to enable GraphQL Persisted Queries. You need to define the schema beforehand =>. Dispatcher Setup AEM as a Cloud Service AEM Coders Hub #aem #aemdeveloper #aemcommunity #aem65 #aemcoral #adobe #adobeaemdeveloper #api #java… Liked. Last update: 2023-04-21. They can be requested with a GET request by client applications. Download the latest GraphiQL Content Package v. Client type. By default all requests are denied, and patterns for allowed URLs must be explicitly added. You can provide additional code to expose pages and other structures, but when you require content from other API’s such as personalized content, a dedicated. Bundle start failed. The following AEM documentation includes everything from essential guides for those new to the content management system (CMS) to videos, tutorials, and further learning resources to get the most out of AEM 6. Customers using CORS requests, might need to review and update their CORS configuration in the Dispatcher. It has the aim of storing (or “caching”) as much of the static website content as possible and accessing. 5 Serve pack 13. Deploying an AEM Headless application requires attention to how AEM URLs are constructed to ensure the correct AEM host/domain is. I add below config to the pom. Instructor-led training View all learning options. GraphiQL is included in all environments of AEM (but will only be accessible/visible when you configure your endpoints). json. 5. In AEM 6. Browse the following tutorials based on the technology used. This GraphQL API is independent from AEM’s GraphQL API to access Content Fragments. Adobe Experience Manager as a Cloud Service uses AEM Publish Dispatcher filters to ensure only requests that should reach AEM do reach AEM. 5 Forms or earlier to AEM Forms as a Cloud Service; Groups and permissions; Import, export, and organize Adaptive Forms, PDF forms, and other assets; Integrate. This guide uses the AEM as a Cloud Service SDK. 5. Content hierarchy for GraphQL optimization: Implement a filter on the _path field of the top-level fragment to achieve this optimization. Author in-context a portion of a remotely hosted React. GraphQL query is an API for headless architecture to deliver content fragment data in the form of JSON. Can Product assets (images) be stored and referenced from AEM via Adobe Commerce admin? How can assets from Dynamic Media be consumed? No official AEM Assets – Adobe Commerce integration is available. The use of React is largely unimportant, and the consuming external application could be written in any framework. The default cache-control values are:. 5. Content Fragments. Linux: use the top command to check CPU utilization. And until recently, it was only available for AEM-as-a-Cloud-Service users. This allows for longer TTLs (and much-reduced request volume at origin. This tutorial explores how AEM’s GraphQL APIs and headless capabilities can be used to power the experiences surfaced in an external app. Overview; 1 - Content modeling; 2 - AEM Headless APIs and React; 3 - Complex components; Deployments. Project Configurations; GraphQL endpoints;. This is a core feature of the AEM Dispatcher caching strategy. 1. It is fully managed and configured for optimal performance of AEM applications. 2. Learn how to create GraphQL queries to return content from Adobe Experience Manager (AEM) and how to use the GraphiQL tool to quickly test, refine, and debug queries. $ cd aem-guides-wknd-spa. Best Practices for Queries and Indexing. js project ready, open a terminal window at the root of the application and install both Nexus Schema and Prisma. The AEM Headless quick setup gets you hands-on with AEM Headless using content from the WKND Site sample project, and a React App that consumes the content over AEM Headless GraphQL APIs. An end-to-end tutorial illustrating how to build-out and expose content using AEM’s GraphQL APIs and consumed by an external app, in a headless CMS scenario. tar. Created for: Beginner. Check at the OS level if the AEM java process is causing high CPU utilization: If AEM is causing high CPU utilization then run the out-of-the-box profiling tool for a few minutes and analyze the result. 8 and above Steps to run the dispatcher in docker container Once the docker is installed in local start the docker using command line or using docker desktop. The GraphiQL tool also enables users to persist or save queries to be used by client applications in a production setting. You can also watch the talk presented at Apollo Space Camp 2020 by Khalil Stemmler here on YouTube. But it’s no secret that Magento’s built-in CMS doesn’t go far when your business scales. Teams. 5 the GraphiQL IDE tool must be manually installed. Logs act as the frontline for debugging AEM applications in AEM as a Cloud Service, but are dependent on adequate logging in the deployed AEM application. Nov 7, 2022. If you expect a list of results: Dispatcher: To allow required URLs; Mandatory; Vanity URL: To allocate a simplified URL for the endpoint; Optional; OSGi Configuration:. zip. It appears that the GraphQL endpoint is blocked on the dispatcher. The GraphQL API of AEM provide a powerful query language to expose data of Content Fragments to downstream applications. By default all requests are denied, and patterns for allowed URLs must be explicitly added. It will be used for application to application authentication. Topics: GraphQL API View more on this topic. It is best practice and highly recommended to use persisted queries when working with the AEM GraphQL API. See: GraphQL Persisted Queries - enabling caching in the Dispatcher; Use a Content Delivery Network (CDN) Recommendation. Experience LeagueI added GraphQL to the bundle in the AEM and it caused bundle start failed. Not sure what the reason could be but this is happening even with untouched old persistent queries as well. Content Fragments. 3. It is best practice and highly recommended to use persisted queries when working with the AEM GraphQL API. 2. This file causes the SDK and runtime to validate and. However if there are huge number of Content Fragments in the system for instance > 50000, please avoid using GraphQL queries as. AEM code & content package (all, ui. Connect and share knowledge within a single location that is structured and easy to search. The AEM GraphQL API allows you to update the default cache-control parameters to your queries in order to improve performance. 3 - Explore the AEM GraphQL API; 4 - Persisted GraphQL Queries; 5 - Client Application Integration; Headless First Tutorial. Learn how to query a list of. react project directory. 4. A “Hello World” Text component displays, as this was automatically added when generating the project from the AEM Project archetype. AEM makes an environment fast and dynamic, because it also serves as a load-balancing tool. The AEM Headless quick setup gets you hands-on with AEM Headless using content from the WKND Site sample project, and a React App that consumes the content over AEM Headless GraphQL APIs. GraphQL Editor user interface does not let you scroll through all the persisted queries when there is a high number of queries (for example, more than. The ability to customize a single API query allows you to retrieve and deliver the specific content that you want/need to render (as the. #aem #cms #dispatcherAEM as a Cloud Service - Local Development Environment setup - @h9ioHow to use Re-Fetching Flush Agent in Adobe Experience Manager(AEM). From the AEM Start menu, navigate to Tools > Deployment > Packages. json. Persisted queries also in effect, define an API, and decouple the need for the developer to understand the details of each Content Fragment Model. The classic UI was deprecated with AEM 6. AEM HEADLESS SDK API Reference Classes AEMHeadless . Learn about the different data types that can be used to define a schema. Get started with Adobe Experience Manager (AEM) and GraphQL. They can be requested with a GET request by client applications. xml [INFO] Parent element not overwritten in C:AshishCodeBaseCloudSPA1mysitedispatcher. Click OK. AEM Dispatcher is available as a plug-in for your web server. Developer. . Depending on your instance, you can directly access the GraphiQL interface included with AEM GraphQL API for submitting and testing queries. impl. Persisted queries are more performant than client-defined GraphQL queries, as persisted queries are executed using HTTP GET, which is cache-able at the CDN and AEM Dispatcher tiers. 2. The default cache-control values are:. The following tools should be installed locally: JDK 11;. When using an out-of-the-box implementation, the process described above should be sufficient to generate the Target Offer from the Experience Fragment and. Learn how AEM can go beyond a pure headless use case, with options for in-context authoring and experience management. Tutorials by framework. Brands have a lot of flexibility with Adobe’s CIF for AEM. The content returned can then be used by your applications. Purging cached pages and assets from Akamai when replicated from AEM in a similar manner as Dispatcher-cached resources. Explore AEM's GraphQL APIs using the built-in GrapiQL IDE. registerService method. The sample React app has three main parts: The src/api folder contains files used to make GraphQL queries to AEM. This isn't so much a field as it is more of a cosmetic enhancement. By utilizing the AEM Headless SDK, you can easily query and fetch Content Fragment data using GraphQL. Tutorials by framework. This tutorial walks through the implementation of a Angular application for a fictitious lifestyle brand, the WKND. 3 and earlier versions where the /enableTTL only caches using max-age directive. Let’s create some Content Fragment Models for the WKND app. Topics: GraphQL API View more on this topic. Tap on the download button in the top-left corner to download the JSON file containing accessToken value, and save the JSON file to a safe location on your development machine. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). The GraphiQL tool also enables users to persist or save queries to be used by client applications in a production setting. Dispatcher filters. With AEM, a production environment often consists of two different types of instances: an Author and a Publish instances. The documentation folder contains some code that is used to generate a subset of the Magento schema that covers all the queries required by the CIF. zip: AEM 6. Apollo client is a robust, production-ready, and mature client for GraphQL on the web. Use the. Adobe Experience Manager as a Cloud Service uses AEM Publish Dispatcher filters to ensure only requests that should reach AEM do reach AEM. Any new configuration available in that new Dispatcher Tools version can be used to deploy to Cloud environments running that version of AEM in the Cloud or higher. Select main from the Git Branch select box. Getting Started. This short post aims to collect valuable resources as a starting point to learn more about the AEM Dispatcher, an important and integral part of every AEM setup. I added two demo classes to my project and reinstall bundle. Adobe Experience Manager as a Cloud Service uses AEM Publish Dispatcher filters to ensure only requests that should reach AEM do reach AEM. The use of React is largely unimportant, and the consuming external application could be written in any framework. The HTTP GET requests from the headless app to AEM’s GraphQL APIs must be configured to interact with the correct AEM service, as. This is used by the CIF authoring tools (product console and pickers) and for the CIF client-side components doing direct GraphQL calls. TTL for the client (for example, a browser) 7200 seconds is the default (s-maxage=7200) TTL for the Dispatcher and CDN; also known as shared caches. Dispatcher cache files are updated unexpectedly | AEM; Unable to view dictionary element in UI (user and system) VLT RCP content synchronization fail; AEM: Collecting status information for troubleshooting in Web Console; Request queue becomes unpublished; Customer unable to delete records from custom schema; How to download. As a AEM BackEnd Developer, I have experience in. AEM Publish service requires an AEM Dispatcher configuration to be added to the AEM Publish’s Dispatcher configuration. This feature is being gradually rolled out to customers in early September. The OSGI configuration outlined in this document is sufficient for: Single-origin resource sharing on AEM Publish. Tap Create new technical account button. For production deployments it is strongly recommended to setup a reverse proxy to the commerce GraphQL endpoint via the AEM Dispatcher or at other network layers (like CDN). Please check the filter section to assure that its allowed. Missing search index that causes large repository traversal causing performance issues due to high disk I/O. There are several ways to control for how long a CDN caches a resource before it re-fetches it from Dispatcher. Aem dispatcher – tips & tricks. Documentation AEM AEM Tutorials AEM Headless Tutorial Dispatcher filters for AEM GraphQL. Learn how to query a list of Content. Author in-context a portion of a remotely hosted React. Experience LeagueManage metadata of your digital assets. The execution flow of the Node. Under Jackrabbit 2, all contents was indexed by default and could be queried freely. When running on Windows and generating the dispatcher configuration, you should be running in an elevated command prompt or the Windows Subsystem for Linux (see. This session dedicated to the query builder is useful for an overview and use of the tool. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL IDE. GraphQL API. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Please check the filter section to assure that its allowed. d/available_vhosts. The Origin header must not be passed to AEM publish via the Dispatcher: Check the clientheaders. The following subtypes of raster image file formats that are not supported in Dynamic Media: PNG files that have an IDAT chunk size greater than 100 MB. Example: if one sets up CUG, the results returned will be based on user's session. The default cache-control values are:. TIP. AEM dispatcher: Filters, ignoreUrlParams, virtualhosts, rewrites by Aanchal Sikka Overview In this extensive blog post, we'll delve into the topics of filters, ignoreUrlParams, virtual hosts, and rewrites, providing a detailed examination of their best practices and simplifying their operational me. AEM devs, join us on Nov 6 (EMEA, LATAM, NA) & Nov 15 (APAC) for Adobe Developers Live. Adobe AEM Magento Integration: A Tandem of CMS and Ecommerce. doFilter. In this article, we’ll break down the responsibilities of a state management solution, discuss what’s involved in building a solution from scratch, and how Apollo Client 3 introduces new ways to manage local state and remote data in harmony. AEM Content Fragments work together with the AEM GraphQL API (a customized implementation,. To support AEM GraphQL persisted queries, add the following pattern: /graphql/execute. The following configurations are examples. When configuring CORS on AEM Publish, ensure: The Origin HTTP request header cannot be sent to AEM Publish service, by removing the Origin header (if previously added) from the. Click on the "Flush" button to clear the cache. all-2. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Next, we’ll use the AEM Headless SDK to retrieve Content Fragment data from AEM’s GraphQL APIs. Since we get GrapghQL connector installed in AEM for Content fragment -Headless approach. An. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. It provides a more flexible and efficient way to access. If a caching issue is suspected, you should republish the pages in question and ensure that a virtual host is available that matches the ServerAlias localhost, which is required for Dispatcher cache invalidation. Learn the recommended Best Practices for the setup and use of AEM GraphQL with Content Fragments. In this video you will: Understand the power behind the GraphQL language. For AEM on-prem installations, this project requires the AEM Commerce Add-On for AEM 6. It allows easier categorization and organization of assets and it helps people who are looking for a specific asset. Navigate to the Software Distribution Portal > AEM as a Cloud Service. Experience LeagueDispatcher; AEM; Usually, Dispatcher is the next server that might serve the document from a cache and influence the response headers returned to the CDN server. Unzip the SDK, which. Related Documentation. 1 - Create Content Fragment Models 2 - Author Content Fragments 3 - Explore the AEM GraphQL API 4 - Persisted GraphQL Queries 5 - Client Application Integration Overview Single-page app Web Component Mobile Server-to-server Configurations AEM hosts CORS Dispatcher filters Rich text Images Localized content Large result sets Preview AEM Headless SDK Dispatcher Configuration Files. graphql. This can be done by creating a new GraphQL servlet in the AEM configuration manager, and then adding the required GraphQL schema and queries to the servlet. js application run from the command line to update asset metadata on AEM as a Cloud Service using Assets HTTP API. Developer. And in this video, we are going to learn about how we can create AEM Project using Archetype. 5 has enhanced its digital customer experience services by providing better content personalization, content fragment enhancements, and easier authoring. js initializes and exports the AEM Headless Client used to communicate with AEM; src/api/usePersistedQueries. Repository Browser is a powerful tool that provides visibility into AEM’s underlying data store, allowing for easy debugging of AEM as a Cloud Service environment. The HTTP GET requests from the headless app to AEM’s GraphQL APIs must be configured to interact with the correct AEM service, as. Enable AEM Dispatcher caching. Code. Example: # GraphQL Persisted. security. The GraphQL API in AEM is primarily designed to deliver AEM Content Fragment’s to. . js initializes and exports the AEM Headless Client used to communicate with AEM; src/api/usePersistedQueries. GraphQL only works with content fragments in AEM. This is the same framework used to translate other AEM content, such as Pages, Experience Fragments, Assets, and Forms. In order to support other 3rd-party "non-Magento" commerce platforms, this project demonstrates how a 3rd-party commerce platform like Hybris can be integrated with the CIF GraphQL connector and the AEM CIF Core Components via the Magento GraphQL API. To share with the community, we talked to the AEM support team and found that it was an issue with 6. Below is a summary of how the React application is built, how it connects to AEM Headless to retrieve content using GraphQL persisted queries, and how that data is presented. {"payload":{"allShortcutsEnabled":false,"fileTree":{"dispatcher/src/conf. x. AEM GraphQL API requests. felix. The WKND client application connects to AEM publish service, so it is important that you published the following to the AEM publish service. The React app should contain one. The configuration file contains a series of single-valued or multi-valued properties that control the behavior of Dispatcher: Adobe Experience Manager as a Cloud Service’s Cross-Origin Resource Sharing (CORS) facilitates non-AEM web properties to make browser-based client-side calls to AEM’s GraphQL APIs, and other AEM Headless resources. Click the Save All Button to save the changes. Learn how AEM automatically generates a GraphQL schema based on a Content Fragment model. cloudpom. AEM as Cloud Service is shipped with a built-in CDN. The WKND reference site is used for demo and training purposes and having a pre-built, fully. Sign up Product. NOTE. adobe aem-guides-wknd-graphql main 18 branches 0 tags Code davidjgonzalez Memo-ized GQL useEffects params so they do not continuously make XHR. Known Issues. 4-linux-x86_64-ssl-4. impl. Learn how to create GraphQL queries to return content from Adobe Experience Manager (AEM) and how to use the GraphiQL tool to quickly test, refine, and debug queries. The following are examples of possible approaches for constructing URLs for AEM GraphQL API and image requests, for several popular headless frameworks and platforms. AEM hosts;. Usually, it relies on invalidation techniques that ensure that any content changed in AEM is properly updated in the Dispatcher. The following configurations are examples. Select the AEM as a Cloud Service development environment from the Eligible Deployment Environments select box. Developer. There are two types of endpoints in AEM: Global. Dispatcher filters. Rich text with AEM Headless. Developer. adobe. Learn how to model content and build a schema with Content Fragment Models in AEM. Enable the below Sling Mappings under /etc/map. Dispatcher filters. You can create an MBean manager class to instantiate MBean services at runtime, and manage the service lifecycle. Using the GraphiQL IDE. dispatcher. In AEM, navigate to Tools > Deployment > Packages to access Package Manager. APOLLO CLIENT. So, on the left side we have authors and we can have multiple authors. Each AEM as a Cloud Service environment has it’s own Developer Console. Tutorials by framework. localhost:4503 8080. GraphQL API. When configuring CORS on AEM Publish, ensure: The Origin HTTP request header cannot be sent to AEM Publish service, by removing the Origin header (if previously added) from the. Recommendation. FileSystemException: C:Usersprojectswknd-testaem-guides-wknddispatchersrcconf. (FilterHandler. json*" } Also, please review if you would want to avoid caching of the. Unpack the Dispatcher Tools into ~/aem-sdk/dispatcher. The zip file is an AEM package that can be installed directly. Enhance your skills, gain insights, and connect with peers. Developer. Create the folder ~/aem-sdk/publish. Open the model in editor. Caching AEM pages or fragments in the AEM Dispatcher is a best practice for any AEM project. If you require a basic introduction to creating Content Fragment Models, please see the appropriate chapter in the basic tutorial. Adobe Experience Manager Assets keeps metadata for every asset. To determine the correct approach for managing build dependent configurations, reference the AEM Headless app’s framework (for example, React, iOS, Android™, and so on) documentation, as the approach varies by framework. Review existing models and create a model. Tap Create new technical account button. 13 of the uber jar. TTL for the client (for example, a browser) 7200 seconds is the default (s-maxage=7200) TTL for the Dispatcher and CDN; also known as shared caches. Use the adventures-all query. GraphQL_SImple. Please check the filter section to assure that its allowed. There’s also the GraphQL API that AEM 6. GraphQL is: “…a query language for APIs and a runtime for fulfilling those queries with your existing data. zip: AEM as a Cloud Service, the default build. In the next chapter, Explore GraphQL APIs, you will explore AEM’s GraphQL APIs using the built-in GrapiQL tool. Bundle start command : mvn clean install -PautoInstallBundle. If you require a single result: ; use the model name; eg city . Edit the file. Select Edit from the mode-selector in the top right of the Page Editor. By default all requests are denied, and patterns for allowed URLs must be explicitly added. An end-to-end tutorial illustrating how to build. By default, sample content from ui. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. GraphQL for AEM - Summary of Extensions. DuoTone, Lab, and Indexed color spaces are not supported. I noticed that my persistent queries are getting updated with Graphql introspection query. AEM Headless is a CMS solution from Experience Manager that allows structured content (Content Fragments) in AEM to be consumed by any app over HTTP using GraphQL. Setup your local development environment for AEM as a Cloud Service SDK or for older versions of AEM. The pattern is: The pattern is: Each persisted query has a corresponding public func (ex. Instead of configuring and maintaining Indexes on single AEM instances, the Index configuration has to be specified. sh out docker. directly; for example, The sample queries are based on the Sample Content Fragment Structure for use with GraphQL. 11 Like 1 Like Translate 2 people had this problem. For GraphQL queries with AEM there are a few extensions: . With AEM as a Cloud Service, your teams can focus on innovating instead of planning for product upgrades. A simple React app is used to query and display Team and Person content exposed by AEM’s GraphQL APIs. Following AEM Headless best practices, the React application uses AEM GraphQL persisted queries to. GraphQL is a query language and server-side runtime for application programming interfaces (APIs) that prioritizes giving clients exactly the data they request. Configuration Browsers — Enable Content Fragment Model/GraphQL. 13+. Developer. GraphiQL is included in all environments of AEM (but will only be accessible/visible when you configure your endpoints). Any attempt to change an immutable area at runtime fails. In the String box of the Add String dialog box, type the English string. By default all requests are denied, and patterns for allowed URLs must be explicitly added. Only static data (such as product or category data) is cached on the Dispatcher. Managing Content. With the Next. Navigate to Tools > General > Content Fragment Models. Through GraphQL, AEM also exposes the metadata of a. 4 web server that runs on Linux i686 and is packaged using the tar. The GraphiQL tool enables developers to create and test queries against content on the current AEM environment. GraphQL API. One could export an AEM page in JSON format via a REST call, however there are many fields in the JSON that the Spring Boot app does not use. Developer Console is accessed per AEM as a Cloud Service. The following are examples of possible approaches for constructing URLs for AEM GraphQL API and image requests, for several popular headless frameworks and platforms. Solved: Hello, I am trying to install and use Graph QL in AEM 6. It is best practice and highly recommended to use persisted queries when working with the AEM GraphQL API. [ERROR] Failed to execute goal org. Ensure you adjust them to align to the requirements of your project. It is intended as a best-practice set of examples as well as a potential starting point to develop your own functionality. Unzip the downloaded aem-sdk-xxx. The release information for the latest desktop app version 2. The AEM GraphQL API is a customized version based on the standard GraphQL API specification, specially configured to allow you to perform (complex) queries on your Content Fragments. Configuration Browsers — Enable Content Fragment Model/GraphQL. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. Once headless content has been translated,. java:135) at org. This means that even when private or s-maxage directives are set it would still cache if max-age is set. 3766. Dispatcher filters. Using this path you (or your app) can: access the GraphQL schema, send your GraphQL queries, receive the responses (to your GraphQL queries). Topics: GraphQL API View more on this topic. To act on the change, we need a GraphQL server that supports introspection. Select GraphQL to create a new GraphQL API. This tutorial explores how AEM’s GraphQL APIs and headless capabilities can be used to power the experiences surfaced in an external app. sample will be deployed and installed along with the WKND code base. Learn best practices for headless delivery with an AEM Publish environment. Learn about Akamai's caching. End to end experience configuring the full AEM stack from author instance to dispatcher. A pre-compiled AEM package is available for easy installation on local environments using CRX Package Manager: aem-guides-wknd. This is built with the Maven profile classic and uses v6. Developer. The basic operation of queries with GraphQL for AEM adhere to the standard GraphQL specification. May 2020 - Present3 years 4 months. Provides link to other generic actions; such as Search, Help, Experience Cloud Solutions, Notifications, and User Settings. The common folder contains all the code that fetches and converts 3rd-party data into the GraphQL format. The zip file is an AEM package that can be installed directly. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. In this chapter, you explore how AEM’s GraphQL APIs can drive the experience in an external application. It becomes more difficult to store your assets,. What I wanted to ask is : Is there any way we can override any Model/Servlet that are being used in Graph QL connector and then accordingly could manipulate API response. User. Learn the recommended Best Practices for the setup and use of AEM GraphQL with Content Fragments. 5 with Service Pack 16 or 17, when in the List view of sites with the “Workflow” column enabled, you cannot sort the list based on the items in that column. The Dispatcher can also be used for load.