Comment 4 for bug 1825245

We're completely fine if the interface for this is kept separate from replacing barcodes. The only relation between the two activities is that they are together in the XUL client, and it works. While they aren't in the web client, and it doesn't work.

The real issue is a combination of how required statcats are enforced, with how some things in the interfaces are tied to workstation registration. The XUL client provides a way around it, the web client doesn't.

Until there is an alternative to doing a workstation registration changing dance, we have to use the XUL client for this.

Separate interface for managing parts? That'd work.

An equivalent to "operator change", but for "workstation", to change what org it thinks you're at? That'd work too (even better). Or something else to make centralized cataloging & item management easier, without being hamstrung by whatever org your workstation is registered with.