Hi,
I am using your scheduler component and the user can create different types of events. They are polymorphic events, meaning the main data is stored in an 'event' table and depending on the type of event other data is stored in other tables. Therefore I would like to know how it is possible to send different create action depending on the event type.
The website has been built in steps and the events are being created using different forms. I plan to, have a custom template from which the user can select an event type and then enter the rest of the information. The only bit i am unsure of is posting to different URLs.
Any help will be greatly appreciated
Ta
6 Answers, 1 is accepted
This can be achieved by either using function for the "create.url" option or set the parent "create" option to function to make entirely custom requests. Please check the related documentation below:
Regards,
Vladimir Iliev
Telerik

Hi Vladimir,
Many thanks for you reply, it looks as though it is something that will work. However, i need to go back a step or two and customise the editor that is displayed. I have managed to get a custom template working using this code
editable: {
template: $("#editor").html()
},
and defining the html. However, as part of my previous question I need to provide an initial screen for the user to select an event type. I know you will not know for definite but I would like to integrate this library into the template http://www.jqueryscript.net/demo/Create-Step-By-Step-Modal-with-jQuery-Bootstrap/ as this would allow me to accomplish what I need. Do you think it possible?
If not do you think it possible to show a context menu from which the user can select the Event Type and then your editor is invoked.
Sorry for the series of questions I would just like to know what is possible with the component.
Many thanks
Yes, the desired behavior is possible to achieve.
Regards,
Vladimir Iliev
Telerik

Hi Vladimir,
Any pointers to how this can be achieved?
Thanks
Rudy
Please note that integrating third party libraries falls outside the scope of our support service. In this cases the developer is entirely responsible for implementing and supporting these custom solutions.
Regards,
Vladimir Iliev
Telerik

For anyone who may be interested this is the bones of the solution:
The underlying JavaScript does not need changes, just the editor template needs them. The editor template should be considered as partial view where you can implement the logic for having navigation between several small views by including desired html and nested scripts. You should just make sure all nested script tags and "#" symbols are escaped correctly - please check the example below:
<script id="customEditorTemplate" type="text/x-kendo-template">
<div id="editorContainer">
Some Html:
<input type="text" />
<script>
alert("template is just executed, edit container is logged in console");
console.log($("\#editorContainer"));
<\/script>
</div>
</script>
Thanks
Rudy