Schedule Webinar via EspoCRM

[SailReal]

Hey all,

We are planing to organise Webinars using Espo.

The current PoC is to create a Meeting in Espo, over time (not all by one but they can register using an website etc) attach the Leads to the Meeting using an Flowchart (`record\relate('Meeting', $meetingId, 'leads', entity\attribute('id'));`) and also send the invitation to the newly attached lead via API call to 'https://crm/api/v1/Meeting/action/sendInvitations' and payload '{"id":"{$$meetingId}","targets":[{"entityType":"Lead","id":"{$$leadId}"}]}'.
This works quiet well but we need to overwrite the Meetings templates which I would like to avoid to not block this feature to be used for other use cases as well. Is there another way to send invitations by specifying the used template? Or do you have another/better approach in general?

Thank you!

[heint]

Greetings SailReal,

If you planning to change exactly the following template as on the screenshot below:


The easiest way here is to use {{#if}} statment for both or even more scenarios.

1. Create a boolem field for Meeting entity (name of my test field is - cIsStandartTemplate)
2. Put your desired content into if statment at Administration > Template Manager > Invitation > Meeting (as shown in the screenshot above):

{{#if cIsStandartTemplate}} /////
<p>Subject: {{name}}</p>
<p>Start: {{#if isAllDay}}{{dateStartFull}}{{else}}{{dateStartFull }} ({{timeZone}}){{/if}}</p>
{{#if isUser}}
{{#if description}}
<p>{{{description}}}</p>
{{/if}}
{{/if}}
<p>
<a href="{{acceptLink}}" style="font-size: 1.2em">Accept</a> ·
<a href="{{tentativeLink}}" style="font-size: 1.2em">Tentative</a> ·
<a href="{{declineLink}}" style="font-size: 1.2em">Decline</a>
</p>
{{#if joinUrl}}
<p>
<a href="{{joinUrl}}">Join</a>
</p>
{{/if}}
{{#if isUser}}
<p><a href="{{recordUrl}}">View record</a></p>
{{/if}}
{{/if}} ////

<p>Hello test</p> /////

(marked fields 1 and -2 with *////* slashes is what i added to the standart template)

In result, if i want to display only "Hello test" text - i keep my boolem field unchecked (false).

Not sure if EVERY functionality will persist, but it's really the easiest way to implement your request logic what i could think of.