SmarTeam Workflow’s API engine offers tremendous flexibility for manipulating processes on-the-fly. The object model, and the combination of nodes, users, and events make it easy to perform fairly advanced operations with workflow. As an example, let’s use the API to dynamically assign a user to a node based on their participation earlier in the workflow. We’ll use BasicScript and C#.NET to write the code (directions for getting the source code below), and cover some of the important details of how to apply the customization in ENOVIA SmarTeam.
SolidWorks’ Enterprise PDM (EPDM) system contains what some might call a “poor man’s API” known as the Dispatch Tool. The Dispatch Tool allows non-programmers (those who don’t write formal code in Visual Studio.NET) to create basic programs, scripts, and functions within EPDM without having to learn a programming language. The tool is limited in functionality of course and is a procedural language, but it does provide a lot of ways to manipulate data inside EPDM. This article highlights the capabilities of the Dispatch Tool through an example that renames a file with the information contained on the file’s Data Card. Sample code for this example is provided.
With every upgrade to ENOVIA SmarTeam (not to mention upgrades to CAD, Office and database platforms) there’s no question about the benefits of building a test environment for validation prior to a production roll-out. An important piece of building a test environment is a properly configured test vault. Quite often, a successful test doesn’t require a complete copy of the entire production vault, so let’s take a look at a simple process to copy specific files from a production system to a test environment on demand.
Design automation tools like DriveWorks provide functionality to read information from a database and to output information to a database. One of the most common tasks for database output is the automation of part numbers and quotation numbers. Although the task seems trivial, there is more to it than meets the eye. Fortunately, the combination of VBA macros, SQL stored procedures, and SQL triggers are great for automating the process.
Workflow processes in Aras Innovator can have their own metadata (in addition to tasks, voting details, an electronic signature, and the metadata of routed content). This workflow-specific metadata is in the form of activity variables, which can be defined by the administrator on a per-process-type basis. Aras Innovator workflow activity variables can be used for dynamic user assignment (to workflows), for updating protected/read-only fields, and for many other needs. In this post, we’ll show how to use an activity variable to update a read-only (protected) field, and even share the source code needed to enable this.