Deleting a task or container in Kivati Studio does not always delete associated dependencies and/or chained properties.
When you delete a task, most of the time Kivati Studio tries to delete dependencies and chained properties associated with the task to help reduce compiler errors. Kivati Studio always deletes dependencies and chained properties declared by the task. That is, dependencies for which the deleted task is the target and chained properties that the deleted task is importing are always deleted.
In some cases, Kivati Studio may not be able to automatically delete:
- Dependencies for which the deleted task is the source
- Chained properties exported from the deleted task
Specific situations in which this may happen include:
- Deleting a task that has relationships to tasks in other containers
- Deleting a task from the project pane that is not also visible in a diagram
When you compile your project after deleting a task under these conditions, you may receive compiler warnings or errors.
This is a known issue in Kivati Studio and will be addressed a future release. As a temporary workaround, simply remove these objects yourself if you receive a compiler error or warning.