Issues with blank change tasks being created

[Community Alums]

We are having an issue with blank change tasks being created and I need some help pinpointing the issue:

Scenario: A change ticket is created and then submitted without any change tasks being added. This particular workflow does not have any automatically generated change tasks, but does follow a workflow related to approvals.

Outcome:

The change ticket is created, but along with it a phantom change task is created as well. This task is associated with whoever started the change ticket, but it is not associated with the change ticket itself. It is completely blank. It really shouldn't even be allowed to be saved, as it has several fields that are required on it prior to save, but somehow whenever a Change is created and submitted without a change task on it first, one of these phantoms is created. I tested the issue and if the change tasks are added and then the ticket is submitted this does not happen.

Any ideas?

I've attached a screen shot of the phantom task for reference.

[Mike Allen · Accepted solution]

So, two possible culprits, I think:   Business Rule and Workflow.   Check your business rules for a script that contains insert() and look at these.   It will also contain change_task.

The workflow will have a step that creates, but you said you did not see that in you workflow.   Still look for any Run Script nodes to make sure they are not creating the change task.

[Community Alums]

Found it, Thanks Mike. It was a run script...didn't have an insert but it was basically creating a new task when there weren't any change tasks created. Not sure why it was in the workflow even, it doesn't look like it was doing anything, well other than creating the phantom tasks