DayBackOnline
Custom Action Examples
DayBackOnline.CustomActionExamples History
Hide minor edits - Show changes to markup
Changed line 56 from:
This On Save event action turns attempts to create an all-day event action into a scheduled event at the current time-slot with the duration set from your DayBack settings. disableAllDayEventsV1.js
to:
This On Event Create event action turns attempts to create an all-day event action into a scheduled event at the current time-slot with the duration set from your DayBack settings. disableAllDayEventsV1.js
Added lines 51-56:
Disable All-Day Events
This On Save event action turns attempts to create an all-day event action into a scheduled event at the current time-slot with the duration set from your DayBack settings. disableAllDayEventsV1.js
Changed lines 36-37 from:
This custom function takes advantage of the seedcodeCalendar.get(filterType) function to create a URL that can be shared with DayBack users within your organization. This link will take them right to the same view, with the same filters applied to the calendar, and even open the same event you have open:
(Upload Coming Soon!)
to:
This custom function takes advantage of the seedcodeCalendar.get(filterType) function to create a URL that can be shared with DayBack users within your organization. This link will take them right to the same view, with the same filters applied to the calendar, and even open the same event you have open: CreateInternalURL.js
Changed line 36 from:
This custom function takes advantage of the seedcodeCalendar.get(filterType) function to create a URL that can be shared with DayBack users within your organization. This link will take them right to the same view, with the same filters applied to the calendar, and even open the same event you have open:
to:
This custom function takes advantage of the seedcodeCalendar.get(filterType) function to create a URL that can be shared with DayBack users within your organization. This link will take them right to the same view, with the same filters applied to the calendar, and even open the same event you have open:
Changed lines 44-51 from:
to:
Send an Email with a custom or event action
Here are 2 separate examples that compose a new email with the event details in the system's default mail client: SendEmail.zip
emailSupport.js is a custom action that allows you to press a button in the event window and compose an email to "support" with the title, description, and a link to the event.
emailSupportOnHold.js is an event action that triggers when the event is saved and it's status changed to your specified status ('On Hold' in this example). It will then compose an email notifying the event is in the specified status and containing the title, description, and a link to the event.
Changed line 27 from:
We use a wufoo form in this example since it's simple: field validation and emailing is all handled by wufoo so the event action we have to write is pretty simple. Here's a short video of this one in action.
to:
We use a wufoo form in this example since it's simple: field validation and emailing is all handled by wufoo so the event action we have to write is pretty simple. Here's a short video of this one in action.
Changed line 27 from:
We use a wufoo form in this example since it's simple: field validation and emailing is all handled by wufoo so the event action we have to write is pretty simple.
to:
We use a wufoo form in this example since it's simple: field validation and emailing is all handled by wufoo so the event action we have to write is pretty simple. Here's a short video of this one in action.
Added lines 23-27:
Confirm Appointments or Collect Information in a Form
Designed to be run as an event action in a shared view, this will show a simple wufoo form when a recipient clicks on an event. DayBack passes some event details into the form and then a receipt of the confirmation is sent to the recipient and the organizer. confirmAppointmentWuFooForm.js
We use a wufoo form in this example since it's simple: field validation and emailing is all handled by wufoo so the event action we have to write is pretty simple.
Changed line 21 from:
Here's a related action that will open a URL in the Location field or show a dialog that the field is empty: conditionallyOpenURLjs
to:
Here's a related action that will open a URL in the Location field or show a dialog that the field is empty: conditionallyOpenURLjs
Added lines 20-22:
Here's a related action that will open a URL in the Location field or show a dialog that the field is empty: conditionallyOpenURLjs
Changed line 34 from:
This custom function allows you to specify fields in which you would like to verify data entry. ValidateFieldEntry.js If a specified field is left empty, a notice will pop-up notifying the user and allowing them to continue editing the event in the popover, or save the event with the empty fields. Click here for a video of it in action.
to:
This custom function allows you to specify fields in which you would like to verify data entry. ValidateFieldEntry.js If a specified field is left empty, a notice will pop-up notifying the user and allowing them to continue editing the event in the popover, or save the event with the empty fields. Click here for a video of it in action.
Changed lines 34-35 from:
This custom function allows you to specify fields in which you would like to verify data entry. If a specified field is left empty, a notice will pop-up notifying the user and allowing them to continue editing the event in the popover, or save the event with the empty fields. Click here for a video of it in action.
(Upload Coming Soon!)
to:
This custom function allows you to specify fields in which you would like to verify data entry. ValidateFieldEntry.js If a specified field is left empty, a notice will pop-up notifying the user and allowing them to continue editing the event in the popover, or save the event with the empty fields. Click here for a video of it in action.
Added lines 30-37:
Validate Field Data Entry
This custom function allows you to specify fields in which you would like to verify data entry. If a specified field is left empty, a notice will pop-up notifying the user and allowing them to continue editing the event in the popover, or save the event with the empty fields. Click here for a video of it in action.
(Upload Coming Soon!)
Changed line 26 from:
Create a link to your existing view for DayBack users within your organization
to:
Create a link to your existing calendar view for DayBack users within your organization
Added lines 24-29:
Create a link to your existing view for DayBack users within your organization
This custom function takes advantage of the seedcodeCalendar.get(filterType) function to create a URL that can be shared with DayBack users within your organization. This link will take them right to the same view, with the same filters applied to the calendar, and even open the same event you have open:
(Upload Coming Soon!)
Changed lines 33-37 from:
� Calling a script in WebDirect will create a new database session that FileMaker Server treats as a new concurrent connection.
� Before the script runs your solutions "OnFirstWindowOpen" script will run.
� If you elect to run the action on the same window and you show the WebDirect toolbar, you'll see a second tool bar below the current one. (That's a WebDirect bug we hope gets squashed soon.)
to:
• Calling a script in WebDirect will create a new database session that FileMaker Server treats as a new concurrent connection.
• Before the script runs your solutions "OnFirstWindowOpen" script will run.
• If you elect to run the action on the same window and you show the WebDirect toolbar, you'll see a second tool bar below the current one. (That's a WebDirect bug we hope gets squashed soon.)
Changed line 9 from:
'Schedule GoToMeetings from DayBack
to:
Schedule GoToMeetings from DayBack
Changed line 11 from:
Create, reschedule, and start GoToMeetings from within DayBack Calendar. Instructions and a movie of this in action are .
to:
Create, reschedule, and start GoToMeetings from within DayBack Calendar. Instructions and a movie of this in action are here.
Added lines 9-12:
'Schedule GoToMeetings from DayBack
Create, reschedule, and start GoToMeetings from within DayBack Calendar. Instructions and a movie of this in action are .
Changed line 45 from:
Keep in mind when writing Javascript for custom actions that the code is executed when loaded (it's loaded when the button to run the action is clicked). So things like onload or jQuery $.ready() aren't necessary here.
to:
Keep in mind when writing Javascript for custom actions that the code is executed when loaded (it's loaded when the button to run the action is clicked). So things like onload or jQuery $.ready() aren't necessary here.
Changed line 25 from:
https://<host>/fmi/webd#<database name>[?script=<script name> [¶m=<script parameter>][&<$variable name>=<value>]]
to:
https://<host>/fmi/webd#<database name>?script=<script name>[¶m=<script parameter>][&<$variable name>=<value>]]
Deleted line 12:
Added lines 16-19:
Track UPS Package
Similar to opening a url, this action looks through your event's description and will track the first UPS package code it finds: track-ups.js
Changed line 1 from:
Some custom actions scripts you can start using
to:
Some Custom Action Scripts You Can Start Using
Changed line 1 from:
Some custom actions scripts you can start working with
to:
Some custom actions scripts you can start using
Changed line 1 from:
Custom Action Examples
to:
Some custom actions scripts you can start working with
Changed line 32 from:
What Kind of Javascript Can I Use]?
to:
What Kind of Javascript Can I Use?
Deleted lines 0-7:
What Kind of Javascript Can I Use]?
Most everything. We don't allow access to the global window object but all built in functions for window can still be called directly. For example: open(), close(), alert(), location.href, can all be used as long as you don't use them in the context of window. In other words use location.href instead of window.location.href.
DayBack also includes a few popular libraries to make coding easier. jQuery, BootStrap, and moment.js are all included. So anything you can do in one of those libraries can be used in a custom action.
Keep in mind when writing Javascript for custom actions that the code is executed when loaded (it's loaded when the button to run the action is clicked). So things like onload or jQuery $.ready() aren't necessary here.
Added lines 31-38:
What Kind of Javascript Can I Use]?
Most everything. We don't allow access to the global window object but all built in functions for window can still be called directly. For example: open(), close(), alert(), location.href, can all be used as long as you don't use them in the context of window. In other words use location.href instead of window.location.href.
DayBack also includes a few popular libraries to make coding easier. jQuery, BootStrap, and moment.js are all included. So anything you can do in one of those libraries can be used in a custom action.
Keep in mind when writing Javascript for custom actions that the code is executed when loaded (it's loaded when the button to run the action is clicked). So things like onload or jQuery $.ready() aren't necessary here.
Changed line 13 from:
Slack WebHook (Send A Message To {https://www.slack.com | Slack]] Group Chat)
to:
Slack WebHook (Send A Message To Slack Group Chat)
Changed line 13 from:
Slack WebHook (Send A Message To Slack Group Chat)
to:
Slack WebHook (Send A Message To {https://www.slack.com | Slack]] Group Chat)
Changed line 15 from:
Here is the code for our popular post-to-slack demo: dayBackSlack.js
to:
Here is the code for our popular post-to-slack demo: dayBackSlack.js
Changed line 15 from:
Here is the code for the post-to-Slack demo in the move above: dayBackSlack.js
to:
Here is the code for our popular post-to-slack demo: dayBackSlack.js
Changed line 19 from:
Show an in-line time tracker from your harvest account to start a timer related to this task. This is the time tracking widget we demo'ed at DevCon 2015 (movie here ). harvest.js
to:
Show an in-line time tracker from your harvest account to start a timer related to this task. This is the time tracking widget we demo'ed at DevCon 2015 (movie here ): harvest.js
Changed line 24 from:
This looks through your event's description and will open the first URL it finds. openFirstUrl.js
to:
This action looks through your event's description and will open the first URL it finds: openFirstUrl.js
Added line 29:
Added line 31:
Changed lines 32-36 from:
� Calling a script in WebDirect will create a new database session that FileMaker Server treats as a new concurrent connection.
� Before the script runs your solutions "OnFirstWindowOpen" script will run.
� If you elect to run the action on the same window and you show the WebDirect toolbar, you'll see a second tool bar below the current one. (That's a WebDirect bug we hope gets squashed soon.)
to:
� Calling a script in WebDirect will create a new database session that FileMaker Server treats as a new concurrent connection.
� Before the script runs your solutions "OnFirstWindowOpen" script will run.
� If you elect to run the action on the same window and you show the WebDirect toolbar, you'll see a second tool bar below the current one. (That's a WebDirect bug we hope gets squashed soon.)
Added line 33:
Added line 35:
Changed lines 32-34 from:
- Calling a script in WebDirect will create a new database session that FileMaker Server treats as a new concurrent connection.
- Before the script runs your solutions "OnFirstWindowOpen" script will run.
- If you elect to run the action on the same window and you show the WebDirect toolbar, you'll see a second tool bar below the current one. (That's a WebDirect bug we hope gets squashed soon.)
to:
� Calling a script in WebDirect will create a new database session that FileMaker Server treats as a new concurrent connection.
� Before the script runs your solutions "OnFirstWindowOpen" script will run.
� If you elect to run the action on the same window and you show the WebDirect toolbar, you'll see a second tool bar below the current one. (That's a WebDirect bug we hope gets squashed soon.)
Changed lines 31-33 from:
Calling a script in WebDirect will create a new database session that FileMaker Server treats as a new concurrent connection.
Before the script runs your solutions "OnFirstWindowOpen" script will run.
If you elect to run the action on the same window and you show the WebDirect toolbar, you'll see a second tool bar below the current one. (That's a WebDirect bug we hope gets squashed soon.)
to:
- Calling a script in WebDirect will create a new database session that FileMaker Server treats as a new concurrent connection.
- Before the script runs your solutions "OnFirstWindowOpen" script will run.
- If you elect to run the action on the same window and you show the WebDirect toolbar, you'll see a second tool bar below the current one. (That's a WebDirect bug we hope gets squashed soon.)
Changed lines 30-33 from:
There are a couple caveats to running scripts in WebDirect via urls. We hope FileMaker, Inc. will change this in a future version, but for now...
to:
There are a couple caveats to running scripts in WebDirect via urls. We hope FileMaker, Inc. will change this in a future version, but for now...
Calling a script in WebDirect will create a new database session that FileMaker Server treats as a new concurrent connection.
Before the script runs your solutions "OnFirstWindowOpen" script will run.
If you elect to run the action on the same window and you show the WebDirect toolbar, you'll see a second tool bar below the current one. (That's a WebDirect bug we hope gets squashed soon.)
Changed lines 28-29 from:
Here is the url format you'd use to execute a script in FileMaker WebDirect:
https://<host>/fmi/webd#<database name>[?script=<script name> [¶m=<script parameter>][&<$variable name>=<value>]]
to:
You can use custom actions to fire scripts in your FileMaker Pro solution, in FileMaker Go, or in WebDirect. For Pro and Go you'll use the fmp;// url format documented here. For WebDirect you'll use a slightly different format. Here is the url format you'd use to execute a script in FileMaker WebDirect:
https://<host>/fmi/webd#<database name>[?script=<script name> [¶m=<script parameter>][&<$variable name>=<value>]]
There are a couple caveats to running scripts in WebDirect via urls. We hope FileMaker, Inc. will change this in a future version, but for now...
Changed lines 28-29 from:
Here is the url format you'd use to execute a script in FileMaker WebDirect: https://<host>/fmi/webd#<database name>[?script=<script name> [¶m=<script parameter>][&<$variable name>=<value>]]
to:
Here is the url format you'd use to execute a script in FileMaker WebDirect:
https://<host>/fmi/webd#<database name>[?script=<script name> [¶m=<script parameter>][&<$variable name>=<value>]]
Changed line 28 from:
Here is the url format you'd use to execute a script in FileMaker WebDirect: https://<host>/fmi/webd#<database name>[?script=<script name> [¶m=<script parameter>][&<$variable name>=<value>]]
to:
Here is the url format you'd use to execute a script in FileMaker WebDirect: https://<host>/fmi/webd#<database name>[?script=<script name> [¶m=<script parameter>][&<$variable name>=<value>]]
Changed lines 24-28 from:
This looks through your event's description and will open the first URL it finds. openFirstUrl.js
to:
This looks through your event's description and will open the first URL it finds. openFirstUrl.js
Call Scripts in WebDirect
Here is the url format you'd use to execute a script in FileMaker WebDirect: https://<host>/fmi/webd#<database name>[?script=<script name> [¶m=<script parameter>][&<$variable name>=<value>]]
Changed lines 1-2 from:
to:
What Kind of Javascript Can I Use]?
Changed line 7 from:
Keep in mind when writing Javascript for custom actions that the code is executed when loaded (it's loaded when the button to run the action is clicked). So things like onload or jQuery $.ready() aren't necessary here.
to:
Keep in mind when writing Javascript for custom actions that the code is executed when loaded (it's loaded when the button to run the action is clicked). So things like onload or jQuery $.ready() aren't necessary here.
Changed lines 1-2 from:
What Kind of Javascript Can I Use?
to:
Changed line 15 from:
Here is the code for the post-to-Slack demo in the move above: dayBackSlack.js
to:
Here is the code for the post-to-Slack demo in the move above: dayBackSlack.js
Added lines 1-24:
What Kind of Javascript Can I Use?
Most everything. We don't allow access to the global window object but all built in functions for window can still be called directly. For example: open(), close(), alert(), location.href, can all be used as long as you don't use them in the context of window. In other words use location.href instead of window.location.href.
DayBack also includes a few popular libraries to make coding easier. jQuery, BootStrap, and moment.js are all included. So anything you can do in one of those libraries can be used in a custom action.
Keep in mind when writing Javascript for custom actions that the code is executed when loaded (it's loaded when the button to run the action is clicked). So things like onload or jQuery $.ready() aren't necessary here.
Custom Action Examples
Use the examples below as the starting point for your own actions.
Slack WebHook (Send A Message To Slack Group Chat)
Here is the code for the post-to-Slack demo in the move above: dayBackSlack.js
Harvest Time Tracker Widget
Show an in-line time tracker from your harvest account to start a timer related to this task. This is the time tracking widget we demo'ed at DevCon 2015 (movie here ). harvest.js
Parse And Open URL In Event
This looks through your event's description and will open the first URL it finds. openFirstUrl.js
|
