Defining Arguments in Edit Time Trigger

Help Orchestrator
1

I noticed that the “Edit Time Trigger” interface is different from last night, especially the way input arguments is defined (as highlighted below).

trigger edit
trigger edit1705×949 202 KB

However, I find the previous interface is very straightforward and user-friendly.

Could someone please explain how to do it? :folded_hands:

Thank you and look forward to you.

Forum Engagement Daily Reports
2

Hi, @GhostBuster

In the new Edit Time Trigger interface:

Go to Runtime Arguments > Input tab. Toggle JSON schema to see argument structure.

Enter values directly in fields (strings without quotes, arrays as JSON e.g. [“item1”]).

Quick steps:

Click Edit on your time trigger

Switch to Input tab under Runtime Arguments

Toggle JSON schema ON if needed

Fill argument values matching your Main.xaml args and then Save

This replaces the old separate Arguments tab. Values inherit from published package but can be overridden here.

3

In the new Edit Time Trigger interface:

  • Go to Runtime Arguments → Input
  • Turn on JSON schema to view the expected argument structure
  • Enter values directly in the fields:
    • Strings without quotes
    • Lists/arrays in JSON format (for example: ["item1"])

Steps:

  1. Click Edit on the time trigger
  2. Open Runtime Arguments → Input
  3. Enable JSON schema if you need to check the argument format
  4. Enter values that match the arguments defined in Main.xaml
  5. Click Save

This replaces the older Arguments tab. By default, values come from the published package, but you can override them at the trigger level.

image
image633×454 40 KB

Orchestrator - Creating a time trigger

5

HI @GhostBuster

This is the new Orchestrator UI where input arguments are now defined using JSON based on the process schema.

Instead of filling values field by field, you need to provide a JSON object that matches the exact data types of your workflow arguments. For example, strings, integers, arrays, and objects must match how the arguments are defined in Studio. If an argument is an object (like Time_span_limit), you cannot pass it as a string.

  • Check the argument types in Studio
  • Build the JSON accordingly
  • Validate the schema error shown at the bottom to fix mismatches

It’s less user-friendly than the old UI, but once the JSON matches the schema, it works fine.

7

Thank you for your reply.

The variable Time_span_limit was defined in Studio as TimeSpan, may I know how shall i define it in JSON file in this new Orchestrator UI?

Thanks.

8

For a TimeSpan argument like Time_span_limit, in Orchestrator JSON you can pass it as an ISO 8601 duration string, for example:

“Time_span_limit”: “PT0H0M10S”

or as an object with ticks if your workflow expects it:

“Time_span_limit”: { “Ticks”: 100000000 }

Make sure the format matches how your workflow reads the argument.