The script paramater is formatted as JSON. In this case, because you are communicating from the host to the workflow and from the workflow to the host, you need to define two service contracts and related data contracts, as shown in Figure 1. You need to call it with some JSON parameters of the details of the DDR to import. WCF services use contracts to define the collection of operations that make up the service and the messages that are sent and received. The script to call is called " Event: Import New DDR".
Then call a script in the BaseElements_Data file.
#BASEELEMENTS INSERT REGISTRATION#
If you're doing this for the first time, it will ask for registration details, so put these in and it will remember them for next time. So you should open the main BaseElements file and let it run it's opening script. When the copy is done, you could use Applescript or a Windows event to automatically import the DDR overnight and have it ready for the next day.įirst, you need to have BaseElements open. You can setup a FMP "Robot" machine and copy your DDR to that machine. This is useful if you have a large solution with long import times that you want to run regularly for example. Parameters for the script are in the form of name value pairs, separated by return characters.
You need to call this script with the correct parameters in order to start an import.
In the BaseElements_Data file, there is a script called "Event: Import New DDR". Once the solution is opened - by opening the main BE file - you can call a script to run the import automatically. We’re going to have a bunch of small additions to show off in BaseElements Next, but we have a couple of cool larger features I wanted to highlight. If you wanted to automate a BaseElements import that runs unattended, you can automate the imports by calling the appropriate script in the BE Data file. As always, we’re working on new versions of BaseElements and deciding on which new features to add.