Resource dependencies & substitutes

What you configure

profiles.dependencies

List required companion resources and consumed units.

profiles.substituteIds

Define the replacements your application permits.

evaluateBooking / findSubstitutes

Evaluate the proposed interval, units, and requirements.

Integration code example

1. Keep dependent-resource IDs consistent with the resource directory.
2. Provide the booking interval and requirements to the licensed planner.
3. Explain decision issues and let your application choose whether to apply a suggested substitute.

Copy this TypeScript into your application, not the browser console. Replace YOUR_WTS_LICENSE_KEY with an entitlement issued for your deployment origin. A WTS license is not a Google, Microsoft or CalDAV credential. These examples are documentation only and never execute on this page.

npm install @wts-calendar/core

import { verifyCalendarLicense } from '@wts-calendar/core';
import { AdvancedResourcePlanner } from '@wts-calendar/core/advanced-resource-planning';

const license = await verifyCalendarLicense('YOUR_WTS_LICENSE_KEY');
const planner = new AdvancedResourcePlanner({
  license,
  timeZone: 'UTC',
  resources: [
    { id: 'design', title: 'Design studio', capacity: 2 },
    { id: 'engineering', title: 'Engineering', capacity: 4 },
  ],
  events: [
    {
      id: 'review',
      title: 'Design review',
      resourceId: 'design',
      start: '2026-09-07T09:00:00Z',
      end: '2026-09-07T10:30:00Z',
    },
  ],
  profiles: [
    {
      resourceId: 'design',
      dependencies: [{ resourceId: 'engineering', units: 1 }],
      substituteIds: ['engineering'],
    },
  ],
});

const request = {
  resourceId: 'design',
  start: '2026-09-07T09:30:00Z',
  end: '2026-09-07T10:00:00Z',
  units: 2,
};
export const decision = planner.evaluateBooking(request);
export const alternatives = planner.findSubstitutes(request);
console.log(decision.allowed, decision.issues, alternatives);

Application responsibilities

The engine returns data, not a built-in chart. Render results in your application and call planner.setData() after resources, events or profiles change.

Evaluations do not reserve capacity or automatically reassign events. Recheck and commit through your application after the user chooses an alternative.

Behavior and lifecycle

• Availability, shifts, requirements, dependencies, and capacity are evaluated together.
• Allowed substitutes are ranked by projected utilization and then stable resource ID.