#Financial Services Cloud25 人正在讨论

Hi @Sandip Patel, Thanks for the suggestion. 

I checked the ReferralDefaultContextDefinition and it is already Active. Since this is the standard/OOTB context definition, I only see Extend and Clone as available actions.   

I'm wondering where I can check whether the context definition is 

published/deployed/republished. If those are already correct, this may be related to feature provisioning in the pre-release org. I'll update the thread once I have more information. 

Hi @Rahul Khedkar

A common supported approach is to keep the navigation state in the parent OmniScript and treat Step 2 as an edit mode rather than trying to make the Step 2 Continue button directly jump to an arbitrary step index. When Step 7 opens Step 2, store a flag such as returnToStep7 = true in the OmniScript data JSON. Then, on Step 2 Continue, your custom LWC can check that flag and invoke the parent OmniScript navigation logic to return to Step 7; otherwise, it follows the normal Step 2 → Step 3 flow. This avoids hard-coding unsupported step-index navigation inside the LWC and works well for an Edit → Return pattern. If you share your current custom LWC navigation code, I can show the exact implementation for your OmniScript.

Hi @Jayashree S

Yes, your understanding looks correct. This seems more like an org entitlement/provisioning issue than only a user permission issue.

You can check these points: 

1. Manage AI Agents
   • You already have this permission, so that part looks fine.
   • Salesforce lists Manage AI Agents as one of the main permissions for managing Employee Agents. Salesforce
2. Check Employee Agent entitlement
   • Financial Advisor Assistance requires the AgentforceEmployeeAgentAddOn.
   • It also requires the relevant Financial Services/Einstein entitlement. Salesforce
3. Why the permission may be missing
   • If Manage Agentforce Employee Agents is not appearing at all, there is a good chance the Employee Agent capability is not fully provisioned in the trial org.
   • Some Salesforce Financial Services Agentforce features specifically require both Manage AI Agents and Manage Agentforce Employee Agents. Salesforce
4. Check the org setup
   • Einstein Generative AI is enabled.
   • Agentforce is enabled.
   • Financial Advisor Assistance is enabled.
   • Required Financial Services licenses/add-ons are assigned.
5. If everything is enabled
   • I would raise a Salesforce Support case and ask them to confirm whether AgentforceEmployeeAgentAddOn / Employee Agent provisioning is active for that trial org.

So yes, I would first check the Employee Agent entitlement/provisioning , rather than spending more time only on permission sets. 

Thank you, 

Venkat Yadav.

@Ajay GM

No, there's no out-of-the-box setting in FSC Stage Management to prevent this. Stage Task generation fires on stage entry and doesn't check whether it already created those Tasks on a prior entry, so every re-entry spawns a fresh set. It also doesn't close prior Tasks. That's the product as built, not a misconfiguration, which is why you see both symptoms.  

Possible solutions:  

1. For duplication, add a record-triggered Flow that checks on Task creation whether an open Task with the same Subject already exists on that application (dedupe key: Subject + WhatId + status not Completed). If one does, don't create the duplicate. That's the guard the stage engine lacks.

2. For stale open Tasks, run a Flow on the stage change itself. When the application leaves a stage, find the open Tasks tied to that stage and close or reassign them per your rule. Forward movement usually means closing out the prior stage's tasks.

Hi Eeswarini, 

Since this worked before Winter '27 in the same design, this looks like a genuine regression in how the flow's finish behavior is being handled after the release — not a logic error in your flow. 

Background: "YOUR FLOW FINISHED" appears whenever a flow ends without a screen as its last executed element. If your flow's last step is an action (like ShowToast) rather than a screen, Salesforce falls back to this default finish screen. If this wasn't happening before Winter '27 with the exact same flow, something changed in how the platform determines "last executed element" or how quick-action-launched flows auto-close. 

Fixes to try: 

1. Add a final Screen element at the very end (after ShowToast), with header and footer removed, and use a Navigation-type action (e.g., NavigateToNext or similar Unofficial SF flow action) to auto-continue/close instead of a real screen the user sees. This is the standard workaround regardless of the regression, since it forces flow completion via a screen node rather than relying on default finish behavior. 

2. Check the Quick Action's flow settings on the record page — Winter '27 changed some Flow/Quick Action finish-behavior defaults; confirm "Reload page after finishing" or the flow's finish handler config still matches your prior sandbox setup. 

3. Compare flow versions/metadata between the working sandbox and the affected environment — if this environment got the Winter '27 upgrade first, check if a newer flow runtime setting differs. 

Given it's release-tied and reproducible, I'd also open a case referencing "screen flow finish behavior change post-Winter '27" — if this is a genuine platform regression, Salesforce needs it logged to fix it broadly, not just worked around per-flow. 

Reference: