This content has been marked as final. Show 5 replies
We ran into a similar situation where a file was released in one country, but not in others.
I ended up making a workflow for this but it was huge and unruly! What we really wanted was the ability to assign permissions based on a checkbox so that you could leave a file in 'Released', but still assign permissions for viewing - sort of a 3rd dimension to permissioning.
We haven't seen a formal solution for this yet.
Set set up another workflow that links from Released (approved) which only Engineering see and we just send it to this workflow for All-Released (all approved) and then everyone sees the files
What happenes when you want to revise the file again before it gets to "All-Release"?
Do states apply at the revision level? Meaning Rev A could be "Released" and Rev B could be "Inwork"? And therefore the shop would only see Rev A?
We pull it back from All-Release workflow for changes it it goes back through our standard workflow for rev.'s. This is why we made a seperat workflow for this.
What does the shop see?
Our problem is engineering may have several revisions inwork that the shop hasn't implemented yet.
So the revisions and status may be:
E - Inwork (ECO in progress by engineering)
D - Approved (Engineering released but not shop effective)
C - Approved (Engineering released but not shop effective)
B - Released (This is what MFG is currently making)
A - Inactive
In the above example, MFG on the shop floor should only see Revision "B". Mfg engineering should see revisions "C" & "D" because they would be getting ready to implement the changes. Only product engineering would see all revisions inlcuding Revision "E".
Not sure how Enterprise can handle this, it seems the workflow is not revision specific, or is it?