Functionality of "Parent" Field on Task table and will REQ's be Parent to an RITM's

divyakosaraju · ‎07-26-2019

Hi ,

I would like to know more about "parent" Field on Task table and the behavior of it. Currently i observed that RITM doesnot have any REQ number populate in its parent field and that is where i was curious to understand more about the functionality.

Thanks,

DIvya.

Chuck Tomasi · ‎07-26-2019

Parent field on task points to the task [task] table. That means whatever records (incidents, change requests, etc) that are extended from task are available. However, you don't have access to the extended fields on them because they are displayed from the task record.

Additionally, most people don't want to related ANY task to an incident or RITM, or whatever - they want a specific class.

For this reason, you will often find a specific reference field on a record such as RITM has a Request field that points specifically to sc_request, not task.

If you want... you could write a BR that updates your parent field whenever request is updated. I'm not sure what value this bring above having the request field, but that's you call.

View solution in original post

Chuck Tomasi · ‎07-26-2019

Parent field on task points to the task [task] table. That means whatever records (incidents, change requests, etc) that are extended from task are available. However, you don't have access to the extended fields on them because they are displayed from the task record.

Additionally, most people don't want to related ANY task to an incident or RITM, or whatever - they want a specific class.

For this reason, you will often find a specific reference field on a record such as RITM has a Request field that points specifically to sc_request, not task.

If you want... you could write a BR that updates your parent field whenever request is updated. I'm not sure what value this bring above having the request field, but that's you call.