Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review RNs 42064/42097/42110 #4351

Merged
merged 3 commits into from
Mar 5, 2025
Merged

Review RNs 42064/42097/42110 #4351

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cae41fb
Review RNs 42064/42097/42110
slc-peter-vanpoucke Mar 5, 2025
9b934bc
Corrections
spetebroodt Mar 5, 2025
d58e2a5
Merge branch 'main' into pr/4351
spetebroodt Mar 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion release-notes/Cube/Cube_Feature_Release_10.5/Cube_10.5.4.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ For more information about running elements in isolation mode, see [Elements can

<!-- MR 10.4.0 [CU13] / 10.5.0 [CU1] - FR 10.5.4 -->

When UI components of type *Calendar* or *Time* are used in interactive Automation scripts, up to now, the entered date and time would be formatted depending on the platform and the configured settings. From now on, when an interactive Automation script is being run within DataMiner Cube, the UI components of type *Calendar* and *Time* will be able to retrieve the time zone and date/time settings of the Cube session, and use those settings to format the time and date entered by the user.
When UI components of type *Calendar* or *Time* are used in interactive Automation scripts, up to now, the entered date and time would be formatted depending on the platform and the configured settings. From now on, when an interactive Automation script is being run within DataMiner Cube, the UI components of type *Calendar* and *Time* will be able to return the time zone of the client and the time and date as entered by the user.

For more information, see [Interactive Automation scripts: UI components 'Calendar' and 'Time' can now retrieve the time zone and date/time settings of the client [ID 42064]](xref:General_Feature_Release_10.5.4#interactive-automation-scripts-ui-components-calendar-and-time-can-now-retrieve-the-time-zone-and-datetime-settings-of-the-client-id-42064)

Expand Down
12 changes: 6 additions & 6 deletions ...se-notes/General/General_Feature_Release_10.5/General_Feature_Release_10.5.4.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,11 +93,11 @@ The information provided is similar to the information found in the *SLElementIn

<!-- MR 10.5.0 [CU1] - FR 10.5.4 -->

When UI components of type *Calendar* or *Time* are used in interactive Automation scripts, up to now, the entered date and time would be formatted depending on the platform and the configured settings. From now on, when an interactive Automation script is being run, the UI components of type *Calendar* and *Time* will be able to retrieve the time zone and date/time settings of the client, and use those settings to format the time and date entered by the user.
When UI components of type *Calendar* or *Time* are used in interactive Automation scripts, up to now, the entered date and time would be formatted depending on the platform and the configured settings. From now on, when an interactive Automation script is being run, the UI components of type *Calendar* and *Time* will be able to return the time zone of the client and the time and date as entered by the user.

To allow the client to set the time zone, on the `UIBlockDefinition`, set the `ClientTimeInfo` option to `UIClientTimeInfo.Return`. This option is intended to be used for UI components of type *Calendar* or *Time* (the latter with either `AutomationDateTimeUpDownOptions`, `AutomationDateTimeUpDownOptions` or `AutomationDateTimePickerOptions`).
To allow the client to return the time zone and client time and date, on the `UIBlockDefinition`, set the `ClientTimeInfo` option to `UIClientTimeInfo.Return`. This option is intended to be used for UI components of type *Calendar* or *Time* (the latter with either `AutomationDateTimeUpDownOptions`, `AutomationDateTimeUpDownOptions` or `AutomationDateTimePickerOptions`).

The ShowUI command now include the following new methods that can be used to request the time zone and date/time settings of the client:
The result of the ShowUI command now includes the following new methods that can be used to request the time zone and date/time settings of the client:

- `TimeZoneInfo GetClientTimeZoneInfo(string destVar)`
- `DateTimeOffset GetClientDateTime(string destVar)`
Expand All @@ -118,7 +118,7 @@ If this time zone information has to be stored for later use, consider the follo
- Use the `Id` property, which can then be restored by using `TimeZoneInfo.FindSystemTimeZoneById(storedId)`.

> [!NOTE]
> The ID that is returned might not be available (anymore) on the DataMiner Agent that is executing the Automation script.
> The ID that is returned might not be available on the DataMiner Agent that is executing the Automation script.

For more info, see [Saving and restoring time zones](https://learn.microsoft.com/en-us/dotnet/standard/datetime/saving-and-restoring-time-zones)

Expand All @@ -128,8 +128,8 @@ This method will return the date and time as it was entered in the UI block with

The returned value will be `DateTimeOffset.MinValue` if the component does not exist, if `ClientTimeInfo` is not set to `UIClientTimeInfo.Return`, or if the component does not support the information.

> [!NOTE]
> Components that have `ClientTimeInfo` enabled should not have a *destVar* that contains "_DateTimeComponentClient". The identifier should be unique.
> [!IMPORTANT]
> Components that have `ClientTimeInfo` enabled should not have components with a *destVar* that contains "_DateTimeComponentClient".

#### Service & Resource Management: Configuring the script to be executed when a reservation goes into quarantine [ID 42067]

Expand Down
12 changes: 6 additions & 6 deletions release-notes/General/General_Main_Release_10.5/General_Main_Release_10.5.0_CU1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,11 +84,11 @@ A number of enhancements have been made to the ProtocolFunctionManager with rega

<!-- MR 10.5.0 [CU1] - FR 10.5.4 -->

When UI components of type *Calendar* or *Time* are used in interactive Automation scripts, up to now, the entered date and time would be formatted depending on the platform and the configured settings. From now on, when an interactive Automation script is being run, the UI components of type *Calendar* and *Time* will be able to retrieve the time zone and date/time settings of the client, and use those settings to format the time and date entered by the user.
When UI components of type *Calendar* or *Time* are used in interactive Automation scripts, up to now, the entered date and time would be formatted depending on the platform and the configured settings. From now on, when an interactive Automation script is being run, the UI components of type *Calendar* and *Time* will be able to return the time zone of the client and the time and date as entered by the user.

To allow the client to set the time zone, on the `UIBlockDefinition`, set the `ClientTimeInfo` option to `UIClientTimeInfo.Return`. This option is intended to be used for UI components of type *Calendar* or *Time* (the latter with either `AutomationDateTimeUpDownOptions`, `AutomationDateTimeUpDownOptions` or `AutomationDateTimePickerOptions`).
To allow the client to return the time zone and client time and date, on the `UIBlockDefinition`, set the `ClientTimeInfo` option to `UIClientTimeInfo.Return`. This option is intended to be used for UI components of type *Calendar* or *Time* (the latter with either `AutomationDateTimeUpDownOptions`, `AutomationDateTimeUpDownOptions` or `AutomationDateTimePickerOptions`).

The ShowUI command now include the following new methods that can be used to request the time zone and date/time settings of the client:
The result of the ShowUI command now includes the following new methods that can be used to request the time zone and date/time settings of the client:

- `TimeZoneInfo GetClientTimeZoneInfo(string destVar)`
- `DateTimeOffset GetClientDateTime(string destVar)`
Expand All @@ -109,7 +109,7 @@ If this time zone information has to be stored for later use, consider the follo
- Use the `Id` property, which can then be restored by using `TimeZoneInfo.FindSystemTimeZoneById(storedId)`.

> [!NOTE]
> The ID that is returned might not be available (anymore) on the DataMiner Agent that is executing the Automation script.
> The ID that is returned might not be available on the DataMiner Agent that is executing the Automation script.

For more info, see [Saving and restoring time zones](https://learn.microsoft.com/en-us/dotnet/standard/datetime/saving-and-restoring-time-zones)

Expand All @@ -119,8 +119,8 @@ This method will return the date and time as it was entered in the UI block with

The returned value will be `DateTimeOffset.MinValue` if the component does not exist, if `ClientTimeInfo` is not set to `UIClientTimeInfo.Return`, or if the component does not support the information.

> [!NOTE]
> Components that have `ClientTimeInfo` enabled should not have a *destVar* that contains "_DateTimeComponentClient". The identifier should be unique.
> [!IMPORTANT]
> Components that have `ClientTimeInfo` enabled should not have components with a *destVar* that contains "_DateTimeComponentClient".

#### Service & Resource Management: Configuring the script to be executed when a reservation goes into quarantine [ID 42067]

Expand Down
2 changes: 1 addition & 1 deletion ...notes/Web_apps/Web_apps_Feature_Release_10.5/Web_apps_Feature_Release_10.5.4.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ uid: Web_apps_Feature_Release_10.5.4

<!-- MR 10.4.0 [CU13] / 10.5.0 [CU1] - FR 10.5.4 -->

When UI components of type *Calendar* or *Time* are used in interactive Automation scripts, up to now, the entered date and time would be formatted depending on the platform and the configured settings. From now on, when an interactive Automation script is being run within a web app, the UI components of type *Calendar* and *Time* will be able to retrieve the time zone and date/time settings of the web session, and use those settings to format the time and date entered by the user.
When UI components of type *Calendar* or *Time* are used in interactive Automation scripts, up to now, entered date and time would be formatted depending on the platform and the configured settings. In case of a web app, the entered date and time would always be returned in UTC. From now on, when an interactive Automation script is being run within a web app, the UI components of type *Calendar* and *Time* will be able to return the time zone of the client and the time and date as entered by the user.

When a default time zone is defined for DataMiner web apps, that default time zone will be used instead of the time zone of the client. See also [Setting the default time zone for DataMiner web apps](xref:ClientSettings_json#setting-the-default-time-zone-for-dataminer-web-apps).

Expand Down