Angular SDK
FlowxProcessRenderer is a low code library designed to render UI configured via the Flowx Process Editor.
Breaking changes: Starting with version 4.0 the ui-sdk will no longer expect the authToken to be present in the LOCAL_STORAGE. Instead, the authToken will be passed as an input to the flx-process-renderer component. This is mandatory for the SSE to work properly.
Prerequisites
- Node.js min version 20 - Download Node.js
- Angular CLI version 19. Install Angular CLI globally using the following command:
This will allow you to run ng related commands from the terminal.
Angular project requirements
Your app MUST be created using the NG app from the @angular/cli~19 package. It also MUST use SCSS for styling.
To install the npm libraries provided by FLOWX you will need to obtain access to the private FLOWX Nexus registry. Please consult with your project DevOps.
The library uses Angular version @angular~19, npm v10.8.0 and node v18.20.4.
If you are using an older version of Angular (for example, v16), please consult the following link for update instructions:
Installing the library
Use the following command to install the renderer library and its required dependencies:
Replace <version>
with the correct version corresponding to your platform version.
To find the right version, navigate to: Release Notes → Choose your platform version → Deployment guidelines → Component versions.
A few configurations are needed in the projects angular.json
:
- in order to successfully link the pdf viewer, add the following declaration in the assets property:
Initial setup
Once installed, FlxProcessModule
will be imported in the AppModule
as FlxProcessModule.withConfig({})
.
You MUST also import the dependencies of FlxProcessModule
: HttpClientModule
from @angular/common/http
Theming
Component theming is done through the @flowx/angular-theme
library. The theme id is a required input for the renderer SDK component and is used to fetch the theme configuration. The id can be obtained from the admin panel in the themes section.
Authorization
Every request from the FlowX renderer SDK will be made using the HttpClientModule of the client app, which means those requests will go through every interceptor you define here. This is most important to know when building the auth method as it will be the job of the client app to intercept and decorate the requests with the necessary auth info (eg. Authorziation: Bearer ...
).
It’s the responsibility of the client app to implement the authorization flow (using the OpenID Connect standard). The renderer SDK will expect the authToken to be passed to the flx-process-renderer
as an input.
The withConfig()
call is required in the application module where the process will be rendered. The withConfig()
method accepts a config argument where you can pass extra config info, register a custom component, service, or custom validators.
Custom components will be referenced by name when creating the template config for a user task.
Custom validators will be referenced by name (currentOrLastYear
) in the template config panel in the validators section of each generated form field.
The error that the validator returns MUST match the validator name.
The entry point of the library is the <flx-process-renderer></flx-process-renderer>
component. A list of accepted inputs is found below:
Parameters:
Name | Description | Type | Mandatory | Default value | Example |
---|---|---|---|---|---|
apiUrl | Your base url | string | true | - | https://yourDomain.dev |
processApiPath | Process subpath | string | true | - | onboarding |
authToken | Authorization token | string | true | - | ‘eyJhbGciOiJSUzI1NiIsIn…‘ |
themeId | Theme id used to style the process. Can be obtained from the themes section in the admin | string | true | - | ‘123-456-789’ |
processName | Identifies a process | string | true | - | client_identification |
processStartData | Data required to start the process | json | true | - | { "firstName": "John", "lastName": "Smith"} |
debugLogs | When set to true this will print WS messages in the console | boolean | false | false | - |
language | Language used to localize the application. | string | false | en | - |
keepState | By default all process data is reset when the process renderer component gets destroyed. Setting this to true will keep process data even if the viewport gets destroyed | boolean | false | false | - |
isDraft | When true allows starting a process in draft state. *Note that isDraft = true requires that processName be the id (number) of the process and NOT the name. | boolean | false | false | - |
legacyHttpVersion | Set this to true only for HTTP versions < 2 in order for SSE to work properly. Can be omitted otherwise. | boolean | false | false | - |
projectInfo | Information about the project that contains the process that is being run. | object | true | - | { projectId: '1234-5678-9012' } |
locale | Locale used to localize the application. | string | false | en-US | ’en-US’ |
cache | Caching of static resources | boolean | false | true | - |
Data and actions
Custom components will be hydrated with data through the $data input observable which must be defined in the custom component class.
Component actions are always found under data
-> actionsFn
key.
Action names are configurable via the process editor.
Custom component validation
Custom components can validate their own status. We can inject the FLX_VALIDATOR_SERVICE
service and use it to validate the component. Whe service exposes the following properties:
validate(isValid: boolean)
- used to validate the componentsaveData(data: any)
- used to save datavalidated$
- used to monitor external submission from the process
Example of the a custom component that validates an input with a required validator:
Custom Interceptors
- Starting from the FlowX SDKs version 4.6, the Angular
HttpClientModule
is no longer use internally to make HTTP requests. Thus, we have a new mechanism that allows you to create custom interceptors for handling HTTP requests.
Request Interceptors
- Here is an example that illustrates how to create an interceptor that adds a custom header to all outgoing requests:
Response Interceptors
- Here is an example that illustrates how to create an interceptor that shows a message when a response errors out:
Interceptors that use Dependency injection
- If you need to use a service in your interceptor, you can use provider factories coupled with the
deps
property to inject the service into the interceptor:
Using custom icons
The SDK provides a mechanism for using custom icons. Providers for custom icons should be included in the main app module in order to be available for the whole application.
Enumerations and translations
The SDK library provides a mechanism for handling enumerations and translations. The api for the method that handles enumerations is provided by the getEnumeration
method which is Promise
based.
These methods should only be used in custom components and within a process context because internal requests depend on the presence of a running project details.
Custom enumerations
Translations
The SDK provides a FlxLocalizePipe
that allows you to manage translations within your application. The pipe is standalone and can be used both in templates and in custom components.
- Here is an example of how to use the pipe in a template:
- Here is an example of how to use the pipe in a custom component:
Caching
The SDK provides a caching mechanism for static resources. The cache is enabled by default and can be disabled by setting the cache
input of the flx-process-renderer
component to false
. When turned on, the cache will store the static resources in the browser’s cache storage.
In order to reset the cache, you can go to the Application
(chrome) or Storage
(firefox) tab in the browser Dev tools and either clear the cache or disable the cache for the current site.
@Dragos - insert Chrome and Firefox screenshots here
Interacting with the process
Data from the process is communicated via Server Send Event protocol under the following keys:
Name | Description | Example | |
---|---|---|---|
Data | data updates for process model bound to default/custom components | ||
ProcessMetadata | updates about process metadata, ex: progress update, data about how to render components | ||
RunAction | instructs the UI to perform the given action |
Task management component
The flx-task-manager
component is available in the FlxTaskManagementComponent
. To use it, import the required module in your Angular project:
Usage
Include the component in your template:
Parameters:
Name | Description | Type | Mandatory | Example |
---|---|---|---|---|
apiUrl | Endpoint where the tasks are available | string | ✅ | https://yourDomain.dev/tasks |
authToken | Authorization token | string | ✅ | (retrieved from local storage) |
appId | The application ID | string | ✅ | (retrieved dynamically) |
viewDefinitionId | The view configuration identifier | string | ✅ | (retrieved dynamically) |
themeId | The theme identifier | string | ❌ | (retrieved dynamically) |
language | The selected language | string | ❌ | (retrieved dynamically) |
locale | The localization setting | string | ❌ | (retrieved dynamically) |
buildId | The current build identifier | string | ❌ | (retrieved dynamically) |
staticAssetsPath | Path for static resources | string | ❌ | (set via environment) |
Coding style tests
Always follow the Angular official coding styles.
Below you will find a Storybook which will demonstrate how components behave under different states, props, and conditions, it allows you to preview and interact with individual UI components in isolation, without the need for a full-fledged application:
Storybook (v4.7.0)
Was this page helpful?