A task based process with a Boolean start condition always fires when a task is created via XOG in version 15.9.1 even if the condition is not met. A process created as auto-start where the start condition is on the create of a task and the condition is based on a boolean custom attribute being set false is not work as expected when the task is imported via XOG with the value of the custom attribute set to true.
Steps to Reproduce:
<?xml version="1.0" encoding="UTF-8"?>
<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">
<Header action="write" externalSource="NIKU" objectType="project" version="126.96.36.199" />
<Project name="My Project 1" projectID="PR2000">
<Task name="New Condition Test Task" taskID="t1" outlineLevel="1" summary="false" start="2021-04-13T08:00:00" finish="2021-04-14T17:00:00">
<OBSAssocs complete="false" />
Expected Results: The process will only fire if the condition is met.
Actual Results: A task based process with a Boolean start condition always fires when a task is created via XOG in version 15.9.1 even if the condition is not met.
Release : 15.9.1, 15.9.2, 15.9.3
Component : CA PPM BUSINESS PROCESS MANAGEMENT
Workaround: Change the Process Start Condition by using a different condition that does not use a Boolean field.
Fixed in Release 16.0.0