I had a comment posted in another blog (Agile PX - Creating an Agile PLM Process Extension ) from Akshay who wanted to know how to get items from the Recently Visited and Navigator panes in the web client. They figured out Recently Visited items, but not Navigator. Navigator doesn't appear to be persisted, so there is little help I can offer, but I thought readers may be interested in knowing how to get the Recent items.
The process flow is pretty simple:
- Get the IUser of interest
- Get the recently visited IFolder
- Iterate over the IAgileObjects in the IFolder
Sometimes the AutoNumber facility in Agile PLM does not offer the level of sophistication needed to produce a truly intelligent part number. Fortunately, Agile provides an extension point to create custom AutoNumber sources. This blog will outline the steps needed to create the code for the custom source and get it installed in Agile so it is ready to use.
In my last blog article, Process Extension Development – Demoting a Change Order, I offered some source code that demotes a change order when one of the affected items on the change has an obsolete item on its BOM. There were a few follow up posts in the LinkedIn discussion about how to create a process extension, also called a PX. This blog will help outline the steps to package the source code, create the ICustomAction and configure Agile PLM to trigger the process extension (PX) on the submitted workflow step.
Demoting a change with an obsolete part on the BOM of an affected item
I often go through the Agile PLM SDK group in LinkedIn. On a recent visit, someone was having an issue with obsolete parts showing on the BOM of an item on a change order. To be clear, the issue is not that parts on the change were obsolete, it is that parts on the BOM of the affected items of a change were obsolete. A process extension (PX) was proposed by another group member to remedy this business rule. This blog illustrates the implementation of that process extension.