Links

Build an Extension App with App Views

This guide will provide an overview on how to use the Symphony App Developer Kit (ADK) to build an extension app that has app views. This app will add entries into the left navigation that will each launch a separate app view. The project will use React and ADK's React and Webpack configuration for app view generation.
Prerequisite: Install NodeJS first, either directly or via nvm

Create Project

Create a working directory and initialize it using npm.
mkdir adk-example-views && cd $_
npm init -y

Install Dependencies

Install the Symphony ADK, the ADK React and Webpack configurations, React itself, Symphony UI Toolkit for UI Components, Typescript, Webpack and the required loaders.
JavaScript
TypeScript
npm install \
@symphony-ui/adk \
@symphony-ui/adk-react \
react \
react-dom
npm install --save-dev \
@symphony-ui/adk-webpack \
@symphony-ui/uitoolkit-components \
css-loader \
style-loader \
babel-loader \
@babel/preset-react \
webpack \
webpack-cli \
webpack-dev-server
npm install \
@symphony-ui/adk \
@symphony-ui/adk-react \
react \
react-dom
npm install --save-dev \
@symphony-ui/adk-webpack \
@symphony-ui/uitoolkit-components \
css-loader \
style-loader \
ts-loader \
typescript \
webpack \
webpack-cli \
webpack-dev-server
Open the project directory in an editor of your choice

Add Script Commands

Edit the package.json file, replacing the scripts section with the following:
"scripts": {
"start": "webpack-dev-server --mode=development",
"build": "webpack --mode=production"
},
This adds two commands:
  • npm start for starting the development web server
  • npm run build to launch the production build process

Add Configuration

JavaScript
TypeScript
Create a .babelrc file with the following contents:
.babelrc
{
"presets": [ "@babel/preset-react" ]
}
Create a webpack.config.js file with the following contents:
webpack.config.js
1
const SymADKWebpack = require('@symphony-ui/adk-webpack');
2
const packageJson = require('./package.json');
3
const config = {
4
devtool: 'source-map',
5
module: {
6
rules: [
7
{
8
test: /\.(js|jsx)$/,
9
exclude: /node_modules/,
10
loader: "babel-loader"
11
},
12
{
13
test: /\.css$/,
14
use: [
15
'style-loader',
16
'css-loader',
17
],
18
},
19
],
20
},
21
resolve: {
22
extensions: ['.js', '.jsx'],
23
}
24
};
25
module.exports = SymADKWebpack(config, packageJson.name);
Create a tsconfig.json file with the following contents:
tsconfig.json
1
{
2
"compilerOptions": {
3
"jsx": "react",
4
"lib": ["ES2015", "DOM"],
5
},
6
"include": ["src/**/*"],
7
}
Create a webpack.config.js file with the following contents:
webpack.config.js
1
const SymADKWebpack = require('@symphony-ui/adk-webpack');
2
const packageJson = require('./package.json');
3
const config = {
4
devtool: 'source-map',
5
module: {
6
rules: [
7
{
8
test: /\.tsx?$/,
9
use: 'ts-loader',
10
exclude: /node_modules/,
11
},
12
{
13
test: /\.css$/,
14
use: [
15
'style-loader',
16
'css-loader',
17
],
18
},
19
],
20
},
21
resolve: {
22
extensions: ['.tsx', '.ts', '.js'],
23
}
24
};
25
module.exports = SymADKWebpack(config, packageJson.name);

Add Application Manifest

Each extension app requires a manifest (also known as the bundle.json file) to describe the application. Create a file named bundle.json with the following contents:
bundle.json
1
{
2
"applications": [
3
{
4
"type": "sandbox",
5
"id": "adk-example",
6
"name": "ADK Example",
7
"description": "Symphony ADK",
8
"blurb": "Symphony ADK",
9
"publisher": "Symphony",
10
"url": "https://localhost:4000/controller.html",
11
"domain": "localhost"
12
}
13
]
14
}

Build the App

We are now ready to start building the app. Create a src directory and a file named index.js (or index.ts if you're using TypeScript) within it.
src/index.js
1
import * as ADK from '@symphony-ui/adk';
2
3
ADK.start({ id: 'adk-example' }).then(() => {
4
ADK.navigation.add('ADK View A', () => {
5
ADK.modules.open('view-a', { title: 'ADK View A' });
6
});
7
});
8
The code ADK.start() initializes the ADK with an app id (adk-example) that must correspond with the value provided in the bundle.json manifest from the previous step. Once the initialization is complete, we use ADK.navigation.add() to add an item to the left navigation bar. This item will have the label "ADK View A" and clicking on it will use ADK.modules.open() to open a module with the app view called view-a. This parameter can either be an actual navigational route (e.g. view.html) or a string that will correspond to a JavaScript or TypeScript file with the same name located in the src/views directory.
Let's proceed to build the app view itself in a file named view-a.jsx (or view-a.tsx if you're using TypeScript) within src/views.
src/views/view-a.jsx
1
import * as React from 'react';
2
import * as ADKReact from '@symphony-ui/adk-react';
3
import { Badge, Icon } from '@symphony-ui/uitoolkit-components';
4
import { useClientTheme, useUserReferenceId } from '@symphony-ui/adk-react';
5
import './view-a.css';
6
7
const ViewA = () => {
8
const { name: theme, layout } = useClientTheme();
9
const userId = useUserReferenceId();
10
11
return (
12
<div className="main-view">
13
<header>
14
<h1>
15
<Icon iconName="market-place" className="header-icon" />
16
Welcome to ADK View A!
17
</h1>
18
</header>
19
<main>
20
<hr className='tk-my-2' />
21
<h3>Meta Information</h3>
22
<div>
23
<strong>Theme</strong>: current theme is <Badge variant='positive'>{theme}</Badge> and <Badge variant='positive'>{layout}</Badge>
24
</div>
25
<div>
26
<strong>User Reference Id</strong>: <Badge variant='positive'>{userId}</Badge>
27
</div>
28
<hr className='tk-my-2' />
29
</main>
30
</div>
31
);
32
};
33
34
ADKReact.createView(<ViewA />, { id: 'adk-example' });
The contents of this app view are entirely arbitrary. You can choose not to use Symphony's UI Toolkit and employ other component libraries of your choice. The only required line here is calling ADKReact.createView() at the end, passing in your component and a configuration object pointing to the same app id as before.
For aesthetics, let's define some styling in src/views/view-a.css.
src/views/view-a.css
1
.main-view {
2
font-family: "Segoe UI", Roboto, sans-serif;
3
margin: 1rem;
4
}
5
.main-view header .header-icon { margin-right: 1rem }
6
.main-view main {
7
display: flex;
8
flex-direction: column;
9
gap: .5rem;
10
}
11
.main-view main hr { width: 100% }

Start the App

We can now start the app using:
npm start
This starts a local development server on https://localhost:4000. Note that this is a TLS-enabled site because all extension apps need to be loaded from TLS-enabled sites. However, because this is a development server, the certificate is self-signed and not trusted by any browser.
Visit https://localhost:4000 in your browser to accept the security warning about the untrusted self-signed certificate. Skipping this step will cause the extension app to not load within Symphony in the next step.

Load the App in Symphony

There are 2 ways to load an extension app into Symphony. For development purposes, we will be using the bundle injection method to temporarily load the app into the current session.
Beyond local development testing, you should get your pod administrator to create a corresponding app entry in the Admin Portal by uploading the bundle.json file.
We can now load the app by injecting the bundle URL as a parameter named bundle behind a pod URL. For example, if you are using the developer sandbox located at develop2.symphony.com, visit the following URL in your browser:
https://develop2.symphony.com/?bundle=https://localhost:4000/bundle.json

Test the App

Acknowledge the warning about being in developer mode. You should notice that a new left navigation item appears and opens an app view when clicked on.

Next Steps

Now that you have built a view-driven Extension App, you can proceed to build out your view and add more as required to complete your app.
Last modified 1mo ago