fix(workspace): drop native confirm() on Close Receiving

Native browser confirm popups look out of place in the tablet UI.
Mark Counted is already a deliberate prior step, so requiring a
second confirmation on Close Receiving was just friction. If a
receiver hits Close prematurely, action_reset_to_counted on
fp.receiving from the back office is the recovery path.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
gsinghpal
2026-05-24 19:36:48 -04:00
parent fc17754996
commit 8d4c85cc52
2 changed files with 6 additions and 4 deletions

View File

@@ -5,7 +5,7 @@
{
'name': 'Fusion Plating — Shop Floor',
'version': '19.0.33.1.8',
'version': '19.0.33.1.9',
'category': 'Manufacturing/Plating',
'summary': 'Shop-floor tablet stations, QR scanning, bake window enforcer, '
'first-piece inspection gates.',

View File

@@ -496,9 +496,11 @@ export class FpJobWorkspace extends Component {
}
async onReceivingClose(rcv) {
if (!window.confirm(`Close receiving ${rcv.name}? The recipe steps will take over.`)) {
return;
}
// No confirmation — Mark Counted is already a deliberate prior
// step, and the native browser confirm() popup looks out of place
// on the tablet UI. If a receiver hits Close prematurely, an
// admin can reset via fp.receiving.action_reset_to_counted from
// the back office.
try {
const res = await rpc("/fp/workspace/receiving_close", {
receiving_id: rcv.id,