Hi everyone, I'm pretty new to being an administrator of FootPrints, and I'm having a little trouble trying to figure out how to successfully do a specific task via a business rule.
In one of our workspace items, we use a workflow to generate business rules at certain stages. Once the workspace item reaches the "Approved" state, the workspace generates multiple subtasks to multiple teams/assignment groups, via Business Rules and Quick Templates. One of the subtasks (we'll call it subtask "B"), however, needs to either not exist, or exist in "On Hold" status, until a specific subtask (let's call it subtask "A") to the same master item is changed to a "Completed" status. Here are a couple ways I was looking to approach this:
1. Master Item reaches "Approved" state, and subtask A and B get generated, but subtask B is set to the "On Hold" status. Once the status of subtask A is set to the "Completed" status, THEN subtask B's status is changed to "Unacknowledged" status with an update to Subtask B's Description field.
2. Master Item reaches "Approved" state, and only subtask A gets immediately generated. Once the status of subtask A is set to the "Completed" status, THEN subtask B is created.
I'm aware of how to populate new ticket fields using a Quick Template fired off by a Business Rule, so setting the new ticket values is not a problem at all. But trying to either only generate subtask B when subtask A is changed to Completed status, OR later go back and change the status of subtask B when subtask A is changed to a Completed status, are the specific things that I'm having trouble with. Here's what I configured yesterday to try to accomplish method #2 above (seemed more likely that I could do method #2 based on the parameters you cna use for the conditions), and when I published and tested this, subtask B did not get created when I marked subtask A as Completed:
The title I specified in the criteria is unique, and is verbatim the title of subtask A. And the status of "Completed" is verbatim the name of the status that I changed the ticket to, but subtask B did not get created when that criteria was met.
I prefer the method #1 approach, if possible. Either way this is addressed I do need to assure that subtask B remains as a subtask to the Master Item.... I'm hoping to avoid a nested subtask, where the subtask B is a child item of subtask A, rather than subtask B being a child item of the Master Item. Hope all of that makes sense. Does anyone have ability to assist with this? Thanks so much!!!