In EWB is there a work around to check a modified Revision back in to the Part Master Rev without first approving it?
Undoing Checkout deletes any work done to the Revision while in EWB.
Approving the Rev to Exit EWB then unapproving the Rev once back on Part Mast. Rev seems to be the only capability.
Has anyone used another approach? We use Individual ECO’s and hand the work from ECO to ECO hence the passing around of unapproved Revs for Engineering modifications.
Not sure what issues approving/checking in could cause, can you provide more detail?
Any hierarchy/order to how you pass revs around?
If so, in a few cases I’ve used workflows with custom user alerts to maintain a sequence.
Unchecking “Single User” on your group to allow sharing the checked out rev(s)?
The Engineers have sequential responsibilities to constructthemethod. They also have their own ECO"s that they want to check revs into and out of.
There are 4 engineering processes to go through to get a method.
Steps 1, 2, and 3 result in partial methods with only step 4 giving formal approval.
Engineer 1 want to initiate the method in his ECO then put it back into the Master File as “unapproved”.
Engineer 2 picks up the unapproved Rev from the Master file and processes it in his ECO, adding materials. When he is done, he places the Rev back into the Master file in an unapproved state.
Engineer 3 takes the unapprovedRev from the Master file and puts it into his ECO. He adds Operations.
When done, Engineer 3 puts the Rev back into the Master file in an unapprovedstate.
Engineer 4 gets the unapprovedRev from the Master file and puts it into his ECO where he modifies or verifies the whole structure for Production.
Once satisfied, Engineer 4 moves the Rev out of his ECO and back into the Master file but does so in an Approved state.
Weird, yes. But the Engineers work in silos and do not want to hand off ECO’s which would fit the workflow model.
Each Engineer perceives his ECO as his domain and what is in that domain for revisioning, represents his workload.
@robcar603 In post processing of CheckIn you can check for Engineer4 or an Engineer4 security group and unapprove the revision. If Engineer4 could be any of them then a checkbox for ready to approve could be used to stop the unapproval.
I will dig into that approach. Are you suggestinga Method Directive?