Next week we’ll be going over multiple use cases in our PLM Talk technical webinar – so far my favorite bit is being able to easily approve/reject change requests so I’m not the bottle neck in our process!
In our last release we increased the time limit for script execution for both action and validation scripts. This request came to use from the PLM 360 IdeaStation. This forum was set up to allow our customers to easily share their wish list for product improvements with the PLM 360 development team. It’s a great place to review what’s been proposed and add your ideas to existing ones as well (or simply ‘kudo’ it so we can see how many folks are interested in the proposal).
Today’s tip is more of a best practice (and personal pet peeve when not employed!). When you set up a new workspace and define the descriptor, consider making those mandatory fields. Since the descriptor is used throughout the UI to easily identify items, it’s great to make it as meaningful as possible be making sure your end users input that data.
Want some more tips and tricks or some best practices on training your end users? Join us tomorrow for PLM Talk where I’ll talk about best practices around involving your end users in defining and improving your PLM 360 solution.
After spending last week clearing trails where we camp, I’m ready to get back to blogging about great new features in PLM 360! One that our coding friends will like is the new Clear() method we recently introduced. Before we had the remove () method which was great for removing a single specified value or object in an array, but you’d have to use a for loop to clear everything. Not anymore! Now you can use clear () – it’s supported on multi-select fields on the item details page and on the various tabs where you would need it: Grid,Relationships, Bill of Materials, Sourcing, Workflow Items, and Project Management.
For example, to remove all items from a multi-select pick list, you’d use item.MULTISELECT.clear(). Want to empty the grid array? Use item.grid.clear().
If you’re a PLM 360 admin that loves to extend your workflow and workspace capabilities using scripting, you’ll love the new Script Debugger feature we introduced last month! Lots of great advanced debugging features to help you develop and troubleshoot scripts.
The debugger will give you lots of visual cues as you walk through the script – there’s dynamic highlighting so you can see the active line of code you are debugging, breakpoints are marked in the line numbering. Something to note about breakpoints - they are only accessible and can set them once you start debugging and not simply when editing a script.
The Help goes into more detail about the different commands and tabs. As an admin myself, I’ve found it most helpful when troubleshooting my condition scripts (which I often employ to control who can perform certain workflow transitions). I demoed this and other new features from our May 2014 release the other week in a recent PLM Talk. Join us next Wednesday for one doing a deeper dive into PLM Connect (specifically showing a PLM 360 and Vault integration)
Continuing with the Autodesk Vault integration for Revit enhancements its time to take a look at the new capability for capturing and managing the Revit model project properties, where users have the ability to import and map these to Vault user defined properties.
A new Mapping User Interface on the Vault Options dialog has been added to streamline connecting Vault with Revit Projects where work sharing is enabled.
In the same vein, shared Parameters support allows users to point to a shared parameters file stored in the Vault for consistency and parameter reuse across projects, reducing effort and error.
We have also updated the In CAD capabilities, where users can manage category, state and revision of the Revit model with Autodesk Vault Professional document management tools and the Revit ribbon strip has been updated simplifying the Login In and Connection Status commands.
So that's about it - it's been a journey! With so many small powerful user enhancements this year, Revit users will hopefully be delighted and more productive than ever.
I was recently asked how in the world do I keep up my (almost) bi-weekly tips and tricks for using and administering PLM 360. A vast majority come from my experience being PLM 360 Administrator myself! Just yesterday I helped an end user on our training team (we’ve developed a solution to track the approval process for courses offered by out Sales and Training teams) effectively use the My Outstanding Work functionality on our Dashboard.
There’s a refresh button button right next to the heading – use that to make sure you’re seeing the latest and greatest. There is a nightly refresh, but using the button will make sure any tasks you’ve completed are removed.
If you train your end users to rely on their dashboard to prioritize their work, make sure they know about this. Brian Schanen did a great write-up with more tips and tricks for using My Outstanding Work in last year’s blog post ‘Your Work is Outstanding’.
In our last release, we extended what fields you can include in BOM views to include all fields from the Sourcing Tab – this is key for cases where end users may want to see information like the manufacturer of the part, the manufacturer part number, or the sourcing comments.
You’ll see now when creating or editing a BOM View you have access to all System Sourcing Fields (and any Customer Sourcing Fields you may have added).
And you’ll now see the system sourcing information in the BOM tab:
Continuing with the Autodesk Vault 2015 Revit integration theme this week we'll take a look at some of the new linking and import capabilities.
With this release users are are now able to directly access model related data stored within the Vault project location and import additional site detail or geometry including other CAD formats, DWG, DXF, DGN, SKP and SAT into the current Revit project. This reduces the steps required to import data, and unlike Link from Vault, when the project is saved back to Vault, only the project file is updated.
Speaking of linking, support for the link file command has been extended to include DGN, SAT and SKP files so more of the project related data can be referenced into the model.
The link to DWF or DWFx file is now also maintained meaning, when user checks out a file with a DWF link, the DWF file is automatically checked out as well. When the file is closed, the DWF link is automatically checked back into the vault - replacing a very manual process and making management a whole lot easier.
Some feedback I got from last week’s PLM Talk was to share more best practices around setting up workflows in PLM 360. Today’s tip covers just that – here’s an easy way to make using our workflow engine even easier. If you’re an admin, disable comments for transitions where input isn’t really needed. I don’t know about you, but if I see a box there for optional comments, I feel the need to write something! It can speed up the process to remove that temptation when it’s not warranted (perhaps on something like a transition to ‘Implemented’ like we show in our ‘out-of-the-cloud’ Change Order workflow):