Case → service task
Use available case information to start supporting service work.
All integrations
Case data
Rx.Mission
Rx.Mission documents integrations through case-management APIs. Explore connecting case events, documents or status to service, signing and follow-up. API versions, permissions and acceptance tests determine feasibility; the Service Automation Suite configuration must be validated.
From product to process
How to use the integration
Request → signature
Start the agreed signing process and follow up its available outcome.
Exceptions → tasks
Route missing information or discrepancies to the team responsible for follow-up.
Combine into one controlled process
Data → rules → execution-
Combine
Case + document + handling rules
-
Determine & check
Check completeness and determine follow-up
-
Execute & report back
Start supporting task · Request document signing · Update case file
Check sources and rules, test changes and track the outcome. Manual tasks get an owner and confirmation.
Build visually. Manage easily.
Reuse building blocks, adapt your process and test the change. Manage it yourself, together with us or let Scope4mation take care of it.
More process examples & technical details
The work between your applications
Case created.
Everything else handled too?
Service Automation Suite connects Rx.Mission with your other applications, people and rules. Keep data aligned, work moving and outstanding actions visible.
A change, request or alert
Service Automation Suite
Data, people, assets and relationships on one foundation.
- Compare
- What exists? What should exist?
- Determine what is needed
- Matrix · policy · legal requirements
- Coordinate the next steps
- Checks · tasks · approvals · actions
Execution ↔ feedback
Your people and tools
Rx.Mission
For example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
Handover to service
A permitting case with controlled follow-up.
Rx.Mission documents integrations through case-management APIs. Explore connecting case events, documents or status to service, signing and follow-up. API versions, permissions and acceptance tests determine feasibility; the Service Automation Suite configuration must be validated.
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.
Rx.MissionRelevant data or workflow status
Update, execute and record outcomes
Choose the handover moment
Choose the status or event that triggers the handover and the context required.
Prepare focused work
Connect relevant data to a request or task for the responsible team.
Return progress
Show the original team what has been handled and which information is still missing.
Documents & follow-up
Keep the document with the work record.
Connect document data and process status to the related request. Signing or archiving is a step, not the end of the workflow.
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.
Rx.MissionRelevant data or workflow status
Update, execute and record outcomes
Identify the record
Connect the document or reference to the right request and people.
Execute the agreed step
Use the available document or signing function and pass only the necessary data.
Start follow-up work
Return the relevant status and connect the next activity to the same request.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect Rx.Mission to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Example configuration · shaped by your process
Synchronise data and return the outcome
Connect and test
API ComposerChoose 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.
Combine and compare
Data Flow ComposerSelect fields, translate codes and relate records using shared data. Compare source and target to identify new, changed or incomplete records.
Execute and use the response
API ComposerBuild 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.
Recognise errors and follow up deliberately
API ComposerConfigure 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.
Which data do you maintain?
An example configuration, not fixed field names or a mandatory combination.
- Source ID and external reference
- Retain verified relationships between records and reuse them across integrations.
- Fields, codes and required data
- Select the required data, translate values and enrich from shared tables. Route uncertain matches for review.
- Result reference and processing status
- Use the available response for feedback and agreed follow-up actions.
Sent ≠ processed. Use the response and agreed validation to determine the next step.
Need to publish data yourself?
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 ComposerFrom data to a complete process?
Combine 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 blocksBeyond the first integration.
Use the same data and rules in your next process.
Start 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.
Signature declined. Keep the process moving.
A request awaits a ValidSign signature. Declining, expiry and technical failure each need different handling.
- Combine
- Link the request, signing request and document. Read the available status and apply agreed conditions to determine the next action.
- The outcome determines what follows
- Signed: process the document and confirm the activity. Declined: route the reason to the owner. Temporary technical failure: retry only under the configured error rule.
- The benefit
- Appropriate follow-up for each outcome without counting a sent signing request as completed work.
A different name does not mean a new record.
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.
- Combine
- Retain verified identifiers and source rules in a shared table. Reuse the relationship for requests, tickets and other integrations.
- The outcome determines what follows
- Known key: use the relationship. Multiple candidates or a missing identifier: request review. Once confirmed, reuse the established relationship.
- The benefit
- A consistent data foundation managed by your team instead of investigated again for every connection.
Refreshing a report does not guarantee reliable data.
A source request can succeed while data is missing, differently coded or not yet fully retrieved.
- Combine
- Combine pagination and output mapping with agreed data checks. Use shared relationship tables to connect sources.
- The outcome determines what follows
- Checks passed: prepare the dataset. Deviation: request review and expose freshness. Temporary API failures follow a bounded recovery path.
- The benefit
- A clearer distinction between a technically successful import and information fit for decision-making.
Your process needs more than a standard action?
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
Rx.Mission in your workflow
Pull up a chair. Or join us online.
Over coffee, tea or online: tell us what you are working on.
We can help with the integrations, automation and coordination your process needs, even if your application is not listed yet.
