Current description holds for Traditional Web Development, the description for Reactive Web Development will follow later.
After installation of the component in your environment and including it to your app over the dependencies, the component’s actions can be easily used in the Preparation action of the Email component.
The following screenshot reveals the simplest usage of the component in case of the iCalendar event creation.
The only difficulty while applying this component is to pass the Organizer object and a list of Attendee objects. This can be easily accomplished by JSON serialization and by passing the objects as JSON string to the email component. This string can be deserialized in the Preparation action as it can be seen in the screenshot above.
In case you don’t use your own event identifier and prefer the generated identifier of the iCalendar component, you need to store the generated identifier somewhere. In the example above the event identifier is stored in the Site Property of the app, however depending on the use case it might be better to manage this identifier using a dedicated entity.
In short, from the example above only two widgets are necessary to create an iCalendar email attachment. The Publish_iCalendarEvent will create a binary which can be provided to the Attach File widget of the Email component.
This means that the simplest usage example can be shown in case of Cancel_iCalendarEvent_light as following.
It might be helpful to have a look to the demo app, which can be downloaded with this component. It shows how you can provide to the user the editing of the HTML description using e.g. CKEditor.