Connecting DriveWorks to other business systems to communicate and share data seamlessly is essential for streamlining processes and improving efficiency.
Integrating DriveWorks with other applications offers many benefits, including:
DriveWorks utilizes the most modern and common methods to integrate with other applications.
In built functionality allows integration with security and email.
DriveWorks provides solutions for following methods of integration:
Direct connection between DriveWorks and other business systems.
With platforms that provide web services for sending and receiving data over the internet.
Using Application Programming Interfaces (APIs) to connect different systems.
Securing access to the data and rules behind an implementation and also who can create specifications is provided by the following integrations:
DriveWorks provides out-of-the-box functionality to create Users and Teams to control who can create and edit specifications, and administer an implementation.
Single sign-on (SSO) is an authentication method that allows one account manager to sign users in to multiple independent software systems. DriveWorks fully supports single sign-on for Microsoft Entra ID
DriveWorks supports sending emails using SMTP or Exchange Online using Oauth 2.0 authentication (Microsoft's recommended method).
Email integration is provided in the following areas:
Build rules for email recipients, the message body and attach any required file.
DriveWorks can automatically send notifications if any connected DriveWorks Autopilot agent unexpectedly disconnects.
DriveWorks Live can email alerts when the maximum number of licenses in use has been exceeded.
Direct connection between DriveWorks and the data held in other business systems.
The data can be held in any compatible database (SQL Server, MySQL, Oracle, etc.) or imported and exported from most common file types.
DriveWorks can read data natively from Microsoft SQL Server or from any other database with an ODBC driver.
The data can be anything from a single value to a whole database table.
Once in DriveWorks you can use rules to sort, filter and process the data further.
The following functions allow database data to be read into a project, when a specification is transitioned or when form inputs change:
Returns a list of data from a field, in a table of the database, by running a SQL query that compares values to a given term.
Returns an array of data from a table in a database by running a SQL query to filter, group and sort the data being queried.
Returns an array of data from a table of the database that matches the given term.
Database data can be imported as a table into a project to be used in rules:
Connect to a database to monitor for new entries to create new or edit existing specifications:
DriveWorks can write data natively to Microsoft SQL Server or to any other database with an ODBC driver.
The data can be inserted, updated or deleted based on rules.
To avoid bypassing the logic of the business system we recommend applying any export to a sub-set of the actual data.
The following function allows data created from a specification to be written to a database when a specification is transitioned or when form inputs change:
Will delete, insert or update rows in a database table and returns the number of affected rows.
The following document types can be used to export data to a database at a suitable point in the workflow of a specification.
They can also be set to run from a button on a user form.
DriveWorks can import data from a range of file formats.
Once imported, the files and the data within them can be used by DriveWorks.
Files can be imported at anytime during the workflow.
Some business systems may produce information that can be used to create a DriveWorks specification.
This can be brought into DriveWorks to populate form inputs:
DriveWorks Autopilot can read structured XML or Tab delimited file formats to convert into a specification.
Or
DriveWorks Autopilot can scan a folder for new XML or Tab delimited file formats to convert into a specification.
Data exported to a file such as, costing, bill of materials, customer and stock information can be read into DriveWorks to be used in rules.
Data can be loaded automatically, if the location of the file is known and is accessible, or up-loaded from a specification.
Read a Text File to import text-based data at a suitable point in the workflow of a specification (for example when a specification is started or when it transitions). It can also be set to run from a button on a user form.
Data stored in .txt format can be imported into a DriveWorks table, there are many table functions available to use the data once it has been imported.
Data stored in .txt and .csv formats can have values mapped to populate constants and controls in a specification.
Load XML data into a specification.
To assist with using the values in the XML file there are many functions available (for example XPathGet, XPathXMLGet).
Load JSON data when a specification is started or its arguments change.
To assist with using the values in the JSON file there are many functions available (for example XPathGet, XPathJsonGet).
DriveWorks provides many ways to import data created in Microsoft Excel, including:
DriveWorks can export data to most standard file types, including text based files as well as direct integration with Microsoft Word and Excel.
Build rules to determine the new file name and path, as well as the data that will be passed to the file.
Drive data into a text file which can be saved as any supported file type (.txt, .html, .xml, .csv, .md, etc.).
See Text Document for more information.
Export data directly into xml documents.
See XML Document for more information.
Generate functional, validated JSON Documents from any valid Schema.
See XML Document for more information.
Data can be driven into Microsoft Excel documents to create native .xlsx files.
Also create .pdf or .html versions of this format if required.
See Excel Workbook for more information.
Data can be driven into Microsoft Word documents to create native .docx files.
Also create .pdf or .html versions of this format if required.
See Word Document for more information.
DriveWorks can edit existing PDF files or create new PDF files from a markdown (.md) file.
See DriveWorks PDF Integration for more information.
DriveWorks integrates directly with SOLIDWORKS to provide a complete Design Automation solution.
Capture assemblies, parts and drawings to produce completely new and driven native SOLIDWORKS files.
Use DriveWorks to create additional file formats of the new files, including:
See SOLIDWORKS for more information.
Extend a Design Automation solution by integrating with popular CAM applications.
Use the SOLIDWORKS CAM or CAMWorks PowerPacks to perform the following:
DriveWorks provides functions and tasks to fully integrate with SOLIDWORKS PDM Professional.
Integrating with PDM allows the following:
DriveWorks can communicate with platforms that provide web services for sending and receiving data over the internet, and can also act as a web service itself.
DriveWorks can send web service requests using JSON for data exchange and relying on HTTP methods like GET, POST and ACCEPT.
This enables DriveWorks to communicate with any compatible web service (such as a CRM or ERP system, or any external web service provider) and allows real-time data to be surfaced directly into a Specification.
If using DriveWorks Live Integration Theme data can be passed from client to client directly.
For example a price calculated by DriveWorks can be sent to an eCommerce provider.
DriveWorks Live can function as a web service.
This allows other business systems to send data that will create or edit DriveWorks specifications automatically.
The Integration Theme supports this by using a URL command function.
When communicating data over a web service, cryptography helps protect data from being viewed, provides ways to detect whether data has been modified, and helps provide a secure means of communication over otherwise nonsecure channels.
DriveWorks provides functions for the most secure hashing algorithms, including support for Hash-based Message Authentication Code (HMAC):
Using Application Programming Interfaces (APIs) to connect different systems.
DriveWorks Pro has been built with a fully documented Application Programming Interface (API) that allows the creation of custom plugins to further integrate DriveWorks.
The Integration Theme utilizes modern web technologies to allow aspects of a DriveWorks Implementation to be easily consumed in a website, application or connected device.
Each instance of the Integration Theme serves a complete Web API, with examples and documentation to help with getting started.
DriveWorks provides and supports PowerPacks which provide additional integration functionality for specific applications.
Learn about the PowerPacks available to integrate with CAM, PDM, CRM, ERP and Cloud applications.
Also learn more about how DriveWorks can provide further integrations with the following: