Cancel Event
  • 31 Jan 2023
  • 1 Minute to read
  • Dark
    Light

Cancel Event

  • Dark
    Light

Article summary

Step Details

Introduced in Version4.0.0
Last Modified in Version7.1.0
LocationIntegration > ICAL > ICAL File

The Cancel Event step allows users to create an iCal file to cancel an event that was created. The Appointment ID, Duration, and Start fields must match the same fields of the created event.


Prerequisites 

This step requires the iCal module to be installed before it will be available in the toolbox. 


Properties

Inputs

PropertyDescriptionData Type
Appointment IdAllows a user to specify the Appointment Id
String
DescriptionAllows the user to describe the created event or reason for cancellation String
DurationSpecifies how long the event will be
TimeSpan
Is All DayDetermines if the event will be the entire specified day
Boolean
LocationSpecifies the location of the event
String
StartSpecifies the date the event will start
DateTime
SummaryAllows the user to give a summary of the event
String

Outputs

PropertyDescriptionData Type
OutputCalendar ics file
FileData

Example Inputs and Outputs

Appointment IdLocationStartOutput
372747273Room 1121/22/2021iCalendar.ics
NullConference A1/22/2024 12:30:00iCalendar.ics
32443NullNullEXCEPTION MESSAGE
3490998NullEmptyEXCEPTION MESSAGE


Common Errors

Parameter 'start' of 'CancelEvent' can not be null

If the Start input field is null or empty, the step will cause an error.

To correct this, ensure that the field has a specified date and time that matches the Start field of the created event.

Exception Message:

Exception Stack Trace: DecisionsFramework.BusinessRuleException: [BusinessRule] Parameter 'start' of 'CancelEvent' 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?

What's Next