App UI registration

Your app must be correctly configured with Adobe App Registry to use the Admin UI SDK to create a custom UI in Commerce. You must perform the following steps before submitting your app to be published.

Code layout best practices

We recommend using the following code layout for your project:

├── src/
│   └── commerce-backend-ui-1/
│       ├── actions/
│       ├── web-src/
│       └── ext.config.yaml
├── install.yaml
├── extension-manifest.json
├── package.json
├── .env
└── app.config.yaml
Copied to your clipboard
├── src/
│   └── commerce-backend-ui-1/
│       ├── actions/
│       ├── web-src/
│       └── ext.config.yaml
├── install.yaml
├── extension-manifest.json
├── package.json
├── .env
└── app.config.yaml

Add or update the `install.yml` file

Create an install.yml file in the root of your project.

Make sure you target the correct extensionPointId: commerce/backend-ui/1

$schema: http://json-schema.org/draft-07/schema
$id: https://adobe.io/schemas/app-builder-templates/1

categories:
  - action
  - ui

extensions:
  - extensionPointId: commerce/backend-ui/1
Copied to your clipboard
$schema: http://json-schema.org/draft-07/schema
$id: https://adobe.io/schemas/app-builder-templates/1

categories:
  - action
  - ui

extensions:
  - extensionPointId: commerce/backend-ui/1

Create or update the `extension-manifest.json` file

Create or update your project extension-manifest.json file so that it is similar to the following:

{
  "name": "commerce-first-app",
  "displayName": "Commerce First App on App Builder",
  "description": "Commerce First App on App Builder",
  "platform": "web",
  "id": "commerce-first-app",
  "version": "1.0.0"
}
Copied to your clipboard
{
  "name": "commerce-first-app",
  "displayName": "Commerce First App on App Builder",
  "description": "Commerce First App on App Builder",
  "platform": "web",
  "id": "commerce-first-app",
  "version": "1.0.0"
}

Add an `ExtensionRegistration` component

Create an ExtensionRegistration React component that registers the menu configuration in the App Registry. Use the adobe/uix-sdk with the adobe-uix-guest dependency. The UI Extensibility Getting Started guide describes this process further.

Add the uix-guest dependency in the package.json.

"@adobe/uix-guest": "^1.0.3"
Copied to your clipboard
"@adobe/uix-guest": "^1.0.3"

Run npm install.

npm install
Copied to your clipboard
npm install

Create an ExtensionRegistration React component to register the application with a unique extensionId, as shown in the following sample ExtensionRegistration.jsx file. The component can optionally return your main page, if any.

import { register } from '@adobe/uix-guest'
import { MainPage } from './MainPage'
import { useEffect } from 'react'
import { extensionId } from './Constants'

export default function ExtensionRegistration(props) {
  useEffect(() => {
    (async () => {
      await register({
        id: extensionId,
        methods: {
        }
      })
    })()
  }, [])

  return <MainPage ims={props.ims} runtime={props.runtime} />
}
Copied to your clipboard
import { register } from '@adobe/uix-guest'
import { MainPage } from './MainPage'
import { useEffect } from 'react'
import { extensionId } from './Constants'

export default function ExtensionRegistration(props) {
  useEffect(() => {
    (async () => {
      await register({
        id: extensionId,
        methods: {
        }
      })
    })()
  }, [])

  return <MainPage ims={props.ims} runtime={props.runtime} />
}

The extension ID should be the same as the one defined in the extension-manifest.json.

Update the `App.js` routing

Update the application routing to have the ExtensionRegistration component correctly routed to the index. Here is an example of the first app routing in the App.js component:

<ErrorBoundary onError={onError} FallbackComponent={fallbackComponent}>
  <HashRouter>
      <Provider theme={lightTheme} colorScheme={'light'}>
          <Routes>
              <Route index element={<ExtensionRegistration runtime={props.runtime} ims={props.ims} />} />
          </Routes>
      </Provider>
  </HashRouter>
</ErrorBoundary>
Copied to your clipboard
<ErrorBoundary onError={onError} FallbackComponent={fallbackComponent}>
  <HashRouter>
      <Provider theme={lightTheme} colorScheme={'light'}>
          <Routes>
              <Route index element={<ExtensionRegistration runtime={props.runtime} ims={props.ims} />} />
          </Routes>
      </Provider>
  </HashRouter>
</ErrorBoundary>

Create a registration runtime action

Under the actions repository in the project, create a registration respository in which you create the index.js file with the following code:

async function main() {

    return {
        statusCode: 200,
        body: {
            registration: {
            }
        }
    }
}

exports.main = main
Copied to your clipboard
async function main() {

    return {
        statusCode: 200,
        body: {
            registration: {
            }
        }
    }
}

exports.main = main

You must populate the registration section with calls to fetch menus, pages, and other entities to be displayed in the Admin. Extension Points provides reference information and examples.

Update the `app.config.yaml` file

Update the app.config.yaml configuration file as follows:

extensions:
  commerce/backend-ui/1:
    $include: src/commerce-backend-ui-1/ext.config.yaml
Copied to your clipboard
extensions:
  commerce/backend-ui/1:
    $include: src/commerce-backend-ui-1/ext.config.yaml

This file now declares extensions and redirects to an ext.config.yaml file.

Add or update the `ext.config.yaml`

Add or update the src/commerce-backend-ui-1/ext.config.yaml file. The commerce-backend-ui-1 directory contains the actions and web-src code.

Your extension configuration file should look like this:

operations:
  view:
    - type: web
      impl: index.html
actions: actions
web: web-src
runtimeManifest:
  packages:
    admin-ui-sdk:
      license: Apache-2.0
      actions:
        registration:
          function: actions/registration/index.js
          web: 'yes'
          runtime: 'nodejs:18'
          inputs:
            LOG_LEVEL: debug
          annotations:
            require-adobe-auth: true
            final: true
Copied to your clipboard
operations:
  view:
    - type: web
      impl: index.html
actions: actions
web: web-src
runtimeManifest:
  packages:
    admin-ui-sdk:
      license: Apache-2.0
      actions:
        registration:
          function: actions/registration/index.js
          web: 'yes'
          runtime: 'nodejs:18'
          inputs:
            LOG_LEVEL: debug
          annotations:
            require-adobe-auth: true
            final: true

The package name must be admin-ui-sdk, and the action must be registration. The function can point to any route that returns the registration in the correct expected format.

We recommend securing the registration runtime action by setting require-adobe-auth to true. The Adobe Commerce instance will correctly load registrations securely based on the provided IMS credentials.

Complete this file with the actions from your app.

Installation

Extension points