How to create problem_task record on the same domain as problem, when created from the 'Child' related list on Problem recordSummaryWhen creating problem_task from "Child" related list in the problem record, it creates the problem task through interceptor configuration in the logged-in user's domain. However, customers require to customize this behaviour and want to create the problem_task in the problem record's domain from which it has been created. Usually, it is not easily achievable because it's not possible to fetch the problem's domain before the problem_task creates. There are no direct relation setups between problem and problem task (in "problem" or "parent" field). 1.Go to any test problem record in the cutomer domain. 2.Scroll to the related list "Child"3.Click on new button in the list.4.Select "Problem task" from the list of options.It takes to the new problem task form.5.Enter some values on the form fields and then save it.6.Refresh the same problem record from which it has created.7.Check to the "Child" list, bring domain column in the list and verify it's created in the logged in user's domain. NOTE: The 'Problem Task' is not available by default on the OOB interceptor for Task (sys_wizard.do?sys_id=eb84f2e4db0320107f02ff1a6896190f). To get the problem task entry, create one sys_wizard_answer record as part of the related list on the above record.InstructionsIt is basically an implementation question. Still, there is some way to achieve this requirement. However, please note that from Technical support we do not work on customization or implementation issues as it is out of our action scope. This is a small working version based on the above requirement, which customers can test and if helpful, can build their own customization on top of it. First of all, there is no OOB way to put the record in the same domain as PRB record, as there is OOB BR that checks the (Domain - Set Domain - Task) logged in users company domain, and places the record in the same. But we can catch the sys_id of the underlying PRB record, and check the domain, and set it to the problem_task record through a Business rule. When clicked 'New' button under the 'Child' related list and follow the steps, it actually creates an entry on the task_rel_task table as well. This table contains both the PRB and PTASK record's references. The suggestion is to create a Before Insert BR on this table, get the data from both the fields and set the domain accordingly. Here are the details of the sample BR Table: task_rel_taskAdvanced- Checked When:Before Insert: Checked Script: (function executeRule(current, previous /*null when async*/) { // Add your code here var prbRec= new GlideRecord('problem'); prbRec.get(current.child); var prbTaskRec = new GlideRecord('problem_task'); prbTaskRec.get(current.parent); prbTaskRec.sys_domain = prbRec.sys_domain; prbTaskRec.update(); })(current, previous); With this, the problem_task record is created in TOP/ACME domain, when the PRB was also in TOP/ACME domain. Please try this in subprod instance and test to see if this fits the requirement.