Intersect Schedule
- 28 Dec 2022
- 1 Minute to read
- Print
- DarkLight
Intersect Schedule
- Updated on 28 Dec 2022
- 1 Minute to read
- Print
- DarkLight
Article Summary
Share feedback
Thanks for sharing your feedback!
Step Details | |
| Introduced in Version | 4.0.0 |
| Last Modified in Version | 5.0.0 |
| Location | Designer Entities > Scheduling |
The Intersect Schedule step compares schedule data between two folders and returns anything where the schedules match.
Properties
Inputs
| Property | Description | Data Type |
|---|---|---|
| First Folder Id | Folder Id | String |
| From Date | Starting date | DateTime |
| Second Folder Id | Folder Id | String |
| To Date | End date | DateTime |
Outputs
| Property | Description | Data Type |
|---|---|---|
| Output | List of CalculationResult |
Common Errors
Parameter [toDate] of IntersectSchedules can not be null
If the toDate or fromDate fields are not configured, an error will occur.
To correct this, ensure that the date fields are properly mapped.
Exception Message:
Exception Stack Trace: DecisionsFramework.BusinessRuleException: [BusinessRule] Parameter 'toDate' of 'IntersectSchedules' can not be null at DecisionsFramework.Design.Flow.CoreSteps.InvokeMethodUtility.ThrowErrorIfNullIsNotAllowed(MethodInfo methodInfo, Object[] parameterValues, String errorMessage
at DecisionsFramework.Design.Flow.StepImplementations.InvokeMethodStep.Run(StepStartData data
at DecisionsFramework.Design.Flow.FlowStep.RunStepInternal(String flowTrackingID, String stepTrackingID, KeyValuePairDataStructure[] stepRunDataValues, AbstractFlowTrackingData trackingData
at DecisionsFramework.Design.Flow.FlowStep.Start(String flowTrackingID, String stepTrackingID, FlowStateData data, AbstractFlowTrackingData trackingData, RunningStepData currentStepData)Was this article helpful?
