This enables a pattern of availabilities to be defined for either a Location,Location Type, Appointment Request, Activity or Activity_Type_Id. The system will automatically create these availabilities over the scheduling window.
Syntax:
[ DynamicComponentDependency ] availabilitypattern AvailabilityPatternName {
[ TimeSpanUOM ] [ TimeZoneOverride ] [ ChangeDetection ] [ CustomChangeHandler ] #SqlDml.QueryBlock ;
}
Column Name | Data Type | Description | Default Value |
---|---|---|---|
id | String(32) | Defines a unique id for the availability pattern. | |
close_time | Number (minutes by default) | Specifies the closing time of the availability. | |
period_end_datetime | Date | Defines the end date and time for the pattern to be applied. | |
period_start_datetime | Date | Specifies the starting date and time for the pattern to be applied. |
Column Name | Data Type | Description | Default Value |
---|---|---|---|
day_pattern | String(7) | Seven character string indicating each day of the week the default pattern should apply too. | YYYYYNN |
open_time | Number (minutes by default) | Defines the time each day specified in day_pattern when the availability starts. | 08:00:00 |
activity_id | String(32) | Specifies the activity to which the availability pattern should be applied. | |
activity_type_id | String(32) | Specifies the activity type to which the availability should be applied. | |
appointment_request_id | String(32) | Specifies the id of the appointment request to which the availability pattern should be applied. | |
availability_type | String(32) | Specifies the type of availability. | |
location_id | String(32) | Specifies the location to which the availability pattern should be applied. | |
location_type_id | String(32) | The location type to which the availability pattern should be applied. | |
start_based | Number (0 = False, 1 = True) | Enforce availability against start time of activity or total duration of activity. | |
time_zone | String(32) | The UTC timezone code to be used for open_time, close_time and day_pattern. |
availabilitypattern AvailabilityPattern {{SelectName}} { SELECT .. id, .. close_time, .. period_end_datetime, .. period_start_datetime, -- optional columns .. day_pattern, .. open_time, .. activity_id, .. activity_type_id, .. appointment_request_id, .. availability_type, .. location_id, .. location_type_id, .. start_based, .. time_zone FROM {{sourceTableName}} WHERE ...; }
Note: All selected columns must have correct aliases that match a IFS Scheduling AvailabilityPattern.
Syntax:
<Identifier>
This page is generated from IFS Developer Studio at 2021-08-13 08:48.