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.
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)
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register