Agenda
Marketplace Website
- Improve UX for search experience on market website
New connectors
- Component Utility
- Keycloak Connector
Connector Improvements
- deepl: Add param options to make Deepl API usable in a more flexible way
Market website
Improve UX for search experience on market website
So far when you have clicked on the magnifyer glass on top right of the market website you have been forwarded to the developer space.

This has been changed so you stay on the market website when searching.

The search space is
https://market.axonivy.com/
https://www.axonivy.com/
https://developer.axonivy.com/
New connectors
Keycloak connector
With AxonIvy V12 it is possible to integrate keycloack as identity provider https://developer.axonivy.com/doc/12.0/engine-guide/integration/identity-provider/keycloak/index.html. This allows users to be managed in Keycloak.
A whole range of use cases are imaginable that make it necessary to send data FROM the AxonIvy application TO Keycloak. For example, imagine a workflow in AxonIvy in which new users are to be approved.
This connector is intended for these use cases.
Pattern Demos
There are many scenarios that developers have to solve again and again in Axon Ivy, such as:
- the locking of tasks
- Admin task for error handling
- Parallelization of tasks
- Scheduled and manually startable background jobs
- customizing the Primeface widget “Input Text”
- Validation of fields
Here we show you how our PRO developers typically solve these tasks in customer projects.
Connector Improvements
Deepl

The sub callable to translate files or text is limited in its parameters and therefore we cannot use the full Deeply API. E.g. when we have Text which contains HTML tags we would need to store the text as HTML file and then pass use the translate(file, targetLanguage) sub call instead of just using the translate(text, targetLanguage) with a API parameter tag_handling = html.
Solution
Additional sub callable starts that can take options for the API call.
Describe alternatives you've considered
Just using the REST client without the connector sub callable.