An efficient module for generating appointment (ICS) files that can be attached to emails. It allows you to create, update, and delete ics appointment files while providing flexibility to add additional information like location and organizer details.
An easy way to generate appointment (ics) files to attach to an email.
- Generate Create/Update/Delete ics appointment files
- Add desired extra input to the appointment like location, description, etc.
- Optionally set a TimeZone
Simply add the SUB_IcalMessage_CreateFile microflow to wherever you wish to generate an ics file. It simply needs an IcalMessage object. Only the start/end time and subject are mandatory, but it's recommended to populate all fields. The AttendeesList parameter required a list of Attendee objects. Be careful not to rename this entity.
If you wish to test the ics files, you can add the SNIP_ICalendar to a page.
In order to correctly send a ICS file via an Email you need to set the correct attachment header. If you are using the Email Connector module you should use their Attachment mechanism to add the ICS file to an email. You can then use the attachmentContentType attribute from the Attachment entity in the Email Connector module to set the correct header. The value should be something like this text/calendar; charset=utf-8; method=REQUEST; name=event.ics. Notice here that you have to set the correct method to the same value that the ical status has.
Sending an update for an appointment
Updated on the same appointment should have the same UID so that the system understands its about the same event. It is also recommended to update the sequence number if you want to send an update about an existing appointment you have already sent earlier. For example, when you cancel an already sent appointment later on (the first mail will have an ics file with sequence 0, and the next one should have a 1). In that case, it is wise to commit the IcalMessage object after sending it the first time and then retrieving it when sending an update. In the SUB_IcalMessage_CreateFile, it will already have updated the sequence number.
There is an optional parameter for a TimeZone. You can leave this empty to use the server timezone. If you do want to use TimeZones I recommended using the TimeZone entity that already exists in the System module of Studio Pro since it already contains the code you need to set a TimeZone. Simply put the Code attribute in the TimeZone field and it should work. You can also set the TimeZone manually if you only want to use 1 perticular zone. (for example "Europe/London").
Issues, Suggestions, and Feature Requests
Please feel free to raise any issues, share suggestions, or request new features on the GitHub repository: