SmarTeam V5R17 SP6 was just posted on the SmarTeam support web site. There seems to be many good fixes in here so we are excited to be able to upgrade users to this SP. If anyone has any questions, just reply to the post or send comments to the team at InFlow Technology.
InFlow Technology PLM Technical Blog
Technical tips and best practices for the SOLIDWORKS PDM and ENOVIA User & Administration
For those who use PDMWorks Enteprise, you will notice that all documents are assigned a workflow when they are added to the vault. These workflows are developed using the Workflow Editor (here is an example). Everything from a CAD drawing to a word document will have a workflow assigned. Because of this, we have seen some people confuse workflow with document routing. In PDMWorks Enterprise, a workflow can serve two purposes, Document Lifecycles and Document Routing. Here is the difference: Document Lifecycle: This applies to documents that undergo revision control. For example, a SolidWorks drawing may start out as "Work In Progress", then move to "Pending Approval", then "Approved". Once […]
If you are interested in more flexible notification when using PDMWorks Enterprise work flow, InFlow has developed a tool to assist. We wrote about this before, but now, there is a video that explains how it works.
Do you have code that uses Block or Symbol insertions? If so, then this Blog is for you! It seems that something has changed in the New SW2007 API. We are working with SW to further understand what has changed. In the past, we were able to simply insert Blocks fairly easy swModel.EditSketch Set BlockInstance1A = swModel.InsertBlock("c:\flat_coated.SLDBLK", 0.0254, 0.0254, 0, 0#) Here is a sample bit of code that seems to work fine now for Blocks: Private Sub Command2_Click() Dim swModel As SldWorks.ModelDoc2 Dim BlockFName1 As String ‘Attach to running instance of SolidWorks If swApp Is Nothing Then Set […]
With the release of Service Pack 4 for V5R17, Dassault Systemes introduces a new milestone regarding Bill Of Material (BOM) handling with its flagship product SmarTeam. This article introduces you to some of the new features and capabilities in this long awaited update. The first feature to introduce is the Item Tree synchronization capability with CAD. In the past, users were left to their own devices to create an Item structure in SmarTeam. This may have been done by script or some other copy tree mechanism. An Item Tree structure can now be created automatically based on your CAD definition and kept in sync as your CAD data changes. You […]
Smarteam users need to understand the importance of using smarteam file explorer. This feature is NOT the same as using Windows explorer. By using smarteam file explorer, Smarteam knows the status of a object – whether it is New, Copied, Referenced or Checked-out. Windows Explorer doesn’t. Using smarteam file explorer – Smarteam WILL NOT allow the user to delete a file which is in "new" or "checked out" state. Reason – This is the only version of the file the user has. It is not available anywhere else. Windows explorer on the other hand will treat this file as any other. So, when the file is deleted, smarteam will still […]
Definition : Only an object explicitly assigned Check Out or New Release will be checked out. The configurations referring to the checked out object will be locked. Other users cannot checkout the locked configurations but can only copy them. Example : A solidworks part with 2 configurations – "Default" and "Flat_pattern" is in released state. "joe" needs to modify the part. 1. Login as user "joe" 2. In the "new release" lifecycle screen below, on clicking OK, Default configuration will be "new released" and flat_pattern will be copied. (see fig.1)3. When user "ann" wants to make changes to "Flat_pattern" configuration – the option to check-out will be grayed out. "ann" […]
Just a quick word on a bit of recent SmarTeam success… We have a customer that is now running 3 SQL SmarTeam sites. (Inflow now has many other Oracle multi-site SmarTeam customers) This is the SQL server with replicated Vault files only (DB is not replicated) The quick performance scoop is: – An assembly that takes about 2 minutes @ Site1 to Open – Was about 24 minutes @ Site2 and is now under 2.5 minutes – At Site3, it simply failed before and is now about 3 minutes or less (Slower line for the DB info) – Login times and general […]