Platform Release Guide 2025A
Platform Release Guide 2025A
CiA Platform
Release Guide
QUALITY ENDORSEMENT – ISO9001 Quality Management Systems – Requirements
COPYRIGHT
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in
any form or by any means electronic, mechanical, photocopying, recording or otherwise, without the prior
permission of Technology One Limited.
SUPERSESSION CLAUSE
Upon receipt of this document, please ensure any earlier versions are destroyed. No earlier versions may be
retained without the written permission of Technology One Limited.
Contents
Objectives. ....................................................................................................................................................... 4
Introduction. .................................................................................................................................................... 6
3. Workplace ........................................................................................................................................... 10
3.1 New .............................................................................................................................................................10
3.2 Major Updates ............................................................................................................................................10
3.3 Updates .......................................................................................................................................................10
3.3.1 CCP-34742 - Global Menu Now Labelled 'More' When Opened ...............................................11
3.3.2 CCP-33246 - Share PII with T1Uni ..............................................................................................11
3.3.3 CCP-32338 - About Page Deprecated for SaaS Customers ........................................................12
6. Connect ............................................................................................................................................... 40
6.1 New .............................................................................................................................................................40
6.2 Major Updates ............................................................................................................................................40
6.3 Updates .......................................................................................................................................................40
Page 4 of 42
2025A Release Guide | CiA Platform
Page 5 of 42
2025A Release Guide | CiA Platform
Page 6 of 42
2025A Release Guide | CiA Platform
1. Course Information
This workbook covers 2025A development for CiA Platform.
The purpose is to provide information on key features and updates that are now available.
1.2 Prerequisites
Important: Prior Knowledge
Prior knowledge of CiA Platform functionality up to and including 2024B release is
required to complete this training.
Page 7 of 42
2025A Release Guide | CiA Platform
2. Discover Mode
Use the Discover button in the CiA footer to access information about what’s new or updated in a release.
TechnologyOne SaaS customers can also review the release notes.
Page 8 of 42
2025A Release Guide | CiA Platform
Page 9 of 42
2025A Release Guide | CiA Platform
3. Workplace
The workplace is your customisable launch pad for accessing CiA apps.
Your workplace helps you manage your workload. It alerts you to roles and functions with new, active, or
outstanding items requiring your attention, like the number of active purchase requisitions or a new report
available in the gallery. Many functions also let you see more details at a glance, right there in the workplace.
For example, you can see the number of tasks you need to action and how they are categorised without even
opening your Workflow Inbox.
The workplace's responsive design makes it easy to use regardless of screen size, so you can dive in deep at
your desk every day, take it to meetings with you on your tablet, or take advantage of every spare minute to
get tasks done quickly on your phone. Even if you work exclusively on a mobile device, the full-feature
workplace is at your fingertips.
3.1 New
No new features were developed in 2025A.
3.3 Updates
The following updates were developed in 2025A.
Function Code Function Name Title
$WORKPLACE Workplace Global Menu Now Labelled 'More' When Opened
Share PII with T1Uni
About Page Deprecated for SaaS Customers
Page 10 of 42
2025A Release Guide | CiA Platform
The menu accessed by selecting the More button in the CiA header has been renamed from "Menu" to "More".
This enhancement improves clarity for all users with consistent labelling of the More button and the menu that
it opens.
GO TO: More > Help and Assistance > TechnologyOne University > Workplace >
Workplace Actions and Settings Overview
When an organisation or individual user has not opted to redact personally identifiable information (PII), the
next time a user accesses the new TechnologyOne University, their university account will be updated with the
following information from their CiA user account:
Page 11 of 42
2025A Release Guide | CiA Platform
• Full family name (previously, only the initial of their family name was shared)
• Email address, which becomes their User ID in TechnologyOne University (previously, a random GUID
was used).
Including this information in the university account will enable more features of the learning platform to be
implemented, including email notifications, forums and reporting.
GO TO: More > Help and Assistance > TechnologyOne University > Workplace > Help
and Assistance > Try the New TechnologyOne University
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > Site-Wide Workplace Settings > TechnologyOne University
Administration
When More is selected in the CiA header, selecting the Settings option displays a sub-menu. In this sub-menu,
the About option either:
• Does not display when the environment is using the TechnologyOne SaaS platform. Instead, the
snapshot version being used by the environment is visible in the footer of the More menu; or
Page 12 of 42
2025A Release Guide | CiA Platform
• Displays when the environment is not using the TechnologyOne SaaS platform AND the user has
permission to view diagnostics. Selecting the About option lists software apps and versions in the
environment.
Removing the About option for SaaS customers ensures that they no longer see a menu option that is not
applicable to their environment.
GO TO: More > Help and Assistance > TechnologyOne University > Workplace >
Workplace Actions and Settings > Workplace Actions and Settings Overview
Page 13 of 42
2025A Release Guide | CiA Platform
4. System Administration
The System Administration functional group brings together all the administration and configuration tasks an
administrator may need to perform. It contains functions to manage:
• Access, security and authentications options to the TechnologyOne suite of products for users
• Setup screens to configure workplace, regional and site settings
• Options for configuring add-ins such as addressing Office 365 and Office Online integration
• Diagnostic tools for auditing and troubleshooting.
4.1 New
No new features were developed in 2025A.
Page 14 of 42
2025A Release Guide | CiA Platform
The Cleanup Parameters section in the TechnologyOne Connect function now directs users to the Information
Security function to configure their data retention policy.
In the Information Security function, the retention policy called TechOne Connect is automatically enabled. A
customer can also proactively manage the database space and file storage used by TechnologyOne Connect
conversations by defining additional settings to automatically:
• Delete files from complete or incomplete conversations after a specified number of days
• Complete conversations after a specified number of days
• Delete completed conversations after a specified number of days.
Once configured, cleanup processing will use the settings to determine which conversations to complete and
delete, and which files to delete.
Alternatively, the cleanup can be disabled so that conversations and their files are never deleted.
Steps
To define retention policy settings for T1 Connect conversations:
1. Open the Information Security function.
2. Select the Data Retention Policies tile.
3. Select View against the TechOne Connect retention policy.
4. For each setting you want to define in the Additional Settings section:
Page 15 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > T1 Connect Configuration > Setting Up T1 Connect
An event is also logged, and its details and timestamp can be used to troubleshoot the issue that caused the
authentication attempt to fail:
Page 16 of 42
2025A Release Guide | CiA Platform
After resolving the issue, a system administrator can clear the Configuration Locked checkbox in the
Authentication Type function. This will also be logged as an event so that there is a record of the user who
unlocked the authentication type and when this occurred. The data transfer can then be attempted again.
Steps
To view logs and unlock a ProDA authentication type:
1. Open the Site Settings function.
2. Select the Authentication tile.
3. Select View on the Authentication Types card.
4. Select View for a ProDA authentication type.
5. Select the Logs tile.
6. Select View for the latest event with the Configuration Locked action.
7. Review the log details and timestamp, and use this information to resolve the issue that caused the
authentication attempt to fail.
8. When the issue is resolved, select the Key Management tile.
9. Select Edit.
10. In the ProDA Settings section, clear the Configuration Locked checkbox.
11. Click Save. The data transfer can now be attempted again.
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > User Authentication > Storing Other Types of Authentication in CiA
Page 17 of 42
2025A Release Guide | CiA Platform
SAML certificates can be used as part of user authentication for signing in and for SAML encryption.
In the Authentication section of the Site Settings function, the SAML Certificates option lets a customer self-
manage the certificate lifecycle by setting parameters for the automatic generation of new certificates, and
providing the ability to activate, download and delete certificates.
Certificate Configuration
In the Certificate Configuration section, set the parameters used for automatic certificate generation:
• the Certificate Lifetime (1, 2, 3, 5 or 10 years) is the default period for which new certificates are valid,
and lets certificates adhere to a customer's security policy. TechnologyOne recommends using a shorter
period for improved system security.
• the Notification Email is the email address/es that will receive notifications about expiring and newly
generated certificates. TechnologyOne recommends using a group email address. Where this is not
possible, the notifications should go to multiple addresses to ensure they are seen and any required
action is taken.
A job automatically runs each week and sends a notification to each nominated email address. This job uses the
configured parameters to:
• Identify any certificates due to expire in one month or less.
• Generate any new certificates required based on the validity period of existing certificates. Certificates
are generated either one month before the expiry of an existing one-year certificate, or two months
before the expiry of any other existing certificate.
Add Certificate
The SAML Certificates screen also provides a button that you can select to manually generate a SAML
certificate if a certificate needs to be generated before the weekly certificate generation job runs (for example,
Page 18 of 42
2025A Release Guide | CiA Platform
if all available certificates are deleted in error, or if system security may have been compromised). When
manually adding a certificate, a different Certificate Lifetime can be specified, and the new certificate can be
activated immediately if you are using the Update from IdP Metadata URL option against the SAML
authentication type to configure the IdP.
Certificate Versions
SAML certificates are listed in the Certificate Versions section of the SAML Certificates screen:
• In the Active Certificates tab, the 2024 version will initially be the active Signing certificate (provided the
SAML certificate was previously updated from the 2015 version) and no Encryption certificate will be
defined.
• In the All Certificates tab, the 2024 version will be listed and the only action that can be performed is
downloading this certificate. As new certificates are generated, they will also be listed in this tab and the
system administrator can:
o Download an individual certificate so that the file that is produced can be uploaded to the
identity provider (IdP). Alternatively, and if your IdP supports it, you can use the SP Metadata
option against the SAML authentication type to produce a single file with the details of all the
SAML certificates.
o Delete an inactive certificate that is not required.
Manage the Signing and Encryption certificates in the Active Certificates tab. Your IdP will determine whether
both certificates are required, and whether different certificates can be specified or if the same certificate must
be used for both signing in and encryption. When you nominate a certificate, it is automatically activated (if it is
not already active). If it is replacing an existing certificate that is not used anywhere else, the replaced
certificate will automatically be made inactive.
The current status and usage displays for each certificate listed under the All Certificates tab. You may need to
reload the page between updating the active certificates and viewing all certificates to see the latest details.
Steps
Page 19 of 42
2025A Release Guide | CiA Platform
Page 20 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > User Authentication > SAML Certificate Management
A SAML authentication type's metadata file can be tailored to meet the organisation's security needs using the
Only Include Active Certificates checkbox in the SP Metadata section of the Authentication Type maintenance
function. Either:
Page 21 of 42
2025A Release Guide | CiA Platform
• Select the checkbox to include only the active signature and encryption certificates when the metadata
file is downloaded. Restricting the file so that only the current and valid certificates are shared with the
identity provider (IdP) minimises risks if expired or revoked certificates are compromised; or
• Clear the checkbox (default) and the downloaded metadata file will include all signature and encryption
certificates, with the active certificates listed first, followed by the inactive certificates. This can make
transitioning to a new certificate smoother as both the old and new certificates are available to the IdP
during the transition. It can also let the inactive certificates act as an authentication backup if there are
discrepancies in certificate expiration dates or synchronization between CiA and the IdP, reducing
downtime or login issues.
Steps
To include only active certificates in an SP metadata file:
1. Open the Site Settings function.
2. Select the Authentication tile.
3. Select View on the Authentication Types card.
4. Select View against the SAML authentication type that you want to update.
5. Select Edit.
6. In the SAML 2.0 SP Metadata Configuration section, select the checkbox to include only active
certificates.
7. Select Save.
8. In the SP Metadata dropdown menu, select SP Metadata. This downloads the metadata file with only
the active signature and encryption certificates included.
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > User Authentication > SAML Authentication Configuration
Page 22 of 42
2025A Release Guide | CiA Platform
When the Hide Log On Button checkbox is selected under the Portal Access tile in the Portal maintenance
function, guest users will not see the option to logon to the portal.
This setting is typically required when a guest user portal does not allow self-registration. It ensures that users
are not presented with a logon option when they are unable to self-register for an account.
Steps
To hide a portal's logon button:
1. Open the Site Settings function.
2. Select the Authentication tile.
3. Select View on the Portals card.
4. Select View against the portal you want to update.
5. Select the Portal Access tile.
6. Select Edit.
7. In the Guest section, select the Hide Log On Button checkbox.
8. Select Save.
Page 23 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > User Portals > Define Portal Access and User Authentication
Requests and responses can be logged for an OAuth authentication type to assist with troubleshooting issues.
When this logging is enabled, some fields that commonly contain sensitive information are hard coded to
always be redacted in the logs, for example, the client secret and access token.
If required, it is now also possible to configure additional fields to redact. This provides greater control and
flexibility over the data captured in diagnostic logs, including:
• Enabling the redaction of all sensitive information in OAuth diagnostic logs, regardless of the identity
provider.
• Allowing a customer to align OAuth log handling with internal security and privacy policies, while
retaining effective troubleshooting capabilities.
• Improving the clarity and usefulness of logs for monitoring and analysis by having only useful
information visible.
Page 24 of 42
2025A Release Guide | CiA Platform
The additional fields to redact would typically be in query parameters and the request/response payloads in
the logs, and are identified by the system administrator as potentially containing sensitive information but not
required for diagnostic purposes.
The values of all redacted fields will be replaced with asterisks in the log files, for example:
Steps
To redact additional fields in OAuth logs:
1. Open the Site Settings function.
2. Select the Authentication tile.
3. Select View on the Authentication Types card.
4. Select View against the OAuth authentication type that you want to update.
5. Select the Logging tile.
6. Select Edit.
7. In the Extra Fields to Sanitise for Logging field, enter each additional field to be redacted in the logs for
this authentication type. Each field name must be entered in a separate line.
8. Click Save. The values of the specified fields will be replaced with asterisks in the log files.
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > User Authentication > OAuth Authentication Configuration
Page 25 of 42
2025A Release Guide | CiA Platform
4.3 Updates
The following updates were developed in 2025A.
Function Code Function Name Title
$TB.SITESETT.MY.MNT Site Settings SAML Support for RealMe
Updated Cookie Warning When Not Using a Custom
Message
Support for AFD Address Verification
Feature Flag Removed for Centralised User Account
Management
$TB.SF.MYENQ Server Folders Improved Server Folder Syncing
$TB.CONNECT.MNT TechnologyOne Test Mode Removed from TechnologyOne Connect
Connect Function
$TB.ATT.ENT.ENQ Attachment Entities Automatic EXIF Data Stripping for Uploaded Images
Page 26 of 42
2025A Release Guide | CiA Platform
The New Zealand government identity provider (IdP) called RealMe is now supported for the SAML
authentication method. RealMe is the verified identity service that New Zealand’s government agencies are
required to use rather than developing new authentication systems.
This support means that an agency can configure a SAML authentication type that lets users can log on to a CiA
portal using their RealMe credentials instead of CiA-specific credentials. A user’s personal information is then
verified and protected through a government-backed IdP, offering a high level of trust and security.
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > User Authentication > SAML Authentication Configuration
When the Show Cookie Warning Message checkbox is selected for a portal, either a custom message can be
entered, or the field can be left blank to use the default message instead.
So that fewer customers need to enter custom cookie warning messages for their portals, the default message
now refers to the portal as a website instead of CiA. This also ensures that Portal users are not confused by a
reference to CiA when an organisation uses its own branding for a portal.
Page 27 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > User Portals > Set Up a User Portal
Note: Only the fields for the GB country code have been mapped in this template.
An address system can then be configured using the AFD provider template. This defaults AFD as the provider
for UK addresses.
Page 28 of 42
2025A Release Guide | CiA Platform
When the address system is set as the default, any existing functionality for which address verification is
enabled will use it to validate UK addresses.
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > Other Site-Wide Settings > Using Address and Routing Providers
To provide a smoother migration experience when implementing and integrating Centralised User Account
Management (CUAM), the feature flag has been marked as generally available. An access code is no longer
needed to enable this feature.
Migrating to CUAM is supported by functionality in the Access Management > Advanced > User Features >
Centralised User Account Management screen:
Page 29 of 42
2025A Release Guide | CiA Platform
• the Information tab is designed to guide users through the migration process. It provides an overview of
the feature, its prerequisites, and information on what it unlocks. It also refers the user to the detailed
CUAM Migration Guide available in TechnologyOne University.
• the Preview and Finalise tab lists the user accounts that will be created when Centralised User Account
Management is implemented. These must be reviewed and any issues resolved before finalising
processing to create the accounts.
Note: A Centralised User Account Management (CUAM) Migration Guide is available in TechnologyOne
University, offering system administrators key insights on benefits, considerations, dependencies, risks, and
detailed steps for migrating to the CUAM model.
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > User Account Management Configuration
Page 30 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > Server Folder Management > Server Folder Syncing
The setting to enable test mode is now available only in the Site Settings function. This makes it clearer to
system administrators that test mode is a site-wide setting that applies to all system-generated emails, not just
TechnologyOne Connect emails.
Page 31 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > T1 Connect Configuration > Setting Up T1 Connect
Exchangeable Image File Format (EXIF) data is a standard used to store information about digital images, such
as the device and settings used to take the photo, and the location and time of the photo. When an image file
attached to a CiA record is downloaded, this metadata can be viewed in the properties of the file.
When required for security or privacy purposes, CiA can automatically strip EXIF data from digital images that
are uploaded as attachments. To configure this:
• In the Attachment Entity function, open the Settings section for the required attachment entity or type,
and select the Remove Metadata from Images checkbox; and
• Set the permission to enforce attachment restrictions for that entity or type to True.
Users will see the list of all applied restrictions when selecting a file to attach, including the restriction on image
metadata.
Page 32 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > System
Administration > CiA Administration Basics > Manage Attachment Entities and their
Settings
Page 33 of 42
2025A Release Guide | CiA Platform
5. Migration Central
Migration Central is a tool for approved early adopters that guides customers through the step-by-step process
to migrate from Ci to CiA, learning from linked TechnologyOne University topics and completing tasks as they
go.
5.1 New
No new features were developed in 2025A.
Authorisation codes are deprecated in CiA, and functions instead check a user's effective permissions. The
Authorisation Code Migration Worksheet is available to migrate Ci authorisation code settings to the
equivalent CiA permission settings for profiles or users.
When the Ci Access Migration feature flag is enabled, the Advanced section of the Access Management
function provides access to Ci Migration tools. From here, a new Authorisation Code Migration Worksheet can
be created for either:
• Profiles. Only authorisation codes associated with profiles or base profiles that are associated with one
or more active users will be selected for the worksheet; or
Page 34 of 42
2025A Release Guide | CiA Platform
• Users, provided the site default is enabled to Allow User and Role Permissions and Resolve using
Corresponding Ci Authorisations. Only authorisation codes that are associated with active users will be
selected.
You can then choose which of the selected authorisation codes you want to migrate and finish the setup to
initiate worksheet processing.
This processing uses the files stored in the Authorisation Codes sub-folder of the Access Migration Mapping
server folder ($TBMG) to attempt to map each authorisation code setting to its corresponding CiA permission
setting. Mapping files are defined for each functional area that are contained in authorisation codes.
When processing is complete, review the selected authorisation codes and mapped permissions. Each
authorisation code setting will be marked as either:
• "Excluded" when a mapped CiA permission setting matches the current effective permission setting so it
will not be created when the worksheet is finalised; or
• "Mapped" when a mapped CiA permission setting does not match the current effective permission
setting so it will be created; or
• "Not Mapped" when an authorisation code setting cannot be mapped and provide an explanation such
as:
o the setting has been deprecated, or is not found in the mapping file, or is coming in a future
release, or
o there is a mapping error.
Finalising the worksheet will create only the mapped CiA permission setting overrides for the associated
profiles or users.
Steps
To migrate Ci authorisation code settings to CiA permission settings
1. Open the Access Management - Core Enterprise Suite function.
2. Select the Advanced tile.
3. Select View in the Ci Migration card.
4. Select View in the Authorisation Code Migration card.
5. Select Add.
6. Select Authorisation Codes.
7. Update the worksheet description, if required.
8. Select the Migration Type to migrate authorisation code settings for either:
o Profiles or base profiles associated with one or more active users; or
o Active users.
9. Select Next.
10. Select the checkbox for one, multiple or all Ci authorisation codes that are to be processed in the
worksheet. Note that you can click on an authorisation code's card to see a summary of the Ci to CiA
migration that will take place.
11. Select Next.
12. Review the worksheet details and authorisation codes.
13. Select Finish Setup.
14. Select Review the Authorisation Codes and Mapped Permissions step in the worksheet's Process pane.
15. Select each record and review the authorisation code mapping. If you want to remove any, you will need
Page 35 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > Migration Central >
Platform Migration > Ci Access Migration
GO TO: More > Help and Assistance > TechnologyOne University > Migration Central >
Platform Migration > Ci Authorisation Code Migration Worksheet
5.3 Updates
The following updates were developed in 2025A.
Function Code Function Name Title
$TB.ACCMNGT.ENQ Access Management Menu Lists Refresh When Access Migration Worksheet is
Re-Run
$C2SEC.CAM.MNT Centralised Access
Management Mapping for Ci Function Parameters, Imports and Data
Analysers
Page 36 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > Migration Central >
Platform Migration > Ci Access Migration Worksheet
GO TO: More > Help and Assistance > TechnologyOne University > Migration Central >
Platform Migration > Ci Access Migration FAQs
Page 37 of 42
2025A Release Guide | CiA Platform
Ci Function Parameters
Ci function parameters are deprecated in CiA, and functions instead check a user's effective permissions.
Provided the site default is enabled to Allow User and Role Permissions and Resolve using Corresponding Ci
Authorisations, when function parameters for Windows Ci functions are included in the Access Migration
Worksheet, the process will map each role's supported Ci function parameters to the equivalent CiA permission
settings.
This processing uses the files stored in the Function Parameters sub-folder of the Access Migration Mapping
server folder ($TBMG) to attempt to map each function parameter setting to its corresponding CiA permission
setting. Mapping files are defined for the Ci Windows used by each Ci function that had function parameters.
When processing resolves the CiA permission settings, review each one under the role's Permissions tab in the
Access Migration Worksheet’s review step. Finalising the worksheet will create the resolved permission
settings against the role.
Ci Import Functions
Ci import functions are deprecated in CiA. Import types are instead assigned directly to roles, and users
associated with the role can initiate those types of imports.
When Import Windows Ci functions are included in the Access Migration Worksheet, the process will map the
entities defined for each role's import functions to the corresponding CiA import types, or mark the import
entity as "Deprecated".
This processing uses the files stored in the Import Mapping sub-folder of the Access Migration Mapping server
folder ($TBMG) to attempt to map each import entity to its corresponding CiA import type. Mapping files are
defined for the Ci Windows used by each Ci import function.
When processing resolves the CiA import types, review each one under the role's Imports tab in the Access
Migration Worksheet’s review step. Finalising the worksheet will associate the mapped import types with the
role.
Page 38 of 42
2025A Release Guide | CiA Platform
GO TO: More > Help and Assistance > TechnologyOne University > Migration Central >
Platform Migration > Ci Access Migration Worksheet
Page 39 of 42
2025A Release Guide | CiA Platform
6. Connect
The Connect functional group’s aim is to be the single pane of glass for all data flowing into and out of the
TechnologyOne Enterprise system. It is the one central place to go for monitoring all data flows in and out. It
also provides a simple, flexible, maintainable toolkit for interfacing with external systems, allowing customers
to embed TechnologyOne solutions more easily into their overall ecosystem.
6.1 New
No new features were developed in 2025A.
6.3 Updates
No updates were developed in 2025A.
Page 40 of 42
2025A Release Guide | CiA Platform
Page 41 of 42
2025A Release Guide | CiA Platform
Our global SaaS solution provides deep functionality for the markets we serve: local government, government, education, health and community services, asset
intensive industries and financial services. For these markets we invest significant funds each year in R&D. We also take complete responsibility to market, sell,
implement, support and run our solutions for our customers, which reduce time, cost and risk.
For over 30 years, we have been providing our customers with enterprise software that evolves and adapts to new and emerging technologies, allowing our
customers to focus on their business and not technology.