Work order → service
Connect available work-order updates with the service desk or technical team.
Devices & inventory
Connect available Ultimo asset and work-order data with the service process. Align status, owner and follow-up with your CMDB or service desk, subject to the Ultimo edition and permitted API functions.
From product to process
Connect available work-order updates with the service desk or technical team.
Share agreed asset identifiers, locations and status fields across maintenance and service.
Route missing information or discrepancies to the team responsible for follow-up.
Asset + work order + service ticket
Link records and determine follow-up
Involve technical team · Align status · Return maintenance outcome
Check sources and rules, test changes and track the outcome. Manual tasks get an owner and confirmation.
Reuse building blocks, adapt your process and test the change. Manage it yourself, together with us or let Scope4mation take care of it.
The work between your applications
Service Automation Suite connects Ultimo with your other applications, people and rules. Keep data aligned, work moving and outstanding actions visible.
Data, people, assets and relationships on one foundation.
Execution ↔ feedback

Microsoft IntuneFor example. Also with other teams, suppliers and applications.
What is complete? Who needs to act? Which exception needs attention?
Maintain records
Connect available Ultimo asset and work-order data with the service process. Align status, owner and follow-up with your CMDB or service desk, subject to the Ultimo edition and permitted API functions.

Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Relevant data or workflow status

Update, execute and record outcomes
Match available devices or resources to existing records using stable identifiers.
Agree the authoritative source for each field. Update only necessary data and avoid duplicate records.
Have missing data or discrepancies reviewed by the team responsible for the asset.
Handover & return
Connect devices and records to the employee and the actual handover. A missing device is not automatically a returned laptop.

Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Relevant data or workflow status


Update, execute and record outcomes
Combine available user and asset data with employee records.
Have the responsible person confirm the handover and update agreed relationships.
Follow up missing returns and outdated relationships on reassignment or departure.
Alerts & follow-up
Turn a relevant status or discrepancy into actionable work. Add context and route follow-up to the right team.

Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Relevant data or workflow status

Update, execute and record outcomes
Use the available status or event and identify repeated alerts.
Connect customer, device or service context where available. Apply your priority and ownership rules.
Create or update a ticket and keep execution and feedback in the same process.
For administrators who want to understand how it works: connect Ultimo to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Choose the API method, URL and authentication. Manage the host and credentials in an environment. Test a request in Discovery and inspect the fields actually returned by the API.
Select fields, translate codes and relate records using shared data. Compare source and target to identify new, changed or incomplete records.
Build the request body from validated data and inspect Body Preview before testing. Use the result ID in Data Context for the next request or save output to an entity. Configure write-back separately.
Configure error rules by HTTP code and/or message. A temporary API failure can use bounded retries. A missing relationship or rejection needs another route: record the cause and configure a verification task for the appropriate team, for example.
An example configuration, not fixed field names or a mandatory combination.
Sent ≠ processed. Use the response and agreed validation to determine the next step.
Use Endpoint Composer to publish a configured Service Automation Suite data object. Choose read and write methods and security profiles so a customer can retrieve agreed service data or a supplier can submit information, for example. Configure data selection and subsequent processing separately.
Endpoint ComposerCombine the integration with a form, a shared matrix, a review or collaboration between service teams. For example, an approved request leads to execution in Microsoft Entra, a ValidSign signature request and feedback in TOPdesk. Your process determines the steps needed; not every use case requires all these components.
Explore the connected building blocksStart with one use case. Connect customer, employee and asset data, for example, and agree which source is authoritative. Reuse those relationships, a matrix where needed and configured actions in the next workflow. Agree who maintains the data and rules. Expand without repeatedly connecting and maintaining the same information.
An employee receives a replacement device. The old asset, new record and open service or security tickets must remain connected.
A person or organisation has a different name in the source than at a customer or supplier. Matching text again can create incorrect or duplicate relationships.
Procurement, a supplier and technical inventory each hold part of the picture. A delivered asset is not automatically assigned to its correct owner.
Configure the missing API request, input and output in API Composer. Use its response in the next step and combine it with data tables, forms and automations. Extend the same product and reuse the configured building blocks.
Use Service Automation Suite to update a ticket in TOPdesk, for example, with fields available through its API, such as category, priority, status and support group. For another application, configure its request and field mapping. The outcome determines the next action: confirm, add information or request review, not merely check whether the request arrived.
Build it yourself: explore the technical approachNeed to publish data or let others submit it? Endpoint Composer exposes a configured Service Automation Suite data object with selected methods and security profiles. Other building blocks handle subsequent processing.
From product to workflow