DriveApps are provided to add out of the box functionality to your current Group.
Available DriveApps include:
Set up links to websites, DriveWorks Projects, KPI's and other dashboards.
The Configure Price Quote DriveApp has been created to make it easy for manufacturing companies to quickly leverage the benefits of online selling.
Set up Jobs to be run by the Schedule Connector inside DriveWorks Autopilot.
To Add a DriveApp:
Each DriveApp needs an alias. This is the name that will be shown to users.
The Default Project is the entry point to the DriveApp for users. Depending on the DriveApp, this may be configurable.
The Start Parameter sets additional data for the DriveApp. Depending on the DriveApp, this may be configurable.
If this applies to the chosen DriveApp:
Select the Microsoft SQL Server where the DriveApp data is to be located.
If connecting to Azure enter the Azure connection string in the Location field.
DriveWorks v20 SP2 onwards support DriveApps being provisioned on an Azure database.
However, we have found Azure will default to a database that is over-provisioned and expensive to run.
We recommend you review the costs of the vCore purchasing model and select the model that matches your requirements.
We recommend switching this to the DTU based purchasing model, 10 DTU's is perfectly suitable for most scenarios
Select the Authentication method for the SQL Server.
If using SQL Server Authentication, enter a valid User Name and Password.
Multiple DriveApps can share the same SQL Server and database if required.
When multiple DriveApps share the same database, any customization settings will apply to all DriveApps in the database.
When a DriveApp has been added, the options detailed below are available from the command bar or the DriveApp tile.
Click Edit to change the options applied when the DriveApp was added (as above).
Click Delete to remove the DriveApp.
The database and data will not be removed.
Adding the DriveApp back and attaching to the same database will restore all data.
To delete the database, use SQL Management Studio.
Click Security to select the Teams that will have the ability to run the DriveApp.
Teams are created in Security Settings.
The DriveApp Team Security dialog has two options:
This option should be selected if all current teams, and teams subsequently added, will have the ability to run the DriveApp.
This option should be selected to choose the teams with the ability to run the DriveApp.
Teams subsequently added will not have access to run the DriveApp.
Click Enabled from the command bar, or Enable from the DriveApp tile to enable the DriveApp.
DriveApps must be enabled for them to be seen and run from the DriveApps task.
When DriveWorks has been upgraded from an earlier version, the DriveApp may require upgrading.
If this is the case, the Enabled button will change to Upgrade.
See Upgrading a DriveApp below.
When a DriveApp requires upgrading the tile will display an Upgrade button.
Click this to upgrade the DriveApp.
Once the upgrade is complete the DriveApp can be enabled.
Each DriveApp may also require the database to be upgraded, please see Upgraded DriveApps for more information.
When a DriveApp has been added and enabled, a one time Initializing process is required.
Please see DriveApps for more information.