Dynamic Scheduling not working for FSM with domain separationSummaryThe Dispatch Groups are in domain – XYZ The Work Groups are in domain – ABC The locations are in customer domain - Top/ Cust. As soon as we put a customer company against a Work Order, the Dynamic Scheduling does not work due to domain mismatch. However, if we make the domains same for Dispatch Group Work Group and location , the logic works fine. Also note if we keep the company field blank, logic works as well, as there is no domain mismatch. Business case-Customer domain Top/cust needed to be supported by the service provider domain Top/XYZGiven the details in the docs, it seems like the dispatch group and the workgroup needs to be in the same domain as the domain of the work order.This cant be the case for XYZ as the service providers need to support the customer and they will be in a separate domain. Steps to reproduceCheck the domain configurationXYZ domain which is the Service Provider domainCustomer domain which is CustDispatch groups, workgroup records are in MSP domain that is ABC , and location and company are in CustRelated LinksFSM didn't add any specific domain separation and only support basic domain separation, WO is created in the company's domain is how general Domain Separation works. Please check here (https://docs.servicenow.com/csh?topicname=c_DomainAssignment.html&version=latest) to see domain assignment.Since on a WOT record, it can not see the dispatch group from the other domain, that's also an expected behavior or general domain separation. There's some ways list in this Domain Visibility Doc: https://docs.servicenow.com/csh?topicname=c_DomainVisibility.html&version=latestWe can either use Contains Domain or Visibility Domain, however, Visibility Domain is a user-to-domain relationship and is explicitly granted. For this usecase, I think we can use Contains Domain which is a many-to-many, domain-to-domain relationship. When a domain is selected, you can see the data from that domain and its children. A contains domain lets you relate domains on an as-needed basis, so in this case, the dispatch group's domain should be contained by the customer's domain.