Thank you for the feedback. The information on the File manager is very helpful.

Md

Yes the design was made to have additional lifecycles other than OTB Preliminary, Prototype and Production released. We have lifecycle phases like concept and others which are specific to part subclasses.

never mind, my local Agile Angel sat on my shoulder and it works as designed. Thanks Vaibhav

hi there,
no I wanted to add another value to the Workflow routings tab. We decided on an extra page 3 field where MDM will fill out the field to determine who is working which CO. We wanted to put Signoff duration as well, but that isn’t available in the OTS reports so we will develop an OBIE report for the users.
Dashboards worked well for this solution.

Thank you for the responses.

Thank you both for the answers. I like the simple approach, add the subclass name.

Correction to my question, this is under Default Types, not business rules.

Hi there,

I like this solution. Thank you

Md

– For ECOs with affected item as Chevy 
– Restrict ECO attachment access to users only listed under User Group – Chevy Restricted Access

Hi there,

I am not sure which version of Agile changed this, but descriptions become Rev controlled and need to be updated with an ECO. It makes sense, a Rev C item might have a different description than Rev A and Agile used to cascade the new description over the older revisions.

Md

Hi there,

We will be interested in this question as well.

We have Agile 9.3.4 with Sites. We will use the Sites to have the ME enter their BOM and use the Master site as a common BOM in Oracle. SCO can be used for the ME to change their mBOM.

One issue we have is the engineering BOM uses A/R as quantity and uses /XX numbers instead of real numbers. It is because our ME cut to fit in the field wire and heat shrink tubing.

Md