Is it possible to prevent a Comala Review when an assigned task is still open? (No reporting app)

[Deleted user]

I would like to prevent a user from submitting a page for review when an assigned task is still open in Comala Document Management. 

The problem is solved easily if the Reporting for Confluence app is installed.
https://wiki.comalatech.com/display/CWL/Make+tasks+disable+a+review

However, we do not have that application. Is there a workaround that is possible? 

We also have JIRA, would that work as an alternative to the Reporting for Confluence app? 

[James Conway · Accepted solution]

Hi @[deleted] ,

One option would be to use the completed  transition on a separate state prior to your review state. The page state will only transition when all tasks are completed. I have provided an example workflow in workflow markup below:

{workflow:name=Complete the tasks}
    {state:Editing|submit=Complete Checklist}
    {state}
    {state:Complete Checklist|completed=Review|description=Complete all tasks to undertake the content review|taskable=true}
        {task:Proofread Content}
        {task:Attach Test Results}
        {task:Resolve all inline comments}
    {state} 
    {state:Review|approved=Done|rejected=Editing}
        {approval:Review|assignable=true}
    {state}
    {state:Done|updated=Editing}
    {state}
{workflow}

You'll need to use the Markup editor in workflow builder (https://wiki.comalatech.com/display/CDML/Markup+editor+in+workflow+builder) to copy this example workflow. 

I have asked our Technical Writer to look at adding this example to the documentation, I expect it will be included in our current documentation space next week at https://wiki.comalatech.com/display/CDML/Make+tasks+disable+a+review 

Let me know if you have any questions here. But if you need a more timely response, please do reach out to our friendly support team with any question at any time via https://support.comalatech.com 

Kind regards

James
Senior Product Manager

[Deleted user]

Thank you for the response @James Conway.

For my implementation, I moved the tasks to the previous state to suit my situation. 

This works if tasks are marked as complete in the "Complete Checklist" state. However, if tasks were marked as complete in the previous state and then transitioned to this state, this would fail. 

I imagine the best way to deal with this is to have at least one task generated on the transition to "Complete Checklist", as you have done in your example. 

I will run this by my colleagues and determine if it will be better to have the onus of ensuring tasks are complete on the content creator or the reviewer. 

Thank you again for the great answer. 

Update:

The only problem with this method is that if I transition back to a previous state, incomplete static tasks will be duplicated when transitioning back to the task checking state. I solve this with the {complete-task} macro in triggers for transitions to previous states. I use a comment to indicate this is an automatic completion to prevent duplication for history.  

[Matteo Gubellini _SoftComply_]

Hi Stephen,

Is it for manually created tasks or the ones built into the workflow?

If you share the WF with me I may be able to figure something out.

Matteo