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; } } }

alert when submit to staging

helloworld

There are 2 successors in the review task. One button is return to the author, another is submit the file to staging (Aproved).
I would like to know if any confirmation can do when the reviewer click on the button that submit the files to staging?
The confirmation can be javascript (alert()), or another solution.

Thanks!

Find more posts tagged with

Comments

MAK

Hi,

I dont think Interwoven given this functionality for the submit task but you can have a cgi task in between to include this extra check.

This CGI task can open a form and ask for user confirmation.

Prerna

We don't need confirmation at submit task,do we? Rather we need it at the review screen that'll be a cgi i suppose.
In that case we can definitely use javascipt alert.

Pawan

There are 2 successors in the review task. One button is return to the author, another is submit the file to staging (Aproved).
I would like to know if any confirmation can do when the reviewer click on the button that submit the files to staging?
The confirmation can be javascript (alert()), or another solution.

Thanks!

I think you should use the appropriate words to describe your question. As you said the review task has two successors, what is the purpose of this task?

MAK

Hi,

If your review task is a usertask, Prerna is correct that you make it a cgi task and include extra check before calling submit task.
BUT if your review task is a group task, it is better to have an extra cgi task for confirmation as cgi task does not provide easy implementaion of taking ownerships, etc.

It will be better if you frame your question again, if things are still unclear.

helloworld

Hi,

If your review task is a usertask, Prerna is correct that you make it a cgi task and include extra check before calling submit task.
BUT if your review task is a group task, it is better to have an extra cgi task for confirmation as cgi task does not provide easy implementaion of taking ownerships, etc.

It will be better if you frame your question again, if things are still unclear.

I am sorry, maybe my question is not clear.
Actually, the workflow as follows:


       -->           -->
Author      Reviewer     SeniorReviewer
       <--           <--

               |
               |
               V

            STAGING

The scenario is that the workflow is trigered by Author, and then the content is send to Reviewer, after the Reviewer's review, the content is send to SeniorReviewer. The content must be approved by SeniorReviewer, and then return to the Reviewer, and then Reviewer do some paper job (e.g. print out the content), then to deploy to STAGING.
So, in the Reviewer's workflow screen, there are 3 buttons. One is "Return to Author", second is "Send to SeniorReviewer", third is "Deploy" that means transit to submit task.

The problem is that the Reviewer may has mistake to click the "Deploy" before the review task of SeniorReviewer. So, the Reviewer must be confirmed when he/she click the "Deploy" button.

Thanks!

suj

The scenario is that the workflow is trigered by Author, and then the content is send to Reviewer, after the Reviewer's review, the content is send to SeniorReviewer. The content must be approved by SeniorReviewer, and then return to the Reviewer, and then Reviewer do some paper job (e.g. print out the content), then to deploy to STAGING.
So, in the Reviewer's workflow screen, there are 3 buttons. One is "Return to Author", second is "Send to SeniorReviewer", third is "Deploy" that means transit to submit task.

The problem is that the Reviewer may has mistake to click the "Deploy" before the review task of SeniorReviewer. So, the Reviewer must be confirmed when he/she click the "Deploy" button.

Thanks!

I would suggest to simplify the reviewer task.

After author submits, the reviewer task should have only 2 successors. Return to Author
Send to SeniorReviewer.

The Deploy option should come in a user task after the 'Senior Review' task.

helloworld

I would suggest to simplify the reviewer task.

After author submits, the reviewer task should have only 2 successors. Return to Author
Send to SeniorReviewer.

The Deploy option should come in a user task after the 'Senior Review' task.

You are right.
But this is the user requirement, the deployment must be on the Review task, because they must do some not electronic job (e.g. print out etc...) before deployment.

MAK

Hi,

Ok. keep the workflow as it is till this point.

When reviewer clicks on Deploy do the following.
1. Instead of the direct deployment task, call a CGI/User task in between.
2. In this CGI/USER task, ask reviewer for confirmation. (you can even have a check whether a senior reviewer approved though WF variables, etc)
3. In case of the confirmation (YES), call the deploy task.
4. In case of failure(NO) call the review task again.

I hope i am able to make it clear, let me know your thoughts on this.
You can even do these checks in your external deployment script but that will make your scripts more complex.

so your new WF will look like this.


       -->           -->
Author      Reviewer     SeniorReviewer
       <--           <--

            ^    |
            |    |
            |    V
        IF NO
        CGI/User Task for Checking
               |
               |
               V
             IF YES 
               |
               V
           STAGING