Calendar Files - expand the use of tokens for all attributes

[Anonymous]

Please consider expanding the use of tokens to all of the field availible in the ICS file.  Tokens would provide a way to make the process repeatable and will remove the possibility to make mistakes by removing the issue of duplicate data entry especially relevant when program cloning occurs.

Below is a sample of the Calendar file object might look like if tokens were allowed.

[Anonymous]

I agree that this could have been implemented more logically.

The Calendar File (ics) should really be a local asset that uses the my tokens that we already created/defined for the event name, venue, dates and times (rich text), so that this data can be referenced consistently in all of the program emails (1st, 2nd, 3rd invitations, confirmation, reminders, etc.).  You would embed the link to the Calendar File just like you embed the link to a Landing Page, which is a more consistent UI paradigm.

In fact, we have been creating our own ics files, loading them into the Design Studio's Images and Files folder and adding a link to that file in our confirmation and reminder emails.  The new Calendar File token with its static basic data and tokens only in the description, isn't much of an improvement.

[Anonymous]

We have also decided not to adopt this new feature as we don't believe it is ready to implementation.

[Anonymous]

Agreed, we were very anxious for this release, then immediately disappointed to realize we're still better off manually creating .ics files as we did before.

[Anonymous]

Adding token support to the file inputs is much more difficult and there are some limitations but we are going to look into adding it regardless.   There is a benefit to having support for the member.webinar URL token in the description, which was one of the main drivers for this feature. 

I'm working with engineering to see when we can add the token support everywhere, but it might be a few months out at this point.

[Anonymous]

Cheryl, any thought to making the Calendar File a local asset rather than a token with tokens inside of it?

[Anonymous]

Elliott, We did think of that, but it would have been a much bigger project.  All kinds of implications in the system.  Attachments to emails, approval workflow, import from Library/sandbox etc etc.  This way seemed more straight-forward.

Tokens is near and dear to my heart and I think this idea is important.  It's still worth having the feature out there, but we need to follow-through with additional token support.

[Anonymous]

Hi Glen,

Any update on this feature? We would LOVE to use this as part of our call team's processes!

[Anonymous]

There are no immediate plans, but it's a good idea.  The more people vote for it, the more important it becomes.