Unable to set To Do as Primary Object in a Process
search cancel

Unable to set To Do as Primary Object in a Process

book

Article ID: 367980

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

I set the object to Event Enabled for ToDo object in studio and am not able to select it as a primary object. I couldn’t find any documentation from Broadcom indicating this object is not available for auto-start and processes. Can you please explain this behaviour?

Resolution

The To Do object isn't process-enabled, which is why it doesn't appear in the list of objects for selection as a Primary Object. Consequently, users cannot create a process directly on the To Do object.

However, let's explore what "Event Enabled" means on the Object properties page, using To Do as an example. Although To Do can't be chosen as a Primary Object, when a process is defined on Task and To Do is a sub-object, it remains available for selection when creating expressions on attributes. This selection isn't influenced by the Event Enabled flag.

When an update occurs on any To Do instance, and if there's a condition (such as Auto start/Post/Pre) on the process, an event will be raised from the App and BG if the object is event enabled. If it's not event enabled, this event won't be raised, leading to delayed conditional evaluation. In such cases, the condition evaluation happens at a stipulated time interval rather than immediately.