Let me start by saying that every related list is a record on another table that is "somehow" related to your main record. As an example, a change_task is related to the change_record through the change_request field.
So, the change task is a related record to the actual change
So what you want is that when something happens at the change_task level then that triggers an update at the change_request level right?
What you need is a business rule on the change_TASK level (related list table) that monitors the condition you want. Then the code will Glide the change_request table where (in this case) change_request.sys_id = change_task.change_request. Finally you will update() that record.
Let me start by saying that every related list is a record on another table that is "somehow" related to your main record. As an example, a change_task is related to the change_record through the change_request field.
So, the change task is a related record to the actual change
So what you want is that when something happens at the change_task level then that triggers an update at the change_request level right?
What you need is a business rule on the change_TASK level (related list table) that monitors the condition you want. Then the code will Glide the change_request table where (in this case) change_request.sys_id = change_task.change_request. Finally you will update() that record.
