How to do an insert and stay using a script in a workflow

lekskr
Kilo Expert

I have a requirement where I needed to add additional approval to a KB article when the submitter has press the publish button.  I'm able to integrated the additional approval process however, when one of the requested user rejects the article, then the KB article is set back to draft, and the user can then press the publish again and the 2nd workflow is started.  At the 2nd time around when a user had approved the KB Article,  the rest of the requested users are not marked as "not required".  

Because it's the 2nd time around on the approval table with the same KB article number, how do I distinguish between the 1st round of approval from the 2nd round of approval?

I was thinking of that I can create a new KB # (insert and stay) at this point so that It will go through the approval process again when the submitter publish the article? Not sure if this is doable or best practice?

Any thoughts are appreciated.

1 ACCEPTED SOLUTION

Abhishek_Chavan
Tera Expert

Hello lekskr,

 

Let me see if I understand your requirement correctly. You need the approval workflow to trigger everytime the knowledge article is published. I am not really sure I understood your requirement when you say - "the rest of the requested users are not marked as "not required".  "

 

If the process has to be repeated for the approval workflow then you donot need to identify if the record is sent for approval the first time or the nth time, just set the required field to "Draft" and then make a conditional query to check if the status is what you need i.e. Draft in this case or approved and then you can add the next steps afterwards in the flow.

View solution in original post

2 REPLIES 2

Abhishek_Chavan
Tera Expert

Hello lekskr,

 

Let me see if I understand your requirement correctly. You need the approval workflow to trigger everytime the knowledge article is published. I am not really sure I understood your requirement when you say - "the rest of the requested users are not marked as "not required".  "

 

If the process has to be repeated for the approval workflow then you donot need to identify if the record is sent for approval the first time or the nth time, just set the required field to "Draft" and then make a conditional query to check if the status is what you need i.e. Draft in this case or approved and then you can add the next steps afterwards in the flow.

Hi Abhishek,

Thank you for your comment, I will try to do the conditional query as you suggested.

 

Rattana