Perform Script on Server (PSOS)
DayBackForFileMaker.PSOS History
Hide minor edits - Show changes to output
Changed line 11 from:
''Note: This may be obvious, but PSOS will only work when your file is hosted in FileMaker Server 13.''
to:
''Note: This may be obvious, but PSOS will only work when your file is hosted in FileMaker Server 13+.''
May 26, 2017, at 09:53 PM
by - Updated #FMCloud to point to build instructions
Changed lines 36-42 from:
DayBack has a script that runs before enabling PSOS which verifies you are running FileMaker Server. In older versions of DayBack, the method we used to check for this did not return True when using FileMaker Cloud. If PSOS is not enabling and your server is on FileMaker Cloud, either update to the latest DayBack, or replace the calculation in the "Can Run On Server" script with the following:
->$$sc_PSOS and Perform Script on Server
->PatternCount ( Get ( HostApplicationVersion ) ; "Server" ) = 1 ->and
->GetAsNumber( Get(HostApplicationVersion) ) >= 13 and
->PatternCount ( Get ( ApplicationVersion ) ; "Server" ) = 0 and
->GetAsNumber( Get(ApplicationVersion) ) >= 13
->$$sc_PSOS and
->PatternCount ( Get ( HostApplicationVersion ) ; "Server" ) = 1 ->and
->GetAsNumber( Get(HostApplicationVersion) ) >= 13 and
->PatternCount ( Get ( ApplicationVersion ) ; "Server" ) = 0 and
->GetAsNumber( Get(ApplicationVersion) ) >= 13
to:
DayBack has a script that runs before enabling PSOS which verifies you are running FileMaker Server. In older versions of DayBack, the method we used to check for this did not return True when using FileMaker Cloud. If PSOS is not enabling and your server is on FileMaker Cloud, either update to the latest DayBack, or apply the specific change as described in [[https://www.seedcode.com/support/viewtopic.php?f=40&t=4348|this support article]].
May 26, 2017, at 09:39 PM
by - Added #FMCloud section regarding the PSOS check
Changed lines 31-41 from:
-> End If
to:
-> End If
[[#FMCloud]]
!!FileMaker Cloud
DayBack has a script that runs before enabling PSOS which verifies you are running FileMaker Server. In older versions of DayBack, the method we used to check for this did not return True when using FileMaker Cloud. If PSOS is not enabling and your server is on FileMaker Cloud, either update to the latest DayBack, or replace the calculation in the "Can Run On Server" script with the following:
->$$sc_PSOS and // Perform Script on Server
->PatternCount ( Get ( HostApplicationVersion ) ; "Server" ) = 1 ->and
->GetAsNumber( Get(HostApplicationVersion) ) >= 13 and
->PatternCount ( Get ( ApplicationVersion ) ; "Server" ) = 0 and
->GetAsNumber( Get(ApplicationVersion) ) >= 13
[[#FMCloud]]
!!FileMaker Cloud
DayBack has a script that runs before enabling PSOS which verifies you are running FileMaker Server. In older versions of DayBack, the method we used to check for this did not return True when using FileMaker Cloud. If PSOS is not enabling and your server is on FileMaker Cloud, either update to the latest DayBack, or replace the calculation in the "Can Run On Server" script with the following:
->$$sc_PSOS and // Perform Script on Server
->PatternCount ( Get ( HostApplicationVersion ) ; "Server" ) = 1 ->and
->GetAsNumber( Get(HostApplicationVersion) ) >= 13 and
->PatternCount ( Get ( ApplicationVersion ) ; "Server" ) = 0 and
->GetAsNumber( Get(ApplicationVersion) ) >= 13
Changed line 29 from:
-> If [PatternCount ( Get ( ApplicationVersion ) ; "Server" )]
to:
-> If [PatternCount ( Get ( HostApplicationVersion ) ; "Server" )]
Changed line 23 from:
Thus, PSOS is a "switch" in DayBack. You can turn this on from the calendars's settings tab or turn it on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
to:
Thus, PSOS is a "switch" in DayBack. You can turn this on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
Added lines 24-31:
!! Caution
If you've linked or embedded the calendar into your file check that your file's start up script bails out when run on FileMaker Server. Each PSOS script initiated runs the start up script in any required files and that can really slow things down. Feel free to use the same routine used as the first lines of DayBack's "Upon Opening" script:
-> If [PatternCount ( Get ( ApplicationVersion ) ; "Server" )]
-> Exit Script []
-> End If
Changed lines 3-10 from:
!! Why would I want to use PSOS?
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times '''10-40 times faster''' when using PSOS on a WAN (your mileage may vary
to:
!! Why Would I Want to Use PSOS?
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can have the server do a lot of the heavy lifting the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.). More interestingly, you can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file.
Using PSOS can result in '''dramatic''' performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network).
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can have the server do a lot of the heavy lifting the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.). More interestingly, you can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file.
Using PSOS can result in '''dramatic''' performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network).
Changed lines 15-16 from:
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. But it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
to:
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server (when there is a lot of latency in your connection to the server). But it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
Changed lines 23-73 from:
!! Adding PSOS to your Calendar file
If you want to add this PSOS functionality into a SeedCode calendar you already have, you can... following these instructions.
First, %newwin% [[https://sites.fastspring.com/seedcode/product/seedcodecalendarproupgradetositelicensefrompro?action=adds | upgrade to the new calendar]]. And you'll need FileMaker Advanced so you can add custom functions and copy/paste script steps from that file: then follow these instructions:
1. Import these three custom functions into your file:
''(yes, that �#� sign is the full name of the first one)''
-> #
-> #Assign
-> #AssignGlobal
2. Copy/paste the new "Check for FileMaker Server" script into your file.
3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using Select All and Copy/Paste:
''(NOTE: do not delete the scripts themselves; only the contents)''
-> Insert Events File Into Calendar
-> Cast Events as Variables - Build Query
-> Capture Events by Date Range - Run SQL Query
-> Upon Opening
-> Toggle PSOS (added in [[version history | version]] 7.25)
-> Clear Event Parsing Variables
-> Click in / Drag Event
-> Load Calendar Graphics
''(NOTE: those last three scripts are unrelated to PSOS, but updating them will fix some minor bugs we found.)''
4. You'll also have to edit the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. If you haven't modified any of the settings in this script in your file, then you can just copy/paste the entire contents from the new file into yours (like you did with the other scripts above). However, if you have modified your settings, you'll want to selectively copy/paste these new steps:
-> Set Variable [$$sc_PSOS; Value:"No"...]
-> Set Variable [$$sc_SortEvents; Value:"Yes"...]
-> The entire If[] section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", then rerun the "Upon Opening" script.
That's it, enjoy!
!! I'm Getting a Notification Dialog saying PSOS isn't available?
We thought developers would like to know about those cases where they'e set the calendar to use PSOS but it won't be used: such as when the calendar is opened shared from FileMaker Pro instead of FileMaker Server.
To get rid of this dialog simply delete the first Show Custom Dialog step in the script "Cast Events as Variables - Build Query" after the comment "Script is running on the server (PSOS)."
to:
Thus, PSOS is a "switch" in DayBack. You can turn this on from the calendars's settings tab or turn it on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
Changed line 3 from:
''Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our [[version history]] for more.''
to:
''Note: The PSOS option is included in SeedCode calendar version 7.25 (a paid upgrade from earlier versions). Check out our [[version history]] for more.''
Changed line 23 from:
-> With PSOS on, it only takes 20 seconds to go from month to month... but it always takes 20 seconds. Going back to a previously visited month is no faster than going to a new month.
to:
-> With PSOS on, it only takes 5 seconds to go from month to month... but it always takes 5 seconds. Going back to a previously visited month is no faster than going to a new month.
Changed line 9 from:
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times '''10-20 times faster''' when using PSOS on a WAN (your mileage may vary).
to:
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times '''10-40 times faster''' when using PSOS on a WAN (your mileage may vary).
Changed lines 15-17 from:
!! Why wouldn't I want PSOS on all the time?
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. And it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. And
to:
!! Why wouldn't everyone want PSOS on?
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. But it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. But it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
Changed lines 3-4 from:
''Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our [[version history]] for more.
to:
''Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our [[version history]] for more.''
Changed lines 3-4 from:
Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our [[version history]] for more.
to:
''Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our [[version history]] for more.
''
''
Added lines 15-26:
!! Why wouldn't I want PSOS on all the time?
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. And it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
Here is an exaggerated example:
-> Without PSOS opening your calendar from another country takes 9 minutes to move from month to month. But once you've been to a given month, going back to that month takes only a couple seconds.
-> With PSOS on, it only takes 20 seconds to go from month to month... but it always takes 20 seconds. Going back to a previously visited month is no faster than going to a new month.
Thus, PSOS is a "switch" in the Pro Calendar. You can turn this on from the calendars's settings tab or turn it on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. And it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
Here is an exaggerated example:
-> Without PSOS opening your calendar from another country takes 9 minutes to move from month to month. But once you've been to a given month, going back to that month takes only a couple seconds.
-> With PSOS on, it only takes 20 seconds to go from month to month... but it always takes 20 seconds. Going back to a previously visited month is no faster than going to a new month.
Thus, PSOS is a "switch" in the Pro Calendar. You can turn this on from the calendars's settings tab or turn it on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
Changed line 75 from:
To get rid of this dialog simply delete the first Show Custom Dialog step in the script "Cast Events as Variables - Build Query" after the comment "Script is running on the server (PSOS)."
to:
To get rid of this dialog simply delete the first Show Custom Dialog step in the script "Cast Events as Variables - Build Query" after the comment "Script is running on the server (PSOS)."
Changed line 39 from:
-> Toggle PSOS (added in [[version]] 7.25)
to:
-> Toggle PSOS (added in [[version history | version]] 7.25)
Changed line 9 from:
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS on a WAN (your mileage may vary).
to:
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times '''10-20 times faster''' when using PSOS on a WAN (your mileage may vary).
Changed lines 57-63 from:
That's it, enjoy!
to:
That's it, enjoy!
!! I'm Getting a Notification Dialog saying PSOS isn't available?
We thought developers would like to know about those cases where they'e set the calendar to use PSOS but it won't be used: such as when the calendar is opened shared from FileMaker Pro instead of FileMaker Server.
To get rid of this dialog simply delete the first Show Custom Dialog step in the script "Cast Events as Variables - Build Query" after the comment "Script is running on the server (PSOS)."
!! I'm Getting a Notification Dialog saying PSOS isn't available?
We thought developers would like to know about those cases where they'e set the calendar to use PSOS but it won't be used: such as when the calendar is opened shared from FileMaker Pro instead of FileMaker Server.
To get rid of this dialog simply delete the first Show Custom Dialog step in the script "Cast Events as Variables - Build Query" after the comment "Script is running on the server (PSOS)."
Changed lines 3-4 from:
Note: The PSOS option will be included in SeedCode's [[https://www.seedcode.com/preview-seedcode-calendar-web-direct/ | Calendar for Web Direct]], which is almost ready. [[https://www.seedcode.com/newsletter-signup/ | Signup for our newsletter]] to be the first to know when it's released.
to:
Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our [[version history]] for more.
Changed lines 9-10 from:
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (over the internet). Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS on a WAN (your mileage may vary). You might not see any improvement on a LAN (on the local network).
to:
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS on a WAN (your mileage may vary).
You'll likely not see any improvement on a LAN (when you're ON the local network).
You'll likely not see any improvement on a LAN (when you're ON the local network).
Changed lines 17-19 from:
If you want to add this PSOS functionality into your calendar file, you'll need FileMaker Advanced so you can add custom functions and copy/paste script steps. %newwin% [[https://www.seedcode.com/cp-app/contact/1 | Ask us for the latest build]], then follow these instructions:
to:
If you want to add this PSOS functionality into a SeedCode calendar you already have, you can... following these instructions.
First, %newwin% [[https://sites.fastspring.com/seedcode/product/seedcodecalendarproupgradetositelicensefrompro?action=adds | upgrade to the new calendar]]. And you'll need FileMaker Advanced so you can add custom functions and copy/paste script steps from that file: then follow these instructions:
First, %newwin% [[https://sites.fastspring.com/seedcode/product/seedcodecalendarproupgradetositelicensefrompro?action=adds | upgrade to the new calendar]]. And you'll need FileMaker Advanced so you can add custom functions and copy/paste script steps from that file: then follow these instructions:
Changed lines 44-49 from:
-> @@Set Variable [$$sc_PSOS; Value:"No"...]@@
-> @@Set Variable [$$sc_SortEvents; Value:"Yes"...]@@
-> The entire @@If[]@@ section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes",the rerun the "Upon Opening" script.
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes",
to:
-> Set Variable [$$sc_PSOS; Value:"No"...]
-> Set Variable [$$sc_SortEvents; Value:"Yes"...]
-> The entire If[] section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", then rerun the "Upon Opening" script.
-> Set Variable [$$sc_SortEvents; Value:"Yes"...]
-> The entire If[] section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", then rerun the "Upon Opening" script.
Changed lines 44-49 from:
-> Set Variable [$$sc_PSOS;
"If[]" section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
5.There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
5.
to:
-> @@Set Variable [$$sc_PSOS; Value:"No"...]@@
-> @@Set Variable [$$sc_SortEvents; Value:"Yes"...]@@
-> The entire @@If[]@@ section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
-> @@Set Variable [$$sc_SortEvents; Value:"Yes"...]@@
-> The entire @@If[]@@ section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
Changed lines 42-43 from:
4. You'll also have to edit the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. If you haven't modified any of the settings in this script in your file, then you can just copy/paste the entire contents from the new file into yours. If you have modified your settings, you'll want to selectively copy/paste these new steps:
to:
4. You'll also have to edit the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. If you haven't modified any of the settings in this script in your file, then you can just copy/paste the entire contents from the new file into yours (like you did with the other scripts above). However, if you have modified your settings, you'll want to selectively copy/paste these new steps:
Changed line 49 from:
to:
5. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
Changed lines 7-8 from:
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.) to the server. You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
to:
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can have the server do a lot of the heavy lifting the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.). You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file.
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (over the internet). Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS on a WAN (your mileage may vary). You might not see any improvement on a LAN (on the local network).
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (over the internet). Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS on a WAN (your mileage may vary). You might not see any improvement on a LAN (on the local network).
Added lines 40-46:
4. You'll also have to edit the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. If you haven't modified any of the settings in this script in your file, then you can just copy/paste the entire contents from the new file into yours. If you have modified your settings, you'll want to selectively copy/paste these new steps:
-> Set Variable [$$sc_PSOS; ...]
-> Set Variable [$$sc_SortEvents; ...]
-> The entire "If[]" section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
Deleted line 15:
Deleted line 26:
Changed line 40 from:
4. ->There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
to:
4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
Changed line 42 from:
to:
4. ->There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
Changed lines 15-16 from:
to:
1. Import these three custom functions into your file:
Changed lines 27-28 from:
to:
3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using Select All and Copy/Paste:
Changed line 42 from:
to:
<4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
Changed line 42 from:
4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with yourfile being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
to:
-<4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
Changed lines 24-26 from:
to:
2. Copy/paste the new "Check for FileMaker Server" script into your file.
Changed line 42 from:
to:
4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with yourfile being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
Added lines 40-42:
'''4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with yourfile being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.'''
Changed line 27 from:
'''3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using copy/paste:'''
to:
'''3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using Select All and Copy/Paste:'''
Changed lines 24-30 from:
'''2. Copy/paste these five new scripts into your file:'''
-> FileMaker Find
-> FileMaker Find - Apply Filters ( SourceNo )
-> Check for FileMaker Server
-> Sort FileMaker Records --- Edit Sort Orders Here ---
-> Sort FileMaker Records for Gantt Chart --- Edit Sort Orders Here �
-> FileMaker Find
-> FileMaker Find - Apply Filters ( SourceNo )
-> Check for FileMaker Server
-> Sort FileMaker Records --- Edit Sort Orders Here ---
-> Sort FileMaker Records for Gantt Chart --- Edit Sort Orders Here �
to:
'''2. Copy/paste the new "Check for FileMaker Server" script into your file.'''
Changed line 45 from:
''(NOTE: those last three scripts are unrelated to PSOS, but updating them will fix a couple of minor bugs.)''
to:
''(NOTE: those last three scripts are unrelated to PSOS, but updating them will fix some minor bugs we found.)''
Changed lines 23-26 from:
'''2. Create a new layout named "Calendar - Web Viewer", and associate it with the CalendarInterface table'''
'''3. Copy/paste these five new scripts into your file:'''
'''3
to:
'''2. Copy/paste these five new scripts into your file:'''
Changed lines 32-35 from:
'''4. Replace the entire contents (all steps) of these eight scripts in your file with the contents of these scripts from the new file using copy/paste:'''
''(note: do not delete the scripts themselves; only the contents)''
''(
to:
'''3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using copy/paste:'''
''(NOTE: do not delete the scripts themselves; only the contents)''
Deleted line 39:
Added lines 44-46:
''(NOTE: those last three scripts are unrelated to PSOS, but updating them will fix a couple of minor bugs.)''
Changed lines 15-16 from:
'''1. Import these custom functions into your file:'''
to:
'''1. Import these three custom functions into your file:'''
Changed lines 25-26 from:
'''3. Copy/paste these new scripts into your file:'''
to:
'''3. Copy/paste these five new scripts into your file:'''
Changed line 33 from:
'''4. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste:'''
to:
'''4. Replace the entire contents (all steps) of these eight scripts in your file with the contents of these scripts from the new file using copy/paste:'''
Changed line 23 from:
'''2. Create a new layout associated with the CalendarInterface table, named "Calendar - Web Viewer":'''
to:
'''2. Create a new layout named "Calendar - Web Viewer", and associate it with the CalendarInterface table'''
Changed lines 23-24 from:
'''2. Copy/paste these new scripts into your file:'''
to:
'''2. Create a new layout associated with the CalendarInterface table, named "Calendar - Web Viewer":'''
'''3. Copy/paste these new scripts into your file:'''
'''3. Copy/paste these new scripts into your file:'''
Changed line 33 from:
'''3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste:'''
to:
'''4. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste:'''
Changed line 13 from:
If you want to add this PSOS functionality into your calendar file, %newwin% [[https://www.seedcode.com/cp-app/contact/1 | ask us]] for the latest build, then follow these instructions:
to:
If you want to add this PSOS functionality into your calendar file, you'll need FileMaker Advanced so you can add custom functions and copy/paste script steps. %newwin% [[https://www.seedcode.com/cp-app/contact/1 | Ask us for the latest build]], then follow these instructions:
Changed line 9 from:
''Note: This may seem obvious, but PSOS will only work when your file is hosted in FileMaker Server 13.''
to:
''Note: This may be obvious, but PSOS will only work when your file is hosted in FileMaker Server 13.''
Changed line 9 from:
''Note: This may seem obvious, but we'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.''
to:
''Note: This may seem obvious, but PSOS will only work when your file is hosted in FileMaker Server 13.''
Changed line 7 from:
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.) to the server. You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
to:
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.) to the server. You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
Changed line 7 from:
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
to:
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.) to the server. You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
Changed line 7 from:
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster using PSOS than without it.
to:
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
Changed line 7 from:
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script ''on the server''. That means you can have the server can do a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and you can avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster with PSOS than without it.
to:
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script ''on the server''. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster using PSOS than without it.
Changed line 7 from:
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script ''on the server''. That means you can have the server can do a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and you can avoid having to move large amounts of data over the network, which is what normally happens when a client machine runs a Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster with PSOS than without it.
to:
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script ''on the server''. That means you can have the server can do a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and you can avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster with PSOS than without it.
Changed line 7 from:
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script ''on the server'', which means the server does all of the heavy lifting (processing, data manipulation, etc.). This can result in dramatic performance improvements for certain operations. Our tests showed that using PSOS in the Pro Calendar results in refresh times 20-40 times faster than without it.
to:
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script ''on the server''. That means you can have the server can do a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and you can avoid having to move large amounts of data over the network, which is what normally happens when a client machine runs a Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster with PSOS than without it.
Changed line 13 from:
If you want to make these changes in your calendar file, %newwin% [[https://www.seedcode.com/cp-app/contact/1 | ask us]] for the latest build, then follow these instructions:
to:
If you want to add this PSOS functionality into your calendar file, %newwin% [[https://www.seedcode.com/cp-app/contact/1 | ask us]] for the latest build, then follow these instructions:
Changed line 13 from:
If you want to make these changes in your copy of the calendar, %newwin% [[https://www.seedcode.com/cp-app/contact/1 | ask us]] for a copy of the latest build, then follow these instructions:
to:
If you want to make these changes in your calendar file, %newwin% [[https://www.seedcode.com/cp-app/contact/1 | ask us]] for the latest build, then follow these instructions:
Added lines 12-13:
If you want to make these changes in your copy of the calendar, %newwin% [[https://www.seedcode.com/cp-app/contact/1 | ask us]] for a copy of the latest build, then follow these instructions:
Changed line 9 from:
''Note: This may seem obvious, but I'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.''
to:
''Note: This may seem obvious, but we'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.''
Changed lines 7-9 from:
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script ''on the server'', which means the server does all of the heavy lifting (processing, data manipulation, etc.). This can result in dramatic performance improvements for certain operations. Our tests showed that using PSOS in the Pro Calendar results in refresh times 20-40 time faster than without it. This may seem obvious, but I'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.
to:
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script ''on the server'', which means the server does all of the heavy lifting (processing, data manipulation, etc.). This can result in dramatic performance improvements for certain operations. Our tests showed that using PSOS in the Pro Calendar results in refresh times 20-40 times faster than without it.
''Note: This may seem obvious, but I'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.''
''Note: This may seem obvious, but I'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.''
Changed line 3 from:
Note: The PSOS options will be included in SeedCode's [[https://www.seedcode.com/preview-seedcode-calendar-web-direct/ | Calendar for Web Direct]], which is almost ready. [[https://www.seedcode.com/newsletter-signup/ | Signup for our newsletter]] to be the first to know when it's released.
to:
Note: The PSOS option will be included in SeedCode's [[https://www.seedcode.com/preview-seedcode-calendar-web-direct/ | Calendar for Web Direct]], which is almost ready. [[https://www.seedcode.com/newsletter-signup/ | Signup for our newsletter]] to be the first to know when it's released.
Changed line 5 from:
!! Why would I want to PSOS?
to:
!! Why would I want to use PSOS?
Added lines 4-7:
!! Why would I want to PSOS?
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script ''on the server'', which means the server does all of the heavy lifting (processing, data manipulation, etc.). This can result in dramatic performance improvements for certain operations. Our tests showed that using PSOS in the Pro Calendar results in refresh times 20-40 time faster than without it. This may seem obvious, but I'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.
Changed lines 7-9 from:
'''1. Import these custom functions into your file'''
''(yes, that �#� sign is the full name of the first one)'':
to:
'''1. Import these custom functions into your file:'''
''(yes, that �#� sign is the full name of the first one)''
''(yes, that �#� sign is the full name of the first one)''
Changed lines 14-15 from:
'''2. Copy/paste these new scripts into your file''':
to:
'''2. Copy/paste these new scripts into your file:'''
Changed line 22 from:
'''3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste''':
to:
'''3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste:'''
Changed lines 7-8 from:
'''1. Import these custom functions into your file''' (yes, that �#� sign is the full name of the first one):
to:
'''1. Import these custom functions into your file'''
''(yes, that �#� sign is the full name of the first one)'':
''(yes, that �#� sign is the full name of the first one)'':
Changed lines 22-23 from:
'''3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste ''(note: do not delete the scripts themselves; only the contents)''''':
to:
'''3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste''':
''(note: do not delete the scripts themselves; only the contents)''
''(note: do not delete the scripts themselves; only the contents)''
Changed lines 7-8 from:
1. Import these custom functions into your file (yes, that �#� sign is the full name of the first one):
to:
'''1. Import these custom functions into your file''' (yes, that �#� sign is the full name of the first one):
Changed lines 13-14 from:
2. Copy/paste these new scripts into your file:
to:
'''2. Copy/paste these new scripts into your file''':
Changed line 21 from:
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste ''(note: do not delete the scripts themselves; only the contents)'':
to:
'''3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste ''(note: do not delete the scripts themselves; only the contents)''''':
Changed line 3 from:
to:
Note: The PSOS options will be included in SeedCode's [[https://www.seedcode.com/preview-seedcode-calendar-web-direct/ | Calendar for Web Direct]], which is almost ready. [[https://www.seedcode.com/newsletter-signup/ | Signup for our newsletter]] to be the first to know when it's released.
Changed lines 1-5 from:
to:
(:title Perform Script on Server (PSOS):)
!! Adding PSOS to your Calendar file
!! Adding PSOS to your Calendar file
Changed lines 3-4 from:
to:
1. Import these custom functions into your file (yes, that �#� sign is the full name of the first one):
Changed lines 9-10 from:
Copy/paste these new scripts into your file:
to:
2. Copy/paste these new scripts into your file:
Changed line 17 from:
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste ''(note: do not delete the scripts themselves; only the contents)'':
to:
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste ''(note: do not delete the scripts themselves; only the contents)'':
Changed lines 5-7 from:
"
"
to:
-> #
-> #Assign
-> #AssignGlobal
-> #Assign
-> #AssignGlobal
Added lines 1-2:
!! Perform Script on Server (PSOS)
Changed lines 4-7 from:
#
to:
"#"
"#Assign"
"#AssignGlobal"
Changed lines 10-24 from:
FileMaker Find
FileMaker Find - Apply Filters ( SourceNo )
Check for FileMaker Server
Sort FileMaker Records --- Edit Sort Orders Here ---
Sort FileMaker Records for Gantt Chart --- Edit Sort Orders Here �
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
Insert Events File Into Calendar
Cast Events as Variables - Build Query
Capture Events by Date Range - Run SQL Query
Go to Calendar Layout
Upon Opening
Clear Event Parsing Variables
Click in / Drag Event
Load Calendar Graphics
FileMaker Find - Apply Filters ( SourceNo )
Check for FileMaker Server
Sort FileMaker Records --- Edit Sort Orders Here ---
Sort FileMaker Records for Gantt Chart --- Edit Sort Orders Here �
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
Insert Events File Into Calendar
Cast Events as Variables - Build Query
Capture Events by Date Range - Run SQL Query
Go to Calendar Layout
Upon Opening
Clear Event Parsing Variables
Click in / Drag Event
Load Calendar Graphics
to:
-> FileMaker Find
-> FileMaker Find - Apply Filters ( SourceNo )
-> Check for FileMaker Server
-> Sort FileMaker Records --- Edit Sort Orders Here ---
-> Sort FileMaker Records for Gantt Chart --- Edit Sort Orders Here �
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste ''(note: do not delete the scripts themselves; only the contents)'':
-> Insert Events File Into Calendar
-> Cast Events as Variables - Build Query
-> Capture Events by Date Range - Run SQL Query
-> Go to Calendar Layout
-> Upon Opening
-> Clear Event Parsing Variables
-> Click in / Drag Event
-> Load Calendar Graphics
Added lines 1-21:
First, import these custom functions into your file (yes, that �#� sign is the full name of the first one):
#
#Assign
#AssignGlobal
Copy/paste these new scripts into your file:
FileMaker Find
FileMaker Find - Apply Filters ( SourceNo )
Check for FileMaker Server
Sort FileMaker Records --- Edit Sort Orders Here ---
Sort FileMaker Records for Gantt Chart --- Edit Sort Orders Here �
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
Insert Events File Into Calendar
Cast Events as Variables - Build Query
Capture Events by Date Range - Run SQL Query
Go to Calendar Layout
Upon Opening
Clear Event Parsing Variables
Click in / Drag Event
Load Calendar Graphics
#
#Assign
#AssignGlobal
Copy/paste these new scripts into your file:
FileMaker Find
FileMaker Find - Apply Filters ( SourceNo )
Check for FileMaker Server
Sort FileMaker Records --- Edit Sort Orders Here ---
Sort FileMaker Records for Gantt Chart --- Edit Sort Orders Here �
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
Insert Events File Into Calendar
Cast Events as Variables - Build Query
Capture Events by Date Range - Run SQL Query
Go to Calendar Layout
Upon Opening
Clear Event Parsing Variables
Click in / Drag Event
Load Calendar Graphics
