Who is this article for?

Existing customers who want to understand how Ideagen solutions and Mazlan are updated automatically.

Ideagen's single sign on is required.

Ideagen applies updates, patches and fixes automatically. This article explains what that means in practice, what it does and doesn't cover, and what customers can expect.

The update process

We automatically roll out updates, patches and fixes to keep your sign in portal and Mazlan running securely and smoothly. You don't need to approve these in advance; we handle it in the background so things just keep working.

Why updates are automatic

• Security fixes are time-sensitive. Vulnerabilities are patched as soon as a fix is ready, not on a fixed review cycle. An approval step would delay that.
• Environments stay consistent. If updates were optional, customer environments would drift onto different versions over time, making support and testing harder.
• The changes involved are low-risk by design. This process covers patches, fixes and incremental maintenance changes — not structural or behavioural changes to the product.

Important note: Ideagen may automatically deploy maintenance updates, patches and fixes to the Software (including to validated environments) to maintain security and performance, without requiring your prior consent.

Scope of updates

Automatic deployment applies to your sign in portal (i.e. the hub and its AI features, including Mazlan). It does not extend to a customer's core business solution or connected systems. Deployments and updates are independent of your main solution; the two are decoupled by design.

Changes that would affect how you use the core Ideagen solution (e.g. new features, interface changes, anything requiring a decision on your part) are not deployed through this automatic channel. Those are communicated separately.

What happens before an update reaches you

• Internal testing against current functionality
• Staged rollout to a subset of environments before wider release
• Monitoring after deployment to catch unexpected issues
• Rollback capability if a problem is identified

What this means for you

No action required:

• No need to review or approve individual patches, fixes, or maintenance updates
• No maintenance window to schedule
• No approval step to complete

What to expect:

• Your sign in portal and and any Mazlan capability continues to function normally through and after an update
• Your validated core product is unaffected, since this sits outside its validation boundary and updates independently of it
• Feature or interface changes are communicated separately from routine patches