|
Hi,
I figured it out eventually, here is the solution in case someone experiences a similar problem.
I used a plain text document template, for the ical template.
I create a file upload field to store the generated ical file.
then using an object script trigger, that runs after an update on the record,
I generated the output of the template using the "rbv_api.runTemplate" method, which returns the base-64 encoded string, of the generated template.
I then use the base-64 encoded string, to populate the file upload field using the "rbv_api.setBinaryFieldValue" method,
which also allows me to change the mime type to "text/calendar" as well as the filename and extension to .ics.
I then use the token of the uploaded file in my email, which results in the .ics file being attached in the email to the user.
Regards,
Stephen
Hi Guys,
I figured it out eventually, here is the solution in case someone experiences a similar problem.
I used a plain text document template, for the ical template.
I create a file upload field to store the generated ical file.
then using an object script trigger, that runs after an update on the record,
I generated the output of the template using the "rbv_api.runTemplate" method, which returns the base-64 encoded string, of the generated template.
I then use the base-64 encoded string, to populate the file upload field using the "rbv_api.setBinaryFieldValue" method,
which also allows me to change the mime type to "text/calendar" as well as the filename and extension to .ics.
I then use the token of the uploaded file in my email, which results in the .ics file being attached in the email to the user.
Regards,
Stephen
Hi Guys,
I figured it out eventually, here is the solution in case someone experiences a similar problem.
I used a plain text document template, for the ical template.
I create a file upload field to store the generated ical file.
then using an object script trigger, that runs after an update on the record,
I generated the output of the template using the "rbv_api.runTemplate" method, which returns the base-64 encoded string, of the generated template.
I then use the base-64 encoded string, to populate the file upload field using the "rbv_api.setBinaryFieldValue" method,
which also allows me to change the mime type to "text/calendar" as well as the filename and extension to .ics.
I then use the token of the uploaded file in my email, which results in the .ics file being attached in the email to the user.
Regards,
Stephen
Save the custom file in a file upload field on the object. Use template token (will replace the token with a file attachment) for the field in either a mail template or document template.
Hi,
I figured it out eventually, here is the solution in case someone experiences a similar problem.
I used a plain text document template, for the ical template.
I create a file upload field to store the generated ical file.
then using an object script trigger, that runs after an update on the record,
I generated the output of the template using the "rbv_api.runTemplate" method, which returns the base-64 encoded string, of the generated template.
I then use the base-64 encoded string, to populate the file upload field using the "rbv_api.setBinaryFieldValue" method,
which also allows me to change the mime type to "text/calendar" as well as the filename and extension to .ics.
I then use the token of the uploaded file in my email, which results in the .ics file being attached in the email to the user.
Regards,
Stephen
Hi Guys,
I figured it out eventually, here is the solution in case someone experiences a similar problem.
I used a plain text document template, for the ical template.
I create a file upload field to store the generated ical file.
then using an object script trigger, that runs after an update on the record,
I generated the output of the template using the "rbv_api.runTemplate" method, which returns the base-64 encoded string, of the generated template.
I then use the base-64 encoded string, to populate the file upload field using the "rbv_api.setBinaryFieldValue" method,
which also allows me to change the mime type to "text/calendar" as well as the filename and extension to .ics.
I then use the token of the uploaded file in my email, which results in the .ics file being attached in the email to the user.
Regards,
Stephen
Hi Guys,
I figured it out eventually, here is the solution in case someone experiences a similar problem.
I used a plain text document template, for the ical template.
I create a file upload field to store the generated ical file.
then using an object script trigger, that runs after an update on the record,
I generated the output of the template using the "rbv_api.runTemplate" method, which returns the base-64 encoded string, of the generated template.
I then use the base-64 encoded string, to populate the file upload field using the "rbv_api.setBinaryFieldValue" method,
which also allows me to change the mime type to "text/calendar" as well as the filename and extension to .ics.
I then use the token of the uploaded file in my email, which results in the .ics file being attached in the email to the user.
Regards,
Stephen