nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

FormAPI Save&Close problem

skd1

Hi,
We are calling a FormAPI callServer to deploy the DCRs, when the DCR is saved. The callServer is being invoked on the "onSave" event. We are experiencing some problem when the user creates a New DCR and clicks on "Save & Close". The dialog box for asking the user to submit the file for workflow doesnot show-up when the user clicks "Save &Close" button. Whereas, when the user first clicks on "Save" and then "Close" , in that case he/she is prompted to submit to workflow.
Please find the necessary attached datacapture.cfg and Javascript file.

Thanks
Sanjay Dash

Find more posts tagged with

Comments

Adam Stoller

You will not get prompted to submit the DCR via a workflow if the DCR is already associated with another job.

If the user first tries Save and then Close - and gets prompted to submit the files via a workflow and says "yes" - and then edits the same file and does Save & Close - they will not get prompted because the DCR is already associated with a workflow.

Does this match your experience? You can always do a File Properties on the DCR before editing it to see if it is already associated with a job - and if not, edit it and do a Save & Close and see what happens....

--fish
(Interwoven Senior Technical Consultant)

skd1

That is definetely my experience. At present the only way the user want to invoke a workflow is when the click the close button or the "save&close" button. They do not want to use the new job from the file menu. All they want is that they should be able to see in the DCR itself that the file is in the workflow.

I am thinking that we can do a callserver in the init, and check for extended attributes. If the extended attributes indicates that the DCR is associated with the job, then we can display a message.

Another related problem is that the user wants to invoke the job dialog box whenever they click on close button. The problem now is that if we click on edit dcr and then click on close without making any changes, the DCR window is closed. Is there anything that we can do on the close handler to prevent this, ie to force it to open the job window?

Migrateduser

I think (but I am not sure) that you could do an onSaveDone (or something similar) that does a window.open to call the CGI that creates workflows, passing all required parameters such as the full path to the DCR. Alternatively you could use FormAPI to set some hidden field, or find the variable that Interwoven uses to control whether to prompt and set that, but that would be a hack and the user might get a prompt to save when they had not made changes.

I think you want to do iwgetfilejobs to see if the file is associated with a workflow; I am not sure it is available in extended attributes. If I remember correctly you have to call this command once for each workarea on a branch as it only reports jobs in the workarea passed to it.