"There are required questions still unanswered"

[Angersma]

Hoping someone has seen this before.  

We have a general catalog item with questions.  The question Template contains 6 questions, all are required, all are visible and all are being answered by everyone ordering the CI. 

When we view these requests from My Requests or from the Approve/Reject page we see the ? icon with the yellow triangle, and when we mouse over it says "There are required questions still unanswered" .  It is causing some confusion because the standard approval actions are not working. 

Our approvers have to approve by clicking the request so it opens and clicking the Approve button in the popped up window.   Checking the box and clicking Approve from the Approve/Reject page does not work because this process requires all questions to be answered. 

Also, when we open the request from the Approve/Reject page, there is an exclamation point icon next to Questions, but when wed go to Questions -> Unanswered Questions, it says "There are no unanswered questions. "

Has anyone seen this before?  How did you troubleshoot?   How can I determine which question the App Portal does not think is answered?   Thank you!!

[TeriStevenson]

I've seen this when a question has been added to an existing template and the request was submitted prior to the question being added.  I've also seen it on other random instances.  If you look at the WD_PackageRequests table for one of the requests there is a column 'HasPendingQuestions' and you can set the value using sql  A few years back I ran into the issue Solved: Adding questions to existing template - Community (flexera.com)

[Angersma]

Thanks for the suggestion @TeriStevenson !    It seemed like our scenarios were a little different, but we did try to create new questions and a new Q  template like your linked article suggested.  Things seemed even more strange after though.  We eventually figured out the Approval workflow had the question template option set to Yes, and referenced our original Q template.   An unintended config.  Once we set that back to No everything was predictable again.