Your Own Event Layouts

%center% %newwin width=440% [[https://www.seedcode.com/rootimages/stikipad/dayback/ShowEvents2.png | https://www.seedcode.com/rootimages/stikipad/dayback/ShowEvents2.png]]

%center% %newwin width=440% [[https://www.seedcode.com/rootimages/stikipad/dayback/ShowEvents3.png | https://www.seedcode.com/rootimages/stikipad/dayback/ShowEvents3.png]]

%center% %newwin width=440%  [[https://www.seedcode.com/rootimages/stikipad/dayback/refresh-after-delete.png | https://www.seedcode.com/rootimages/stikipad/dayback/refresh-after-delete.png]]

!! Update the calendar view after deleting a filemaker record?

https://www.youtube.com/watch?v=nxi8abtlBn0

!! What if the layout I want to use is in my own file?

That's actually pretty easy to handle. You'll still edit the script "Load Source Settings at Startup --- Describe Your Sources Here ---" to tell DayBack that you'd like to use a FileMaker layout for one of your sources (watch the movie above or edit that script after the comment "Should we show event details using a FileMaker layout? Boolean - True or False").

Then you'll edit the script "Show Event Details From WebViewer" adding the four lines shown below to call a script in ''your'' file, passing in the ID of the event you clicked on as the script parameter $eventID.

%center% %newwin width=440% [[https://www.seedcode.com/rootimages/stikipad/dayback/showevents.png | https://www.seedcode.com/rootimages/stikipad/dayback/showevents.png]]

Note that the lines shown above are shown in the "edit" branch of the "Show Event Details From WebViewer" script; you could add the same kind of branch to the "create" section right above it.

%center% %width=440% https://www.seedcode.com/rootimages/stikipad/dayback/refresh-after-delete.png

%newwin% %width=440% [[https://www.seedcode.com/rootimages/stikipad/dayback/showevents.png | https://www.seedcode.com/rootimages/stikipad/dayback/showevents.png]]

%newwin% %center width=400px% [[https://www.seedcode.com/rootimages/stikipad/dayback/showevents.png | https://www.seedcode.com/rootimages/stikipad/dayback/showevents.png]]

%newwin% %center width=400% [[https://www.seedcode.com/rootimages/stikipad/dayback/showevents.png | https://www.seedcode.com/rootimages/stikipad/dayback/showevents.png]]

If you would like to update the calendar view when deleting a record the easiest way is to add a script step to the "On Event Record Load" script. This script is called on a layout script trigger "OnRecordLoad" and is run whenever an event record loads (this includes when an event is deleted) in our included event detail layouts. Simply add a Perform Script "Refresh Webviewer" script step inside the if statement as shown in the image below.

If you would like to update the calendar view when deleting a record the easiest way is to add a script step to the "On Event Record Load" script. This script is called on a layout script trigger "OnRecordLoad" and is run whenever an event record loads (this includes when an event is deleted) in our included event detail layouts. Simply add a Perform Script "Refresh Webviewer" script step inside the if statement as shown in the image below.

To remove an event from the calendar view just pass a few parameter values into the script "Refresh Calendar Event (Data ; {EventID ; RenderID ; QueryID ; Operation ; ForceRefresh} )".

So an example of a parameter for that script might look like:

#("sc_Data" ; "") &
#("sc_EventID" ; $sc_EventID) &
#("sc_Operation" ; "delete")

I would suggest duplicating the "Close Event Window & Refresh Calendar" script and adding a delete record before the close window script step for your delete button. Then changing the "Data" parameter when calling "Refresh Calendar Event (Data ; {EventID ; RenderID ; QueryID ; Operation ; ForceRefresh} )" to what is shown above. Then remove the "If" statement that wraps that script step as we don't need to check for record modification when deleting. These changes will change the script to delete the record, close the window, and then update the calendar view to reflect the deleted event.

Make sure to remove or change any on record load script triggers that might interfere with the script as that trigger will run when deleting a record.

If you choose to use your own layout rather than DayBack popovers you may want to manage when event changes show up on the calendar. This is ultimately handed by the script "Refresh Calendar Event (Data ; {EventID ; QueryID ; ForceRefresh} )". This script takes event data and an event ID and updates the  event display on the calendar. This script should be run after the event window is closed so it is executed from the context of the calendar layout. For an example we use the script "Close Event Window & Refresh Calendar" on our "To Do Details" layout to update the event on closing the window. We recommend copying the "Close & Refresh Calendar" button off of that layout and using it on your layouts as it calls that script and is a great starting point.

To remove an event from the calendar view just pass a boolean false statement into the data parameter for "Refresh Calendar Event (Data ; {EventID ; QueryID ; ForceRefresh} )". So that would be either False or 0. I would suggest duplicating the "Close Event Window & Refresh Calendar" script and adding a delete record before the close window script step for your delete button. Then changing the "Data" parameter when calling "Refresh Calendar Event (Data ; {EventID ; QueryID ; ForceRefresh} )" to a false value. Then remove the "If" statement that wraps that script step as we don't need to check for record modification when deleting. These changes will change the script to delete the record, close the window, and then update the calendar view to reflect the deleted event.

To remove an event from the calendar view just pass a boolean false statement into the data parameter for "Refresh Calendar Event (Data ; {EventID ; QueryID ; ForceRefresh} )". So that would be either False or 0. I would suggest duplicating the "Close Event Window & Refresh Calendar" script and adding a delete record before the close window script step for your delete button. Then changing the "Data" parameter when calling "Refresh Calendar Event (Data ; {EventID ; QueryID ; ForceRefresh} )" to a false value. Then remove the "If" statement that wraps that script step as we don't need to check for record modification when deleting. These changes will change the script to delete the record, close the window, and then update the calendar view to reflect the deleted event.

To remove an event from the calendar view just pass a boolean false statement into the data parameter for "Refresh Calendar Event (Data ; {EventID ; QueryID ; ForceRefresh} )". So that would be either False or 0. I would suggest duplicating the "Close Event Window & Refresh Calendar" script and adding a delete record before the close window script step for your delete button. Then changing the "Data" parameter when calling "Refresh Calendar Event (Data ; {EventID ; QueryID ; ForceRefresh} )" to a false value. This edit would delete the record, close the window, and then update the calendar view to reflect the deleted event.

If you choose to use your own layout rather than DayBack popovers you may want to manage when event changes show up on the calendar. There is a script called "Refresh Calendar Event (Data ; {EventID ; QueryID ; ForceRefresh} )". This script takes event data and an event ID and updates the  event display on the calendar. This script should be run after the event window is closed. For an example we use the script "Close Event Window & Refresh Calendar" on our ToDo Detail layout to update the event on closing the window. We recommend copying the close button off of that layout and using it on your layouts.

To remove an event from the calendar view just pass a boolean false statement into the data parameter for "Refresh Calendar Event (Data ; {EventID ; QueryID ; ForceRefresh} )". So that would be either False or 0. I would suggest duplicating the "Close Event Window & Refresh Calendar" script and adding a delete record before the close window script step for your delete button.

You'd also select your layout in the script "Load Source Settings at Startup --- Describe Your Sources Here ---" after the comment "Which layout should we use to display event details for this source?". Be sure to run the upon opening script after editing that Source Settings script.

No. You can certainly use your own. Just reference your layout in any [[custom action]] scripts that need to land on your layout (our example script, "Go To Event Record from Webviewer" uses our "Action - View Event" layout but can certainly use yours.

No. You can certainly use your own. There are just a few things to keep in mind.

'''Event List'''

-> There are a few script steps that reference this layout (such as when you wish to see repeating events as a list) so rename ''your'' event list layout to "Event List" before importing the scripts in your [[integration]]. After the scripts are in you can rename your layout back to whatever you'd named it before.

'''Event Details'''

-> The event details layout is the one we go to when clicking on an event in the calendar and when making a new one from within the calendar. Thus a lot more scripts point to this layout.

->This is a mini window (a small window) so you can still see calendar events behind it while you're editing the event: we also kept it small because we bring up several of these small windows when you click on a conflicting event.

-> So, you may want to keep our Event Details layout even if you already have one, since it can be convenient to have a small, quick reference version of the event. What many people do is add a button to our Event Details layout (which is fully customizable, by the way) which jumps to their larger Event Details layout...

!! Making New Records

In order for you to arrive at your own layout when you ''create'' an event on the calendar, edit the script "Create Edit Delete Event ( SourceNo ) { Operation , Hide, DateStart , DateEnd , TimeStart ... }" and find the comment "--------- Create -------". A few steps after that you'll see a go to layout command: change that to your layout and you'll be all set.

%color=red% >> How to use your own event layouts a) instead of a popover, b) as a supplement to a popover with Custom Actions.