The following section contains answers to some frequently asked questions about using Test Drives with Google Cloud Marketplace and Orbitera. For overview information about Test Drives, see Build a Test Drive.
How do I integrate a CRM leads registry with the Orbitera signups?
If your CRM allows you to create a custom form for leads registration with field names and an URL, then you can follow the instructions described at Accelerate Sales by Linking Orbitera to your CRM and Marketing Automation Systems in the Orbitera blog or use the instructions available at the Orbitera configuration guide.
You can also use the Callbacks API to send your custom POST request to a third party component: a custom microservice you built or a tool already offering an integration with your CRM (like Zapier).
Please read more on extending the Orbitera with the Callbacks API at the Orbitera blog.
How do I keep the costs of Test Drive deployments under control?
To control the costs associated with your Test Drives, go to the Test Drive configuration screen (Test Drives > select a Test Drive > Edit). There, you can define deployments constraints. Constraints include:
- Concurrent Instances Limit: the number of deployments available at the same time.
- Launch Limit per Customer: the number of deployments that can be run for a single customer's account (the next deployment can be started after the previous one has finished)
- Duration: the time after which the deployment is automatically deleted.
For more information, you might also check the Restrictions section.
Remember to approprietly configure the Quotas on your GCP project for your Test Drive, as described in Build a Test Drive, Infrastructure and Cost.
How do I customize the emails sent to my customers?
Any email that is sent to your customers in the process of running a Test Drive is customizable. To list all the templates available for Test Drives, go to Settings > Email templates in the Orbitera portal, then filter the list by putting the phrase testdrives in the search field at the top of the page.
Double-click an element in the list to enter the customization form for its template.
How do I integrate 3rd party components (like external servers) with a Test Drive deployment?
Sometimes you may find it necessary to notify external components that a new instance of the Test Drive was created. It might include creating additional, per-deployment account in a SaaS part of the solution or creating a proper configuration for a component shared across multiple Test Drive instances.
In this case, using a startup script of a VM instance is usually the easiest
way to trigger an action. Calling a proper API with a
curl command and passing
the right data, covers most situations. In more complex environments you might
consider writing your own application handling the integration scenarios and
run it through a startup script.
Sometimes it is also required to notify a third party component about finalizing the Test Drive instance (triggered by the customer or caused by a preconfigured timeout). For such situations, Orbitera offers a Shut Down Callback feature. From the Test Drive configuration screen (Test Drives > select an element from the list > Edit), scroll to the Shut Down Callback section. To notify an external component about the finished deployment, in the URL field, enter the URL for the HTTP GET call. You can use placeholders for parameter values, such as the server's IP address.
How do I allow a Test Drive user to define custom properties for the deployment?
Any custom value for a property of a top-level Deployment Manager script can be populated from the Orbitera framework. To populate the value, select the entry file of the deployment that requires additional properties. The list of properties will show up with names, input fields for entering the value, and checkboxes to make the property configurable for a user.
Value can be defined with supported placeholders or just as static text. You can also select which of those parameters should be configurable for a Test Drive user; only those parameters which have the Public checkbox checked, will be visible and updatable for end users.