record view issue

Question

Hi , 
 I have two buttons in summary view first insured and second insured. 
 First insured they can add task and even second insured they can add tasks will get in summary view. 
 After clicking on second insured tab, it is going another page there backtosummary link is there but when i click on backtosummary it is going to first insured tab . 
 i have handled through logic in interface level it is working fine but when i check in site level it is not working because there policy to task table has one many relations so selected task id not getting but rv!record. 
 how can i get selected taskid and i need to pass to rule input of summary page.

Shubham Aware · Accepted Answer

Since you open the Task summary through a record link, inside that Task view you won&rsquo;t have the parent Policy rv!record. Pass the selected Task Id as a URL parameter/rule input when navigating, then use that rule input on the Summary page to open the correct tab. 
 https://docs.appian.com/suite/help/26.3/url-parameters.html

VarunTejaGurrapu · Answer

Hi saneswarib657943 , I want you to understand few things- 
 When coming back: 
 
 Appian only knows rv!record 
 It does NOT remember which tab you came from 
 So your local UI logic is lost 
 That&rsquo;s expected behavior, not a bug 
 
 So correct approach could be - Pass the context (insured type + task id) explicitly when navigating. 
 1. Pass parameters while navigating - 
 a!recordLink(
 label: "Open Task",
 recordType: cons!AAA_TASK_RECORD,
 identifier: fv!item.id,
 parameters: {
 insuredType: local!selectedTab,
 taskId: fv!item.id
 }
) 
 2. Capture in target interface. 
 3. Come back to summary - 
 a!recordLink(
 label: "Back to Summary",
 recordType: cons!AAA_POLICY_RECORD,
 identifier: rv!record.id,
 parameters: {
 insuredType: ri!insuredType,
 taskId: ri!taskId
 }
) 
 4. Use - local!selectedTab: ri!insuredType in Summary Page. Just to summarize above context: To retain the selected insured tab and task context, pass the required parameters ( insured type and task ID ) explicitly through recordLink/navigation parameters and bind them to rule inputs in the target and summary interfaces, instead of relying on rv!record or local variables. If you still face any issues, please let us know, by giving more context through screenshots/text, that could help us to understand more.