DCR Save Issue

prem_pratick

Can any one please let us know what happens in the below scenario.

1. When a user clicks on the Save button , he does not wait for the DCR to save , but keeps on clicking the SAVE button , the deployments gets linedup. Does this lead to the Opendeploy stalls during deployment.

2. Is there a way to stop a user from clicking the SAVE button, when he has already clicked on SAVE and the DCR is still saving(Deploying) in background.

Note: We use Form API (Call server) which calls the deployment command when a DCR is saved.

Thanks
Prem Pratick

Migrateduser

Hi Prem -

The scenario you describe apparently has some significant customization. Typically the deployment would be handled by a workflow, but it sounds like someone may have written some FormAPI to trigger a deploy after the save. The only scenario I can think of where that would be useful would be if you were using some sort of external server for doing the preview and for whatever reason mounting the workarea as a filesystem on the external server wasn't a viable option.

Obviously, I'm way out in speculation land here, but if I'm on the right track, probably all you need to do is update your save handler to set a flag on the beginning of the save process and unset it at the end of the deployment. Check the flag every time the appropriate onSave event fires (there's a whole stack of them - see the FormAPI manual) and only process it if the flag is not raised. If the flag is raised, just pop an alert to tell the user to wait.

That said, if the user is clicking the button repeatedly, it's probably an indication that the whole process is taking too long for this to be a viable approach from a usability standpoint.

If you'll post your DCT and any associated FormAPI, I'll be happy to take a look and see if my guessing about what's happening is in fact on track.