Skip to content
Book a demo

Cross-source questions

ServiceNow and Workday in one question

Ask questions that join ServiceNow incidents and SLAs with Workday organizations and headcount, with the query and lineage for each system in the answer.

Book a demoHow cross-source answers work

Short answer

One question can span ServiceNow and Workday, such as how SLA breaches by assignment group compare with each team’s headcount. Nexatron queries each within the asking person’s access, combines the results in an isolated step inside your workspace, and shows each source’s query. ServiceNow and Workday are both available.

Example joined questions

Questions to ask. Each needs data from both systems; the answer depends on your own data and definitions.

  • Which assignment groups breached the most resolution SLAs last month, and how did each group’s Workday headcount change over the same period?
  • How many P1 incidents per worker did each supervisory organization’s teams resolve this quarter?
  • Which teams with open job requisitions in Workday also have the most incidents past their SLA?

Agree how ServiceNow assignment groups map to Workday supervisory organizations, usually through the employee ID on each ServiceNow user record.

Check before you trust a joined answer

  • Group membership changes over time. Name the date the mapping applies to.
  • ServiceNow access control lists and Workday security groups both apply, so a manager sees only their own organizations.
  • Say whether the count is SLA records or incidents: one incident can carry several SLAs.

How a cross-source answer works

  1. Each system is queried within the person’s access

    Nexatron sends each part of the question to the system that holds it. A system each person signs in to answers as the person asking, and a shared connection reads the same data for everyone enabled on it.

  2. Results are joined inside your workspace

    Nexatron combines each system’s results in an isolated step inside your tenant when the question is asked. Nothing has to be consolidated into a warehouse first, and there is no pipeline to build.

  3. The queries come back with the answer

    The answer carries the generated query for each system and how many records matched, so a reviewer can check which system supplied which figure and repeat the check later.

  4. Joins follow links found at setup

    Nexatron joins on the links setup found between the systems, and says how many records matched. If no record matches, it says so and marks the figures as uncertain.

  5. Currencies are never added up as they are

    Amounts in different currencies are converted with one system’s own exchange rates where a usable rate source exists, and otherwise shown side by side with the reason.

  6. Longer than a single-source answer

    These answers take longer than single-source ones.

More on how it works and its limits: Cross-source analytics and the guide to cross-source analytics without a warehouse migration.