Date Format and Timezone Settings

Nected provides workspace-level settings to configure the default Date Format and Time Zone. These configurations apply to all new Rules and Workflows created in the workspace and are essential for ensuring consistency in how date and time values are displayed, interpreted, and used across your automation logic.

You and your team can access Nected across different regions, time zones, and systems. Without a standardized date format or timezone setting, workflows can easily misinterpret scheduling logic or timestamp comparisons, leading to data errors or failed triggers.

With this feature:

• Teams can work from any timezone and still schedule rules and workflows that execute reliably and consistently.

• Any REST API call that uses a date or datetime value will now be formatted based on the workspace’s selected format and timezone—ensuring compatibility across third-party systems.

• Logs, tokens, and time-based conditions within Nected will follow a uniform structure, helping developers and non-technical users interpret data without confusion.

This is particularly critical when:

• Rules are scheduled based on local business hours or regional compliance

• REST APIs expect ISO-standardized or region-specific timestamps

• Time-based conditions (e.g., "trigger at 9 AM") need to execute accurately regardless of the origin of the request

By setting a default workspace date format and timezone, you ensure automation logic behaves predictably across all time-sensitive use cases.

Date Format Configuration

The Date Format setting determines how date and datetime values are displayed in the platform UI and parsed in user input across the workspace. You can select from predefined regional formats grouped under "International", "India", or use "ISO" standards which are always available and preselected by default.

How to Configure:

1. Go to your Workspace Settings.

2. In the "Dateformat" dropdown, select one of the supported format groups.

Supported Format Groups and Formats:

International Formats	India Formats
mm/dd/yyyy hh:mm:ss	dd/mm/yyyy hh:mm:ss
mm-dd-yyyy hh:mm:ss	dd-mm-yyyy hh:mm:ss
mm/dd/yyyy	dd/mm/yyyy
mm-dd-yyyy	dd-mm-yyyy

And the one which is always been selected/ the default format:

ISO Formats

• yyyy-mm-dd'T'hh:mm:ssZ

• yyyy-mm-dd'T'hh:mm:ss.000Z

• yyyy-mm-dd'T'hh:mm:ss.000000Z

• yyyy-mm-dd hh:mm:ss

• yyyy/mm/dd hh:mm:ss

• yyyy-mm-dd

• yyyy/mm/dd

The ISO format group is ideal for technical accuracy and integration reliability. These formats align with industry standards (such as RFC3339 and ISO 8601) and are particularly suitable when working with databases, APIs, and server-side systems where consistent datetime representation is critical.

Once set, the selected date format is used by:

• All newly created Rules and Workflows

• UI components for date input or display

• Logs and execution traces within the platform

This setting does not impact Rules or Workflows that were created before the change.

NOTE: For all the new rules and workflow the date and timezone will automatically update. For older rules and workflow, their own timezone and date will be same unless the users will update them by themselves.

Time Zone Configuration

The Time Zone setting defines the default timezone context for all datetime operations performed in the workspace. This includes scheduled executions, timestamp comparisons, token evaluations involving datetime fields, and log outputs.

How to Configure:

1. In the same Workspace Settings panel, locate the "Time Zone" dropdown.

2. Select a time zone from the list. This list includes all IANA-compliant timezone identifiers (e.g., Asia/Kolkata, Africa/Algiers, UTC, America/New_York).

The selected timezone will be used internally to:

• Calculate and display datetime values

• Align triggers or conditions that rely on local time (e.g., run every day at 10 AM)

• Parse or evaluate user-provided time inputs relative to the workspace

Important Consideration: Scope of Impact

Updating the date format and timezone in the workspace settings does not retroactively update existing Rules and Workflows. All logic that was created prior to this configuration will continue to operate using its previously saved format and timezone.

To apply the new settings to existing logic:

1. Open the Rule or Workflow editor.

2. Go to the Settings tab of that individual flow.

3. Manually update the date format and timezone values.

This explicit opt-in behavior ensures backward compatibility and protects previously deployed automations from unintended behavioral changes.

Best Practices

• Use ISO format + UTC timezone when:

  • Interacting with external APIs or databases that expect standardized formats

  • Your system operates across multiple regions or data centers

• Use regional formats and local timezones (like dd/mm/yyyy and Asia/Kolkata) when:

  • The team is based in a specific geography

  • Displaying data for local users in a user-facing UI

• When using tokens or dynamic fields, ensure the output format matches the expected input type of downstream systems or conditions.

Example Use Case

If your workspace is configured with:

• Date Format: dd-mm-yyyy hh:mm:ss

• Time Zone: Asia/Kolkata

Then, any new date or datetime input fields in rules, condition blocks, or token outputs will automatically follow this format and timezone. However, workflows or rules created before this setting will still use whatever configuration they were built with, unless explicitly updated.

Workspace-level Date Format and Timezone Settings provide a centralized mechanism to standardize how datetime values are handled across new logic in Nected. While these settings do not affect existing automation directly, they help reduce formatting inconsistencies, especially in multi-user or multi-regional environments.