Legacy Item Upload - Choose current revision in release workflow

[aaron37SWJ]

Hey,

We have a lot of legacy items that are still to be loaded into Upchain as we found the initial migration many years ago to be problematic so we choose not to only migrate the most current projects.

We are now finding that we are modifying a lot of those legacy parts and when uploading to upchain the revision of the part/s in question are usually not revision 0.

Could an admin have the power to choose the starting revision for that item during release. For example if we have a part at revision 5, we have to loop around a CR 5 times to get it to catch up correctly. It would be far easier to have that choice on release. (yes we would loss some traceability, but we also lose traceability when we do 5 revisions of the same item to catch up to current, it is just long and tedious and a job no one wants to do.)

You may have a work around already for this so welcome for some advice if so.

Thanks 

Aaron

[SonicFlow]

This is essential PDM functionality that other systems incorporated years ago. Not just for admins if you have trusted users. This may be possible in Upchain with a custom workflow? But getting creative shouldn't be necessary, since this is something every company needs at some point.

[PualQuek]

Hi @aaron37SWJ,

Just to understand your process better, could you send me a video of what you are currently doing and your expectation in a private message? 

I can get the team to provide some guidances or setup some calls with you. 

Regards,
Paul
Principal  User Experience Designer (Upchain)