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.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

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: 

1. Create a boolean custom attribute on the task object. No default value 
2. Create a process and set it to an object based process by assigning it to the task 
3. Configure a start option on the create event with a start condition of ( Test Boolean = 0 ) 
4. Use the XOG XML below to create a task.  Note that any value (1, 0, true, false) of custom attribute will be ignored and the process will always fire 

<?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="15.3.0.200" />
   <Projects>
      <Project name="My Project 1" projectID="PR2000">
         <Tasks>
            <Task name="New Condition Test Task" taskID="t1" outlineLevel="1" summary="false" start="2021-04-13T08:00:00" finish="2021-04-14T17:00:00">
               <estimateRules />
               <CustomInformation>
                  <ColumnValue name="partition_code">NIKU.ROOT</ColumnValue>
                  <ColumnValue name="z_do_not_reset">true</ColumnValue>
               </CustomInformation>
            </Task>
         </Tasks>
         <Allocations />
         <scenarioDependencies />
         <InvestmentAssociations>
            <Allocations />
            <Hierarchies />
         </InvestmentAssociations>
         <General />
         <OBSAssocs complete="false" />
      </Project>
   </Projects>
</NikuDataBus>

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. 

Environment

Release : 15.9.1, 15.9.2, 15.9.3 

Component : CA PPM BUSINESS PROCESS MANAGEMENT  

Cause

DE60653 

Workaround: Change the Process Start Condition by using a different condition that does not use a Boolean field. 

Resolution

Fixed in Release 16.0.0