We have invested a lot of time to have a loose coupling between the workflow ui Axon Ivy Portal delivered by the platform and the Axon Ivy Projects which is part of your Axon Ivy Application. This gives you a big value: No migration pain π¦. You should be able to update the Axon Ivy Portal without ever touching your Axon Ivy Project. So you can benefit from all bug fixes and maybe back-ported features from Axon Ivy Portal on a LTS train for free π!
This is only possible if you start using the iFrame approach. This is the only way, which we can guarantee that you have no dependencies to Axon Ivy Portal.
Development
- Basically you can develop your Axon Ivy Processes without ever integrating the Axon Ivy Portal.
- If you like to see how your processes looks and feels at runtime so just install the Axon Ivy Portal in Axon Ivy Designer via Axon Ivy Market. There is a shortcut to import the Axon Ivy Portal.
Don'ts!
β Don't change anything in the portal and push it to your own repository
β Don't have any maven dependency to the portal itself
Operation
- Install the Axon Ivy Portal in an own application as part of the default security context.
- Install your Axon Ivy Projects in an own Axon Ivy Application
πRather by installing this by hand, automate the deployment in a build pipeline - and please run the Axon Ivy Engine in a containerized environment, even if it's just Docker.
These two applications has a technical boundary to each other, but the security context is spanning a business context where all users, roles, tasks and cases belongs together.
Default security context?
In Axon Ivy 10, application lives in a security context. Most of you only need one security context, one which is already pre-installed - the default one. There is only one use case to create more than one security contexts - for multi tenancy.