@elevasis/sdk 1.48.0 → 1.49.0

package/reference/sdk/templates/recurring-job.mdx

@@ -18,8 +18,8 @@ loadWhen: "Applying the recurring-job workflow template"
 
 Two-part pattern for recurring jobs:
 
-1. **Setup workflow** (`recurring-job-setup`): Creates a schedule entry that triggers the main job workflow on a recurring basis. Run once to activate.
-2. **Main job workflow** (`recurring-job`): The actual work executed on each scheduled trigger.
+1. **Setup workflow** (`recurring-job-setup-workflow`): Creates a schedule entry that triggers the main job workflow on a recurring basis. Run once to activate.
+2. **Main job workflow** (`recurring-job-workflow`): The actual work executed on each scheduled trigger.
 
 The job workflow and setup workflow share a schedule key for idempotent schedule management.
 
@@ -43,8 +43,7 @@ z.object({
 
 ```typescript
 z.object({
-  scheduledAt: z.string(),              // ISO timestamp of the scheduled trigger
-  jobInput: z.record(z.string(), z.unknown()).optional(), // Passed through from schedule creation
+  jobInput: z.record(z.string(), z.unknown()).optional(), // Passed through as scheduleConfig.payload at setup time
 })
 ```
 
@@ -72,7 +71,7 @@ import { z } from 'zod'
 // Setup workflow -- run once to create the schedule
 export const recurringJobSetup: WorkflowDefinition = {
   config: {
-    resourceId: 'recurring-job-setup',
+    resourceId: 'recurring-job-setup-workflow',
     name: 'Recurring Job Setup',
     type: 'workflow',
     description: 'Creates or updates the schedule for the recurring job',
@@ -104,10 +103,15 @@ export const recurringJobSetup: WorkflowDefinition = {
           tool: 'scheduler',
           method: 'createSchedule',
           params: {
-            resourceId: 'recurring-job',
-            cronExpression,
-            timezone: timezone ?? 'UTC',
-            input: { scheduledAt: new Date().toISOString(), jobInput: jobInput ?? {} },
+            organizationId: context.organizationId, // ignored -- the platform re-scopes this from execution context
+            name: 'Recurring Job Schedule',
+            target: { resourceType: 'workflow', resourceId: 'recurring-job-workflow' },
+            scheduleConfig: {
+              type: 'recurring',
+              cron: cronExpression,
+              timezone: timezone ?? 'UTC',
+              payload: { jobInput: jobInput ?? {} },
+            },
             idempotencyKey: 'recurring-job-schedule',
           },
         }) as { id: string }
@@ -124,7 +128,7 @@ export const recurringJobSetup: WorkflowDefinition = {
 // Main job workflow -- triggered by the scheduler on each run
 export const recurringJob: WorkflowDefinition = {
   config: {
-    resourceId: 'recurring-job',
+    resourceId: 'recurring-job-workflow',
     name: 'Recurring Job',
     type: 'workflow',
     description: 'Executes on each scheduled trigger',
@@ -133,7 +137,6 @@ export const recurringJob: WorkflowDefinition = {
   },
   contract: {
     inputSchema: z.object({
-      scheduledAt: z.string(),
       jobInput: z.record(z.string(), z.unknown()).optional(),
     }),
     outputSchema: z.object({
@@ -147,12 +150,12 @@ export const recurringJob: WorkflowDefinition = {
       id: 'run',
       name: 'Run Job',
       description: 'Execute the recurring job logic',
-      inputSchema: z.object({ scheduledAt: z.string(), jobInput: z.record(z.string(), z.unknown()).optional() }),
+      inputSchema: z.object({ jobInput: z.record(z.string(), z.unknown()).optional() }),
       outputSchema: z.object({ completed: z.boolean(), processedAt: z.string(), summary: z.string() }),
       handler: async (input, context) => {
-        const { scheduledAt, jobInput } = input as { scheduledAt: string; jobInput?: Record<string, unknown> }
+        const { jobInput } = input as { jobInput?: Record<string, unknown> }
 
-        context.logger.info(`Recurring job started at ${scheduledAt}`)
+        context.logger.info(`Recurring job started at ${new Date().toISOString()}`)
 
         // === REPLACE THIS SECTION WITH THE ACTUAL JOB LOGIC ===
         // Example: fetch data, process it, send a report
@@ -186,9 +189,11 @@ export const recurringJob: WorkflowDefinition = {
 ## Adaptation Notes
 
 - **Job logic:** Replace the placeholder comment in the `run` handler with the actual job logic. Ask the user what the job should do before generating the full workflow.
-- **Both workflows needed:** Remind the user to add both `recurringJob` and `recurringJobSetup` to their `src/index.ts` registry. Run `setup` once to activate; only `recurring-job` runs automatically thereafter.
+- **Both workflows needed:** Remind the user to add both `recurringJob` and `recurringJobSetup` to their `src/index.ts` registry. Run `setup` once to activate; only `recurring-job-workflow` runs automatically thereafter.
 - **Idempotency key:** The `recurring-job-schedule` key ensures re-running setup does not create duplicate schedules.
 - **Timezone:** Always ask the user their preferred timezone. Defaults to UTC which may cause unexpected run times.
+- **`organizationId` in `createSchedule` params:** The platform always re-scopes this from the execution context server-side, so the value passed here is ignored -- it exists only because the field is required by the scheduler's type.
+- **Execution input on each run:** The job workflow receives `scheduleConfig.payload` as its input, with a `_scheduleMetadata` object (`scheduleId`, `scheduleName`, `scheduleStep`) merged in automatically. Extra fields are not part of the validated `inputSchema` and are silently dropped by Zod's default parsing.
 
 ---
 

package/reference/sdk/templates/text-classifier.mdx

@@ -70,7 +70,7 @@ type Input = z.infer<typeof inputSchema>
 
 export const textClassifier: WorkflowDefinition = {
   config: {
-    resourceId: 'text-classifier',
+    resourceId: 'text-classifier-workflow',
     name: 'Text Classifier',
     type: 'workflow',
     description: 'Classifies text into predefined categories using an LLM',

package/reference/sdk/templates/web-scraper.mdx

@@ -72,7 +72,7 @@ type Input = z.infer<typeof inputSchema>
 
 export const webScraper: WorkflowDefinition = {
   config: {
-    resourceId: 'web-scraper',
+    resourceId: 'web-scraper-workflow',
     name: 'Web Scraper',
     type: 'workflow',
     description: 'Scrapes structured data via Apify and stores in Supabase',
@@ -86,16 +86,20 @@ export const webScraper: WorkflowDefinition = {
       name: 'Run Apify Actor',
       description: 'Execute the Apify actor and collect results',
       inputSchema,
-      outputSchema: z.object({ items: z.array(z.unknown()), runId: z.string() }),
+      outputSchema: z.object({ items: z.array(z.unknown()), runId: z.string(), tableName: z.string() }),
       handler: async (input) => {
-        const { actorId, startUrls, maxItems } = input as Input
+        const { actorId, startUrls, tableName, maxItems } = input as Input
         const result = await platform.call({
           tool: 'apify',
           method: 'runActor',
           credential: 'apify',
-          params: { actorId, input: { startUrls: startUrls.map(url => ({ url })), maxItems: maxItems ?? 100 } },
+          params: {
+            actorId,
+            input: { startUrls: startUrls.map(url => ({ url })) },
+            maxItems: maxItems ?? 100,
+          },
         }) as { items: unknown[]; runId: string }
-        return { items: result.items, runId: result.runId }
+        return { items: result.items, runId: result.runId, tableName }
       },
       next: { type: StepType.LINEAR, target: 'store' },
     },

package/reference/ui/exports.mdx

@@ -44,7 +44,7 @@ description: "Auto-generated catalog of all published @elevasis/ui subpath expor
 | `@elevasis/ui/layout` | Layout | Components | Published layout component entry for downstream applications. |
 | `@elevasis/ui/charts` | Charts | Components | Published chart component entry for downstream applications. |
 | `@elevasis/ui/theme` | Theme | Visual | Published theme entry for downstream applications. |
-| `@elevasis/ui/theme/presets` | Theme Presets | Visual | Re-exports the canonical THEME_PRESETS tuple, ThemePresetName union, and ThemePresetEnum Zod enum from @repo/core. Single source of truth for preset names across UI, schemas, and Zustand state. |
+| `@elevasis/ui/theme/presets` | Theme Presets | Visual | Published THEME_PRESETS tuple, ThemePresetName union, and ThemePresetEnum Zod enum, defined locally and kept manually aligned with the canonical list in packages/core/src/auth/multi-tenancy/theme-presets.ts. |
 | `@elevasis/ui/api` | API | Foundation | Published API client entry for downstream applications. |
 | `@elevasis/ui/utils` | Utils | Foundation | Published utility entry for downstream applications. |
 | `@elevasis/ui/graph` | Graph | Visual | Published graph helper and visualization entry. |

package/reference/ui/index.mdx

@@ -77,6 +77,6 @@ You do not need `@elevasis/ui` if you are only writing backend workflows and age
 
 `@elevasis/ui` uses `@elevasis/core` internally for entity schemas, org-model types, and auth contracts. Installing `@elevasis/ui` will pull in `@elevasis/core` as a dependency. You do not need to install `@elevasis/core` separately unless you need direct access to its subpaths.
 
-## Export Catalog
+## Documentation
 
-See [Export Catalog](exports.mdx) for a generated table of all published subpath exports derived from the reference manifest.
+- [Export Catalog](exports.mdx) - Generated table of all published subpath exports derived from the reference manifest