Skip to content
KiweelyKiweelyKiweely

Inventory Every Workday Integration System, Schedule, and Owner

Workday represents every integration as an integration system, with a schedule, a business process, an integration system user, and notifications. There is no single owner field. This is the inventory to take from those tasks.

  • Checked against Workday on
  • Applies to Workday Extend
  • 5 min read
  • Published
  • By Kiweely
On this page

You cannot retire, move, or even explain an integration you cannot name. Workday already has the list. It does not have a column called Owner. Integration systems are the rows. Security, notifications, and the integration system user are how you fill in the person.

Workday represents every integration, whatever built it, as an integration system. A Studio deploy registers a new integration system for every transport in that integration, so one Studio project can be several rows. Enterprise Interface Builder, connectors, and Studio all show up in the same shape: something you can launch, schedule, and find afterward in Process Monitor.

The columns, and the task that fills each one

Open View Integration System for the row, then the related actions below. Do this in the tenant where the integration actually runs. Workday refreshes Sandbox and Sandbox Preview from Production every week, so the inventory of what runs for real belongs in Production. What to recheck after that refresh is a separate pass.

Column Where Workday keeps it What to write down
ColumnName Where Workday keeps itThe integration system What to write downThe name people search. Studio can produce more than one system per assembly, one per transport.
ColumnHow it starts Where Workday keeps itTriggers on the integration system What to write downManual, a subscription, an API, a schedule, or a business process. An integration business process can also start from View Integration System, from Launch / Schedule Integration, or as a step on another process, such as after Complete Form I-9.
ColumnSchedule Where Workday keeps itLaunch / Schedule Integration What to write downFrequency, time, time zone, priority, catch-up, and the end of the recurrence. Details below.
ColumnWho may launch it Where Workday keeps itSecurity on the integration system What to write downThe security that can launch it, and the rights it has while it runs.
ColumnAccount it runs as Where Workday keeps itThe integration system user on the service steps What to write downService steps run as that user. A security error in the event names the missing domain.
ColumnWho is told Where Workday keeps itIntegration System > Configure Integration Notifications What to write downA user-based security group, the inbox of the worker who launches it, and any email addresses configured on the notification. This is the closest Workday gets to an owner.
ColumnWhat it sends Where Workday keeps itConfigure Integration Attributes, and the delivery or retrieval step What to write downAttributes are tenanted values: a type of data, or a behavior such as whether prior values are included. Some require a value before launch. Delivery is a separate step.
ColumnFile name Where Workday keeps itConfigure Integration Sequence Generators What to write downA sequence of date, time, sequence, and fixed text. If a sequence generator is configured, Workday ignores the static Output Filename attribute.
ColumnLast outcome Where Workday keeps itProcess Monitor, integration event What to write downEach launch has an integration event id. Status messages are written onto that event.

There is no owner field on the pages Workday publishes for these tasks. Put a name in your inventory only after you have read the notification security group and agreed which person carries it. A security group with twelve members is not an owner until someone is.

Schedules worth copying exactly

Launch / Schedule Integration is not a single cron box. Record the option, not the word “daily.”

Run frequency What you must capture
Run frequencyRun Now What you must captureNo recurrence. Someone launched it, or a process did.
Run frequencyRun Once in the Future What you must captureStart date, time, time zone.
Run frequencyMinute What you must captureInterval of 5, 15, 30, or 45 minutes, plus start and end time and the date range. The start has to be in the future when you set it.
Run frequencyHourly What you must captureAn interval from 1 to 12 hours, start and optional end time, time zone, date range.
Run frequencyDaily What you must captureEvery weekday, or every n days. Start time, time zone, start date, end date.
Run frequencyWeekly What you must captureEvery n weeks, which weekdays, time, time zone, dates.
Run frequencyMonthly What you must captureWhich months, and either a day number, last day of the month, or a weekday such as first Monday. Time, time zone, dates.
Run frequencyDependent What you must captureThe other integration or alert, and the status it waits for, such as Completed or Completed with Warnings.
Run frequencyCustom What you must captureThe explicit list of dates and times.

Also copy priority (Critical, High, Normal, or Low) and Catch Up Behavior (None or Run Once). Catch-up is what happens when a maintenance window skips the slot. A partner who expected a file during that window needs this written down. See overnight SFTP failures.

One limit is easy to miss. On the range of recurrence, a scheduled integration runs for at most five scheduled instances after the end of the following calendar year. An end date that looks distant still stops.

Business process, then the person

If the integration system has no business process of its own, it uses the default Integration Process Event: Initiation, then Service - Fire Integration. The file is not delivered unless someone added Service - Document Delivery. Retrieval is Service - Document Retrieval, and it has to come before Fire Integration. When an Integration step on that process fails, the parent process stops. That is documented behavior, so the inventory should say whether this system is chained from another.

Search bp: plus the integration name to find a definition that already exists. After a system-specific process exists, Workday says to create further versions only through Business Process > Create, Copy, or Link Definition.

Notifications on the business process fire from the final status. The connector course also warns that the default email template links to the event and its files, and that Workday does not recommend attaching the integration files to the email. If your inventory’s “owner” currently receives the full file by email, that is a finding, not a convenience.

How to use the list

Sort it three ways. By schedule, so two payroll files are not five minutes apart on the same integration system user. By notification group, so you can see the integrations nobody is told about. By transport, so the SFTP endpoints, the Studio systems, and the ones with no delivery step are obvious.

That list is the input to a later decision: keep the integration in Workday, or rebuild it outside the tenant. Kiweely Roots (coming next) is aimed at the second. It is outside the tenant, it uses standard Workday APIs, and you describe the integration instead of maintaining the Studio archive. Register interest and attach the count of systems that have a schedule and no notification group. Roots is not a report inside View Integration System, and it is not available to run this inventory for you today.

Sources checked

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.