Closed as fixed if next.
1. Log in as Admin 2. Requests . Manage Requests > General Repairs 3. Select Request is for = Someone Else 4. NOTE the Location and Organization under Request Details defaults based on the initial Requested For person 5. Click on Name look up under Requested For, then select Abe Abstractor 6. NOTE the Location changes to match Abe's Primary Location 7. NOTE the Organization does NOT change to match Abes' Primary Organization (updates in 10.3.1) 8. Manually update the Primary Organization to Abe's 9. Submit the Request 10. When the Request is in Status = Issue, click on Associations tab then triTask > triWorkTask 11. Open the Work Task record 12. ISSUE: Primary Work Location on the Work Task generated from the Request does not match the Location on the Request (Abe's Location). Customer Organization does match the updated Organization
No known workaround.
When the Request is for = Someone Else is used to select a different User, the Location is automatically updated to reflect the Primary Location of the new person. On Submit of the Request, the Primary Work Location on the generated Work Task should match the Location on the Request, not the Location of the original Request is for = Me person Fixed WF "triRequest - Synchronous - on Change Requested For " to always map the triLocationRequestedTX field and also the triCustomerOrgTX was modified.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels