DriveWorks Pro 20

DriveApp Administration

DriveApp Administration

DriveApps are provided to add out of the box functionality to your current Group.

Available DriveApps include:

• Dashboard

  Set up links to websites, DriveWorks Projects, KPI's and other dashboards.

• CPQ (Fully released for DriveWorks v18.2)

  The Configure Price Quote DriveApp has been created to make it easy for manufacturing companies to quickly leverage the benefits of online selling.

• Scheduler

  Set up Jobs to be run by the Schedule Connector inside DriveWorks Autopilot.

Add

To Add a DriveApp:

1. Click the Add button from the command bar.
2. From the Add DriveApp wizard, select the DriveApp to add. Click Next.
3. Enter an alias for the DriveApp.

   Each DriveApp needs an alias. This is the name that will be shown to users.

   Multiple Instances of each DriveApp can be set up. Aliasing each DriveApp identifies each instance.
4. Select the Default Project.

   The Default Project is the entry point to the DriveApp for users. Depending on the DriveApp, this may be configurable.

   This could also become configurable once the DriveApp has been set up and initialized.
5. Enter the Start Parameter.

   The Start Parameter sets additional data for the DriveApp. Depending on the DriveApp, this may be configurable.

   Click Next.

   Some DriveApps may not require a database connection.

   If this applies to the chosen DriveApp:

   Click Finish

6. 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.

   Microsoft Azure

   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

   Click Next.

7. Select the Authentication method for the SQL Server.

   If using SQL Server Authentication, enter a valid User Name and Password.

8. Select an Existing or New Database to hold the data for the DriveApp.
   The DriveApp will create the database, schema and default data when the DriveApp is run for the first time.

   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.

   Click Finish.

When a DriveApp has been added, the options detailed below are available from the command bar or the DriveApp tile.

Edit

Click Edit to change the options applied when the DriveApp was added (as above).

Delete

Click Delete to remove the DriveApp.

Security

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:

• All teams can run the DriveApp

  This option should be selected if all current teams, and teams subsequently added, will have the ability to run the DriveApp.

• Custom

  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.

Enabled

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.

Upgrading a DriveApp

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.

Initializing a DriveApp

When a DriveApp has been added and enabled, a one time Initializing process is required.

Please see DriveApps for more information.