This version of ISOWARE requires Java 21. Java 21 can currently be downloaded here: https://adoptium.net/temurin/releases. Please note that this version of Java does not include an automatic update function, so you must make sure to download and install new versions at appropriate intervals. Alternatively, Oracle's version can be used, but please note the license terms when using this.
It is now possible to insert background images into Swimlane shapes:

When editing Swimlane shapes, the following new elements for handling background images can now be seen at the bottom:

It is now possible to share a process by creating a sharing link or by sharing a process with another organization
Processes can be shared by:
To copy a sharing link, you must have the Edit processes right:
This method is used to send a direct link to a specific process. If the link is sent to a recipient whose email address is registered to a user in ISOWARE, the link works in the same way as you normally open a process in ISOWARE. That is, you must be logged in to be able to view the process. This type of link is called a Internal User Link. If this type of link is sent to an ISOWARE user who does not have the necessary permissions to view/edit the process, ISOWARE creates temporary permissions for the specific process.
If the link is sent to a recipient whose email address is not registered with a user in ISOWARE, the link contains additional information that gives the recipient guest access to the process in question. In this case, the link only provides access to the specific process. This type of link is called a Shareable link.
To send a link to a process as an email, you must have the Edit processes permission:
Links of the type Shareable link and Link to internal user, where the system has created temporary permissions for the specific process, are basically valid for 30 days (can be changed). If access is desired to be blocked earlier. This can be achieved by clicking on the share in the list and selecting Unshare
When a process in organization 1 is shared with organization 2, the process becomes part of organization 2. This means that users in organization 2 have the same access to the shared process as they have to other processes in organization 2.
This is only possible if an administrator has made the necessary setup of the organization to which the process in question belongs. This is described in the help section Setting up process sharing with other organizations
To share a process with another organization, you must have the Edit processes right:
The existing report sharing feature has been updated to have the same capabilities as the new Process Sharing feature.
Reports can now be shared by:
To copy a sharing link, you must have the Edit own/all reports permission:
This method is used to send a direct link to a specific report. If the link is sent to a recipient whose email address is registered to a user in ISOWARE, the link works in the same way as opening a report in ISOWARE normally. That is, you must be logged in to view the report. This type of link is called a Link to internal user. If this type of link is sent to an ISOWARE user who does not have the necessary permissions to view/edit the report, ISOWARE creates temporary permissions for the specific report.
If the link is sent to a recipient whose email address is not registered to a user in ISOWARE, the link contains additional information that gives the recipient guest access to the report in question. In this case, the link only provides access to the specific report. This type of link is called a Shareable link.
To send a link to a report as an email, you must have the Edit own/all reports permission:
Links of the type Shareable link and Link to internal user, where the system has created temporary permissions for the specific report, are generally valid for 30 days (can be changed). If you want to block access earlier, you can do so by clicking on the share in the list and selecting Unshare
When a report in organization 1 is shared with organization 2, the report becomes part of organization 2. This means that users in organization 2 have the same access to the shared report as they have to other reports in organization 2.
This is only possible if an administrator has made the necessary setup of the report template on which the report in question is based. See more in the help section Setting up report sharing with other organizations
To share a report with another organization, you must have the Edit own/all reports right:
To comply with heightened cybersecurity standards, including NIS2 and ISO 27001, ISOWARE now introduces Multi-Factor Authentication (MFA / 2FA). MFA adds an essential layer of security by requiring a 6-digit one-time code from an authenticator app upon login, in addition to username and password.
ISOWARE utilizes the open TOTP standard (Time-based One-Time Password / RFC 6238). This allows users to choose any standard authenticator app, including:
MFA can be enabled per user by an administrator:
The first time a user logs in after MFA has been enabled, an onboarding wizard is displayed:
During subsequent logins, the user enters their username and password, followed by the 6-digit code from their phone.
Users can select Trust this browser for 30 days on trusted devices to skip the verification prompt for 30 days per browser.
If an employee loses or replaces their smartphone, an administrator can reset the user's MFA pairing with a single click in the user's profile, allowing the user to pair a new device during their next login.
ISOWARE 17.2.0 introduces full support for the Model Context Protocol (MCP) and enterprise AI assistants, including Microsoft 365 Copilot, Microsoft Copilot Studio, Claude, and Cursor. This empowers corporate AI agents to securely query and retrieve information directly from ISOWARE.
ISOWARE now includes a built-in MCP server (via Server-Sent Events at /rest/mcp/sse) and a standardized OpenAPI 3.0 specification (/rest/mcp/openapi.json), making it easy to connect Copilot Studio as a Custom Connector or MCP agent.
Security and confidentiality remain paramount:
Connected AI agents have automatic access to the following toolset:
[Title](url).In addition to Microsoft Copilot integration, ISOWARE also supports an optional built-in AI chatbot directly inside the ISOWARE web interface, powered by Google Vertex AI, enabling users to ask procedural questions directly in the browser.