I have been experimenting with the different Revisioning (Lifecycle) states and I am not sure if this has caused this issue or not
For My Items WS I have the following Lifecycle (See attached)
Unreleased -> Active -> Obsolete
Transitions: Release - Active , Revise -> Active & Retire - Obsolete
With both Release & Revise Transition set to Increment Version Only
After taking and Item through the Revisioning WS workflow the lifecycle of the item updated from Unreleased to Active & a Version of 1.
I have a relationship to my Quote WS Linked Items and when I use the create relationship icon I cannot create a new quote record and get the following message in the create relationship dialog "This item has already been linked to an incomplete Revisioning Item" and I cannot create the relationship.
If I go to my Quote WS and on a records Linked Item Tab I can successfully create the relationship to my items?
Not sure what I don't have set-up correctly?
BD
Solved! Go to Solution.
Solved by BiggePLM. Go to Solution.
Have you tried creating the new quote relationship using the add button found in the relationships tab? I am curious to hear whether issue is isolated to the relationship icon or not.
You mentioned that the item, you are trying to add a quote relationship to, has a revision value of 1. Could you try to create the relationship against the working version next and let me know if that can be done?
Yes to both suggestions. It appears I can add relationship as long as it is the working version?
1. From Sales Quote Linked Item Add. - successfully added link, shows as working version (see Add_Sales Quote.PDF)
2. From Relation Icon, Item & BOM - Working version (See Add_Relationship_working version.pdf)
Although I got a script error during the link creation when I used the create new Sales Quote that I need to work on but the PLM functionality appeared to be correct. Just for the working version only
The issue appears to be isolated to records who are in a revision other than working. Thank you for bringing this issue to our attention.
Well I can work with that for now, as I am in early development phase with my workflow, that I want to use this functionality and I am currently utilzing the grid. Once Linked Items can be added via script and not read only this will be an issue.
Thanks for responding and letting me know I wasn't missing a setup step and that your support team is aware and working on the issue.
BD
Sorry for any confusion both BiggePLM and DonovanJr are my AutodeskID.
I did not realize that with the new login change, the support site gets logged in using the user name that is logged into the PLM tenant. I had to setup a new Autodesk ID to separate the Administration user from my generic user.
BD
Thank you for letting me know and thank you for bringing this issue to our attention.
I had a two thoughts in terms of status of the items and the message about incomplete Revision controlled Item.
In reviewing the Life Cycle and Relationship sections on the Wiki Help it talks about the change window that is opened after a Revision Controlled item is linked to a revisioning workspace record.
One - In my tenant I had planned on leaving the working versions available to anyone with Item edit permissions, so that information can be updated "on-the fly" and once the changes need to be committed the users would link the working version to the Revisioning Record (or create new) and submit the proposed changes to be commited to my item admistrators. (Stage 1 in the revisioning workspace after creation). The Administrators could then review the changes and comit them by completing the revisioning workflow.
Is part of the issue that the changes were made to the working version of the item prior to it being added to a revisioning record?
Two: I am using the lifecyle; Unreleased -> Active -> Obsolete and I was only planning on incrementing the version not the Rev. since the "Rev" Lettering coorisponds to our Revision Release levels in Vault. In the Default this would follow the Document Control Lifecycle. I do not have the need to utilize both version control and Revision control in PLM so I chose Version to separate it from our Vault CO Process nomenclature.
Is this contributing to the issue?
BD
The per-design behavior in PLM 360 is to mandate that only working versions be assigned to a change order, and this rule also applies to your current configuration where you establish a link to your quotes workspace. The error message initially received when calling the create relationship icon on a non working version of an item is confusing and should state instead something along the line of "You cannot create a relationship to a released item revision, please select working version to proceed".
In PLM 360 a working version of the item is ever present so you don't need to revise an existing item in order to get a working version.
I hope this answers most of your questions.
I understand that functionality and it makes sense. Although, If I understand correctly, only working versions can be linked. if that is the case then there is an additional quirk, when you are in a workspace (Change Orders or in my Case Sales Quote) linked item (Affected item) tab and add a link, the list of available items from the linking workspace shows the current version/rev of the items. But it actually creates the link to the working version (I can get screenshots that show this). Not an issue, and is consistent with your stated use of working versions, but could be confusing or mis-leading.
I currently have a business case need to create a relationship between an two workspaces for a purpose other than revising. My intent would be that a service person needs to initiate a quote for a repair of equipment and has a equipment manual that gives him some information on the part he needs to get. He then uses the items & BOMS workspace to narrow into the exact part number to quote.
Rather than take the part number over to the sales quote and type it into the grid on the sales quote (that is currently how I have it structured). I thought, since the item needed is currently selected in the items & BOM workspace why not just create the link and add it to the linked items tab in the sales quote. With the new linked item object I could then dupicate the downstream script spawing activity of the sales quote workflow.
Hope this makes sense. I can continue to live with the manual entry method, but is there any plans to change or offer this functionality. If so I can submit it to the Idea Station
BD
Excellent observation! The UI defect has already been reported to our development team to only display working revisions in add items to affected items dialog. And as you've correctly observed, even if you select a revision (e.g. 1,2, or A, B), the item linked to the change order (or sales quote in your case) will be the working version. This shows that the defect is isolated to the current UI.
Please bear with me as I review your last use case.
Please confirm that you are simply looking for a way to call an action script after an item has been added as a linked item through a relationship.
Well I have action scripts associated with the workflow and Item create behaviors for the sales quote workspace that currently work from the grid tab once the grid has rows.
It is the step of adding the items from the Items & BOMS workspace to the sales quote grid. Currently I am using a linked pick list field that the user has to type in the part number in the field in the grid.
Most likely the user will start by looking through the items & BOMs workspace to find the item they need to process on the sales quote then enter it manually on the grid.
I was looking to make it easier to add items to sales quote using the relationship icon, Then process the sales quote workflow as it currently is set-up (Except use the linked items tab rather than grid. I will try to attach a diagram of my overall workflow
Although as I write this I realize that the spawing scripts in the sales quote workflow will work until I get to returning information back to the sales quote. The linked item object is read only correct?
So I am back to the grid....
Looks like I have a couple of things needed before I can make those updates to my process.
BD
Could you try to use the insert / edit image button?
Hi Bob,
What you could to solve this issue is leverage the relationship tab, where you could add items to it (by script) then at a latter point in time in the workflow pull information from the items and inset it to the grid and modify the items themselves if need be.
I am thinking this might be a little bit on the heavy side in scalability, but with a good usage of libraries and breaking up what is happening between steps in the workflow it could be possible.
And for reference on the scripting stuff:
( going for the bonus points)
relationship tab: http://wikihelp.autodesk.com/PLM_360/enu/Help/Help/0091-Develope91/0092-Server-S92/0099-Scriptin99#S...