Valtimo offers the functionality needed to create and add plugins to Valtimo implementations.
To create a custom plugin in your project, the following dependency is needed:
- valtimo:plugin
for example:
implementation("com.ritense.valtimo:plugin:$valtimoVersion") A plugin can be created with the @Plugin annotation on the class. All classes with the plugin annotation are
detected when the application is started. The plugin class should not be a Spring bean.
For example:
@Plugin(
key = "twitter",
title = "Twitter Plugin",
description = "Tweet and retweet with this new Twitter plugin"
)
class TwitterPlugin {
...A plugin can be configured with properties. Properties can be added to the plugin class with the @PluginProperty
annotation.
For example:
@PluginProperty(key = "username", secret = false)
private lateinit var username: StringBy setting the secret attribute in this annotation to true the plugin property will be marked as a secret. This is
meant to be used for sensitive information (e.g. passwords or API keys). Secrets are encrypted before being stored in
the database and will be automatically decrypted before use in the plugin.
These things should be kept in mind when creating the frontend components for secrets:
- When editing an existing plugin configuration, the value will not be sent back to the frontend to avoid exposing sensitive data.
- Only when submitting a value that is not null or an empty string will the property be updated.
- This functionality requires an application property
valtimo.plugin.encryption-secret. The value of this property determines the encryption key. The encryption secret has to be EXACTLY 16, 24 or 32 bytes.
A plugin class can have methods that are marked as actions through the @PluginAction annotation. These methods can
then be used in a process definition through the use of process links.
A single action can be linked to a task, and will run when that task is reached.
For example:
@PluginAction(
key = "post-tweet",
title = "Post tweet",
description = "Post a tweet on twitter.",
activityTypes = [ActivityTypeWithEventName.SERVICE_TASK_START]
)
fun postTweet(execution: DelegateExecution, postTweetProperties: PostTweetProperties) {
...A plugin class can have methods that need to be run on plugin creation, update or deletion. This can be achieved with the @PluginEvent annotation.
These methods will then be invoked during the corresponding event of a Plugin Configuration lifecycle.
For example, startListener() will be executed when a Plugin Configuration is being created:
@PluginEvent(invokedOn = [EventType.CREATE])
fun startListener() {
...Available event types: CREATE, UPDATE and DELETE.
It is possible to run a method on all three of these events by specifying so in the invokedOn argument of the annotation e.g. @PluginEvent(invokedOn = [EventType.CREATE, EventType.DELETE]).
A PluginEventInvocationException with references to the plugin and any underlying exceptions will be thrown should a method ran as part of an event fail.
NB! Limitations
- If the annotation contains duplicate event types, then the method will still only be invoked once per event type per annotation.
@PluginEvent(invokedOn = [EventType.CREATE, EventType.DELETE, EventType.CREATE])
fun willRunOnceOnCreateAndDelete() {
...- Only methods without arguments are supported.
- Annotated methods are resolved in alphabetical order.
The newly created plugin class can not be used yet because Valtimo does not know how to create the new plugin. This
problem is solved by creating a factory that extends the PluginFactory and registering it as a bean.
The create() method has to be implemented to inject Spring beans or other objects that are necessary. This does not
include plugin properties, as those are set automatically.
For example:
@Component
class TwitterPluginFactory(
pluginService: PluginService,
private val twitterClient: TwitterClient
) : PluginFactory<TwitterPlugin>(pluginService) {
override fun create(): TwitterPlugin {
return TwitterPlugin(twitterClient)
}
}Plugin categories denote a commonality between plugins. They can be applied to interfaces, so any plugin implementing this will belong to that category. When a plugin implements more than one interface with a category, it belongs to multiple categories. This can be used by the backend to create plugins that rely on other plugins to be configured, and can be used by the frontend to search for plugins in a specific category.
A plugin implementing an interface annotated with @PluginCategory can be autowired into a @PluginProperty of
the same type on a different plugin.
The example below explains the implementation of a tweet supplier for a Twitter plugin, which can then be used to send out actual tweets.
First, the interface is defined that includes the required functionality. @PluginCategory with a key is added so that
can be used to find configurations of that type in the frontend:
@PluginCategory(key = "tweet-supplier")
interface TweetSupplier {
fun supplyMessage() : String
}At least one implementation of the plugin is required. In this case, the PropertyTweetSupplier implements the
interface TweetSupplier and supports all required functionality. When searching for configurations for category
tweet-supplier, all stored PropertyTweetSupplier configurations are found.
@Plugin(
key = "property-tweet-supplier",
title = "Property tweet supplier",
description = "Get a message from a property"
)
class PropertyTweetSupplier: TweetSupplier {
@PluginProperty(key = "message", secret = false)
private lateinit var message: String
fun supplyMessage(): String {
return message
}
}When creating a configuration of the TwitterPlugin, the frontend should get and show a list of all available
configuration of type tweet-supplier. The ID of the chosen configuration will be part of the properties submitted for
the creation of the TwitterPlugin configuration. The @PluginProperty can reference the interface type corresponding
to the category. The plugin will then be automatically injected with the corresponding configuration when using the
TwitterPlugin.
@Plugin(
key = "twitter",
title = "Twitter Plugin",
description = "Tweet and retweet with this new Twitter plugin"
)
class TwitterPlugin {
@PluginProperty(key = "tweetSupplierConfigurationId", secret = false)
private lateinit var tweetSupplier: TweetSupplier
@PluginAction(
key = "post-tweet",
title = "Post tweet",
description = "Post a tweet on twitter.",
activityTypes = [ActivityTypeWithEventName.SERVICE_TASK_START]
)
fun postTweet(execution: DelegateExecution, postTweetProperties: PostTweetProperties) {
val message = tweetSupplier.supplyTweet()
...
}
}To develop a frontend plugin, the library @valtimo/plugin provides several interfaces which a frontend
plugin must conform to, in order to be used in an implementation.
First, a plugin specification conforming to the PluginSpecification interface needs to be created. Below is an example specification with explanations for each property:
import {PluginSpecification} from '@valtimo/plugin';
import {SamplePluginConfigurationComponent} from './components/sample-plugin-configuration/sample-plugin-configuration.component';
import {SAMPLE_PLUGIN_LOGO_BASE64} from './assets';
import {SampleActionConfigurationComponent} from './components/sample-action-configuration/sample-action-configuration.component';
const samplePluginSpecification: PluginSpecification = {
/*
The plugin definition key of the plugin.
This needs to be the same as the id received from the back-end
*/
pluginId: 'sampleplugin',
/*
A component of the interface PluginConfigurationComponent, used to configure the plugin itself.
*/
pluginConfigurationComponent: SamplePluginConfigurationComponent,
// Points to a Base64 encoded string, which contains the logo of the plugin.
pluginLogoBase64: SAMPLE_PLUGIN_LOGO_BASE64,
functionConfigurationComponents: {
/*
For each plugin action id received from the back-end, a component is provided of the interface FunctionConfigurationComponent.
These are used to configure each plugin action.
*/
'sample-action': SampleActionConfigurationComponent,
},
/*
For each language key an implementation supports, translation keys with a translation are provided below.
These can then be used in configuration components using the pluginTranslate pipe or the PluginTranslationService.
At a minumum, the keys 'title' and 'description' need to be defined.
Each function key also requires a translation key. In this case, the key 'sample-action' is added.
*/
pluginTranslations: {
nl: {
title: 'Voorbeeld-plug-in',
description: 'Een uitstekende plug-in om mee te beginnen.',
'sample-action': 'Voorbeeldactie',
configurationTitle: 'Configuratienaam',
url: 'URL',
message: 'Bericht',
...
},
en: {
title: 'Sample plugin',
description: 'A great plugin to get started with.',
'sample-action': 'Sample action',
configurationTitle: 'Configuration name',
url: 'URL',
message: 'Message',
...
},
de: {
title: 'Beispiel-Plugin',
description: 'Ein tolles Plugin für den Einstieg.',
'sample-action': 'Beispielaktion',
configurationTitle: 'Konfigurationsname',
url: 'URL',
message: 'Nachricht',
...
},
},
};
export {samplePluginSpecification};Plugin logos are provided as a Base64 encoded string. This string is then imported in the plugin specification as shown above. The size has to be kept down to a minimum, so logo images must be resized before encoding them to Base64. A maximum height of 60 pixels is advised.
This website is good for encoding images to Base64. After uploading, click show code,
and then copy the string under For use in <img> elements:.
Here is a sample file of a Base64 encoded logo:
const SAMPLE_PLUGIN_LOGO_BASE64 =
'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAgAAAAIACAYAAAD0eNT6AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAABBJJREFUeNrswTEBAAAAwqD1T20Hb6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOA3AQYAAvAAAXL/+O0AAAAASUVORK5CYII=';
export {SAMPLE_PLUGIN_LOGO_BASE64};As shown in the plugin specification section, plugin configuration components need to
conform to the interface PluginConfigurationComponent. Below the interface is shown, with a comment for each required
property.
import {Observable} from 'rxjs';
import {EventEmitter} from '@angular/core';
/*
The required data outputted from the component.
In each case, a configuration title must be provided by the configuration component.
The rest of the properties must conform to the properties expected by the back-end.
*/
interface PluginConfigurationData {
configurationTitle: string;
[key: string]: any;
}
/*
The generic interface for a configuration component.
All of these properties must be implemented by the plugin configuration component,
since this interface is extended below.
*/
interface ConfigurationComponent {
/*
An observable the component must subscribe to.
If this observable is triggered, the component must check if its configuration data is valid,
and if so, emit this data on the configuration EventEmitter from the interface below.
*/
save$: Observable<void>;
/*
A boolean observable which the component must subscribe to.
If true, all input in the component must be disabled.
*/
disabled$: Observable<boolean>;
// The plugin definition key provided to the component. For the sample plugin, this would be 'sampleplugin'
pluginId: string;
/*
When the values of the inputs in the configuration component change,
the configuration component must continuously check whether the configuration data (all inputs combined) is valid.
This EventEmitter outputs a boolean. So if the data is valid, output 'true', if invalid, output 'false'.
*/
valid: EventEmitter<boolean>;
}
interface PluginConfigurationComponent extends ConfigurationComponent {
/*
An observable input which includes configuration data if the plugin had already been saved previously,
and is now being modified. Subscribe to this observable to prefill the input fields in the component.
*/
prefillConfiguration$?: Observable<PluginConfigurationData>;
/*
As mentioned before, if the observable of the 'save$' input property is triggered,
check if the configuration data is valid. If so, output this data through this EventEmitter.
*/
configuration: EventEmitter<PluginConfigurationData>;
}As mentioned, the plugin configuration component listens to prefill data of the interface PluginConfigurationData,
and outputs configuration data of this same interface. It is advised to extend this interface and further specify what
data the plugin requires. For the sample plugin, this would be:
import {PluginConfigurationData} from '@valtimo/plugin';
interface SamplePluginConfig extends PluginConfigurationData {
url: string;
}
export {SamplePluginConfig};How a configuration component for the sample plugin can be implemented is shown below.
The way this is implemented can differ, as long as the interfaces are conformed to.
Below is sample code of implementing the component using components from the library @valtimo/user-interface.
import {Component, EventEmitter, Input, OnDestroy, OnInit, Output} from '@angular/core';
import {PluginConfigurationComponent} from '@valtimo/plugin';
import {BehaviorSubject, combineLatest, Observable, Subscription, take, tap} from 'rxjs';
import {SamplePluginConfig} from '../models';
@Component({
selector: 'valtimo-sample-plugin-configuration',
templateUrl: './sample-plugin-configuration.component.html',
styleUrls: ['./sample-plugin-configuration.component.scss'],
})
export class SamplePluginConfigurationComponent
// The component explicitly implements the PluginConfigurationComponent interface
implements PluginConfigurationComponent, OnInit, OnDestroy
{
@Input() save$: Observable<void>;
@Input() disabled$: Observable<boolean>;
@Input() pluginId: string;
// If the plugin had already been saved, a prefill configuration of the type SamplePluginConfig is expected
@Input() prefillConfiguration$: Observable<SamplePluginConfig>;
// If the configuration data changes, output whether the data is valid or not
@Output() valid: EventEmitter<boolean> = new EventEmitter<boolean>();
// If the configuration is valid, output a configuration of the type SamplePluginConfig
@Output() configuration: EventEmitter<SamplePluginConfig> =
new EventEmitter<SamplePluginConfig>();
private saveSubscription!: Subscription;
private readonly formValue$ = new BehaviorSubject<SamplePluginConfig | null>(null);
private readonly valid$ = new BehaviorSubject<boolean>(false);
ngOnInit(): void {
this.openSaveSubscription();
}
ngOnDestroy() {
this.saveSubscription?.unsubscribe();
}
formValueChange(formValue: SamplePluginConfig): void {
this.formValue$.next(formValue);
this.handleValid(formValue);
}
private handleValid(formValue: SamplePluginConfig): void {
// The configuration is valid when a configuration title and url are defined
const valid = !!(formValue.configurationTitle && formValue.url);
this.valid$.next(valid);
this.valid.emit(valid);
}
private openSaveSubscription(): void {
/*
If the save observable is triggered, check if the configuration is valid, and if so,
output the configuration using the configuration EventEmitter.
*/
this.saveSubscription = this.save$?.subscribe(save => {
combineLatest([this.formValue$, this.valid$])
.pipe(take(1))
.subscribe(([formValue, valid]) => {
if (valid) {
this.configuration.emit(formValue);
}
});
});
}
}The corresponding template file looks like this:
<v-form
(valueChange)="formValueChange($event)"
*ngIf="{
disabled: disabled$ | async,
prefill: prefillConfiguration$ ? (prefillConfiguration$ | async) : null
} as obs"
>
<v-input
name="configurationTitle"
[title]="'configurationTitle' | pluginTranslate: pluginId | async"
[margin]="true"
[defaultValue]="obs.prefill?.configurationTitle"
[disabled]="obs.disabled"
[required]="true"
>
<v-input
name="url"
[title]="'url' | pluginTranslate: pluginId | async"
[margin]="true"
[defaultValue]="obs.prefill?.url"
[disabled]="obs.disabled"
[required]="true"
>
</v-input>
</v-form>
Each plugin action received from the backend must have a corresponding function configuration component in the
frontend. Implementing these components works in much the same way as implementing the plugin configuration component,
The only difference is that function configuration components do not have to provide a configuration title.
Below is sample code for the sample plugin action with the id sample-action:
interface SampleActionConfig {
message: string;
}
export {SampleActionConfig};import {Component, EventEmitter, Input, OnDestroy, OnInit, Output} from '@angular/core';
import {FunctionConfigurationComponent} from '@valtimo/plugin';
import {BehaviorSubject, combineLatest, Observable, Subscription, take, tap} from 'rxjs';
import {SampleActionConfig} from '../models';
@Component({
selector: 'valtimo-sample-action-configuration',
templateUrl: './sample-action-configuration.component.html',
styleUrls: ['./sample-action-configuration.component.scss'],
})
export class SampleActionConfigurationComponent
// The component explicitly implements the FunctionConfigurationComponent interface
implements FunctionConfigurationComponent, OnInit, OnDestroy
{
@Input() save$: Observable<void>;
@Input() disabled$: Observable<boolean>;
@Input() pluginId: string;
@Input() prefillConfiguration$: Observable<SampleActionConfig>;
@Output() valid: EventEmitter<boolean> = new EventEmitter<boolean>();
@Output() configuration: EventEmitter<SampleActionConfig> =
new EventEmitter<SampleActionConfig>();
private saveSubscription!: Subscription;
private readonly formValue$ = new BehaviorSubject<SampleActionConfig | null>(null);
private readonly valid$ = new BehaviorSubject<boolean>(false);
ngOnInit(): void {
this.openSaveSubscription();
}
ngOnDestroy() {
this.saveSubscription?.unsubscribe();
}
formValueChange(formValue: SampleActionConfig): void {
this.formValue$.next(formValue);
this.handleValid(formValue);
}
private handleValid(formValue: SampleActionConfig): void {
const valid = !!(formValue.message);
this.valid$.next(valid);
this.valid.emit(valid);
}
private openSaveSubscription(): void {
this.saveSubscription = this.save$?.subscribe(save => {
combineLatest([this.formValue$, this.valid$])
.pipe(take(1))
.subscribe(([formValue, valid]) => {
if (valid) {
this.configuration.emit(formValue);
}
});
});
}
}<v-form
(valueChange)="formValueChange($event)"
*ngIf="{
disabled: disabled$ | async,
prefill: prefillConfiguration$ ? (prefillConfiguration$ | async) : null
} as obs"
>
<v-input
name="message"
[title]="'message' | pluginTranslate: pluginId | async"
[margin]="true"
[defaultValue]="obs.prefill?.message"
[disabled]="obs.disabled"
[required]="true"
>
</v-form>
The main app.module.ts needs to be updated as well. The @NgModule needs to have added imports:
@NgModule({
declarations: [
...
],
imports: [
...
SamplePluginModule
],
providers: [...,
{
provide: PLUGINS_TOKEN,
useValue: [
SamplePluginSpecification
],
},
],
bootstrap: [AppComponent]
})The main menu.ts needs to be updated as well:
export const menuItems = [
{
roles: [ROLE_ADMIN], title: 'Admin', iconClass: 'icon mdi mdi-tune', sequence: 6, children: [
...
{link: ['/plugins'], title: 'Plugins', sequence: 7},
...
]
}
];The template code shown above uses the pluginTranslate pipe to show translations from the plugin specification.
To use this, first import PluginTranslatePipeModule from @valtimo/plugin and add it to the imports array of the
plugin module. Now, the pluginTranslate pipe can be used in templates. It uses the following syntax:
<span>
{{ 'translationKey' | pluginTranslate: pluginId | async" }}
</span>
The pipe returns an observable, so do not forget to add | async at the end.
translationKey refers to one of the translation keys specified in the plugin specification.
pluginId refers to the plugin's definition key. For the sample plugin, this would be sampleplugin.
It is provided by the pluginId input on the configuration component by default.
If translation is to take place inside the component (as opposed to inside the template using the pipe),
the PluginTranslationService may be used, which is exported by @valtimo/plugin. It supports a translate method,
which returns an observable containing the translation, and an instant method, which returns a string containing the
translation.
Finally, after implementing the components and specification, a module has to be defined for the plugin. This module, together with the specification, is then imported in the app module as shown in on this page.
The sample plugin module would look like this:
import {NgModule} from '@angular/core';
import {CommonModule} from '@angular/common';
import {PluginTranslatePipeModule} from '../../pipes';
import {FormModule, InputModule} from '@valtimo/user-interface';
import {SamplePluginConfigurationComponent} from './components/sample-plugin-configuration/sample-plugin-configuration.component';
import {SampleActionConfigurationComponent} from './components/sample-action-configuration/sample-action-configuration.component';
@NgModule({
declarations: [SamplePluginConfigurationComponent, SampleActionConfigurationComponent],
imports: [CommonModule, PluginTranslatePipeModule, FormModule, InputModule],
exports: [SamplePluginConfigurationComponent, SampleActionConfigurationComponent],
})
export class SamplePluginModule {}