Primefaces Theme per Application
(Since 6.0.1)

The Primefaces theme can now be configured per application and session. There is a new application configuration property available in the Admin UI to configured it. If it is not configured the default theme is used.

See Engine Guide > Miscellaneous > Html Dialogs > Primefaces Theme for more information.

Thread Pool Configuration
(Since 6.0.2)

The number of threads that are used by thread pools in Axon.ivy can now be configured with system properties:

• ThreadPool.*.CorePoolSize: Number of threads used at least by the thread pool.
• ThreadPool.*.MaximumPoolSize: Maximum number of threads used by the thread pool.

The following attributes of thread pools can be monitored with JMX:

• corePoolSize: Number of threads used at least by the thread pool.
• maximumPoolSize: Maximum number of threads used by the thread pool.
• poolSize: Current number of threads in the thread pool.
• activeCount: Number of threads currently in use (not idle).
• queueSize: Number of jobs in the queue waiting for a free thread to execute it.

See Engine Guide > Administration > System Properties and Engine Guide > Monitoring > Java Management Extensions (JMX) > Provided MBeans for more information.

New Process Engine

Completly new and rewritten process engine. Based on the latest available technologies.

100% Java

100% implemented in Java.
IvyScript is no longer used in the engine itself.
Completly new java based execution model. There is no longer a PetriNet model used to execute your processes.

Improved Performance

The new process engine is 20% faster. This really boost your processes.

The startup of the Axon.ivy Engine is 50% faster.

The portal

The new portal provides a smart overview for users to start their daily work. It's capable of loading tasks and processes from any application of one or multiple ivy servers if the same user exists on that application. It has been built by developers for developers. Feel free to customize it.

Three users are created as initial defaults:

• admin: with same password
• demo: with same password
• guest: with same password

Customizable Error Pages

The content and appearance of the ivy error page can now be customized.

It is possible to adjust the default error page webapps/ivy/ivy-error-page.xhtml. Alternatively custom error pages can be defined in webapps/ivy/WEB-INF/web.xml.

See also the chapter Configuration -> Error Handling -> Custom Error Page in the Engine Guide.

REST API

• HTTP GET /ivy/api/{application name}/engine/info - Returns the version and the name of the engine.
• HTTP GET /ivy/api/{application name}/workflow/task/{taskId} - Returns the task with the given task identifier.
• HTTP GET /ivy/api/{application name}/workflow/tasks - Returns the tasks the authenticated user can work on.
• HTTP GET /ivy/api/{application name}/workflow/tasks/count - Returns the number of tasks the authenticated user can work on.
• HTTP GET /ivy/api/{application name}/workflow/case/{caseId}/document/{documentId} - Returns the content of the document.

New certificate

The client libraries for the Rich Dialog technology in this release are signed with a new certificate. The certificate is now issued to AXON IVY AG. ivyTeam the former provider company of Axon.ivy Designer and Engine was merged into this new company. All users of Rich Dialog UI's will see a security warning dialog the first time they start the process/application on a new Designer/Engine.

See also the official information on the Java website for more information.

Java 8

Axon.ivy Designer is now bundled with the Java 8 JRE. If you use Rich Dialogs in your projects, make sure that your users work with Java 8.

Enhanced Error Messages and Status Codes

The responses and corresponding HTTP status codes have been enhanced for task-resume requests. Now, the following status codes are returned in case of failure:

• 403 - FORBIDDEN: The user is not allowed to work on the task.
• 404 - NOT FOUND:
  • The task does not exist.
  • The task is in an unavailable state.
  • The task was finished and the user was not allowed to work on it.
• 409 - CONFLICT: The user is allowed to work on the task but:
  • The task was finished by another user.
  • Another user is currently working on the task.

Java 8