Versions Compared
Version | Old Version 1 | New Version 2 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
This his tutorial is designed to help you understand how to create a simple pipeline. We will step through each field and describe exactly what type of information is required.
Simple Scenario
We want to create a simple ACT3D publisher pipeline that uploads files to the Catalog and includes the following processes:
- Watch the folder, C:\CAD, and its subfolders.
- Publish SpinFire ACT3D files.
- Upload the files to the Catalog.
- Convert the files to STEP format and store them in the Catalog.
Assumptions
- The original CAD file is uploaded to the Catalog.A thumbnail is needed and is uploaded to the Cataloghas sufficient read/write permissions.
- The local copy of the newly created file is removed from the local drive.
- The newly created file is written to the C:\out folder.
Steps
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
In our simple scenario, the CAD files are located on the local drive; select the Directory Watcher trigger.
| ||
Expand | ||
| ||
A Catalog Part is essentially the entry in the Catalog. The Catalog Part must exist in order to upload resources/files to the Catalog. The Catalog Part can be thought of as a container in the Catalog. We'll fill this container with the associated files. In this case, it will be the CAD file itself, the thumbnail, the ACT3D file, and the converted STEP file. We'll use the name of the CAD file as the name of this container or Part.
Since the pipeline definition is generic, we don't know what the file path and name is at this point. You could enter a specific path and file but then the pipeline would operate only on that one file. We need a variable that represents all the various files that are queued up during the pipeline execution. This is where Dynamic Properties are used. A Dynamic Property is replaced by its value; the value in this case is the current file being worked on. The dynamic property that represents the path and name of the current file being processed is: %dw.dw_changed_file% where the initial "dw" is the name of the directory watcher trigger defined earlier. Select %dw.dw_changed_file% from the list. Select Use filename as Part Number under Part Numbering. This means that the filename will be used to represent the part moving forward. This is important because: The CAD attributes will be stored in the Part under the CAD tab if they exist in the CAD file. Image Removed |
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
Expand | ||||||
| ||||||
Now, to convert the CAD file to an ACT3D file:
| ||||||
Expand | ||||||
| ||||||
Now that the ACT3D file has been created, we need to upload it to the Catalog (a process similar to uploading the CAD file in step #4).
|
Expand | ||
---|---|---|
| ||
We need to create a PNG file and assign it to the Catalog part as the representative thumbnail.
|
Expand | ||
---|---|---|
| ||
Expand | ||
| ||
Finally, we'll convert the original CAD file to the STEP CAD file format.
|
Expand | ||
---|---|---|
| ||
Now that the STEP has been created, upload it to the Catalog.
|
Info | ||||
---|---|---|---|---|
| ||||
It is common to use an action multiple times within a pipeline such as the Upload to Catalog. It's a good idea to give each action a descriptive name that makes it obvious to know what it does when using it
|