Can AI agents automate Public 360?
Tieto · hybrid · public-sectorrecords-management
Public 360 has substantial first-party integration capability, but its public technical specification is much thinner than its product catalogue. Tieto states that Public 360 integrates line-of-business systems, shared public services and custom solutions through standard APIs. The supported portfolio includes a Process Engine and reusable process libraries, a third-party integration tool and a Power Automate connector. Named modules integrate Microsoft Teams, SharePoint and Office applications, SvarInn, SvarUt, eFormidling, digital post, e-signing, the Norwegian population and business registers, cadastral data, e-services and public disclosure. These are strong routes for event-driven archiving, document flows and case processes. Public material does not expose a current endpoint catalogue, request schema, authentication model, SDK or tenant-level entitlement map, so the generic API score remains conservative and each procurement must obtain the installed-version integration contract. Automation also operates inside Nordic records-management, Noark, GDPR, access-control, retention and disclosure obligations; a technically permitted write may still be an invalid records action. No product-specific first-party MCP, general CLI, repeatable visual RPA result or computer-use result was established.
Best path today: integrations · Overall automatability: 8/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | standard-apithird-party-integration-tool coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | unknown | verdict: unknown |
| Integrations | yes | power_automate |
| CLI | unknown | |
| Extensibility | yes | process-engineprocess-librarythird-party-integration-toolpower-automate-connector webhooks: unknown |
| Data access | export: cases, records, documents, metadata, search-results, public-disclosure · import: cases, records, documents, metadata, emails, registry-data | |
| RPA / UI automation | unknown | web-domoffice-add-ins No repeatable UI probe was run. Vendor-supported APIs, the process engine, the third-party integration tool and the Power Automate connector are preferable to visual control for governed case and archive actions. The exact tenant, enabled modules, access matrix, disclosure rules, records policy and custom processes must be tested before any write automation.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 6 | — | 8 | — | — | — | 8 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-08-17 |
platforms | declared | source | 2026-08-17 |
license | declared | source | 2026-08-17 |
modalities.api.exists | declared | source | 2026-08-17 |
modalities.api.kinds[0] | declared | source | 2026-08-17 |
modalities.api.kinds[1] | declared | source | 2026-08-17 |
modalities.api.coverage | declared | source | 2026-08-17 |
modalities.integrations.power_automate | declared | source | 2026-08-17 |
modalities.extensibility.scripting | declared | source | 2026-08-17 |
modalities.data_access.export | declared | source | 2026-08-17 |
modalities.data_access.import | declared | source | 2026-08-17 |
verdict.scores.api | declared | source | 2026-08-17 |
verdict.scores.integrations | declared | source | 2026-08-17 |
freshness.watch[0].url | declared | source | 2026-08-17 |
freshness.watch[1].url | declared | source | 2026-08-17 |
freshness.watch[2].url | declared | source | 2026-08-17 |
Last verified 2026-08-17 · volatility high · JSON record