Hello, we are hosting a community webinar session on testing Flows here - https://www.linkedin.com/events/7486444337514360832?viewAsMember=true
. come one come all.
Escrever um comentário...
0/9000
Grupo
Flow Orchestration
Hi team! Has anyone ever faced the following issue?
I have been working with the new
Flow Approval Processon the Case object. I was able to correctly implement an approval process that is assigned to a Queue. This Queue contains a Public Group where I assign users to. I've also added the Work Guide component to a Flexipage, so assigned users can approve or reject the approval process.
This has been working as expected on lower environments. Nonetheless, in our Production org,
assigned users to the Public Group cannot see the Work Guide on the Flexipage.
I've already verified the following:
1. Work Guide component is correctly added to the Flexipage.
2. User is correctly assigned to the Public Group.
3. Flow Approval Process is Active.
4. Queue that assigns the Public Group has 'Case' and 'Orchestration Work Item' assigned as supported objects
Are there any permissions that I might be missing for this weird situation to be happening? What I'm finding specifically weird is that it works in lower environments, but not on Production.
1 resposta
Try following Troubleshooting Step:
Log in as one of the affected users, navigate to the App Launcher, and search for Orchestration Work Items
.
1. If they cannot see the object, it's a Profile/Permission Set issue (Check The Fix for Issue#1)
2. If they can see the list view but it's empty (or they can't see the specific item for that Case), it's a Sharing/OWD issue (Check The Fix for Issue#2).
The Fix for Issue#1: Ensure the users' Profile or assigned Permission Set has Read and Edit permissions on the Orchestration Work Items object.
The Fix for Issue#2: Go to Sharing Settings and check the OWD for Orchestration Work Item. If it is set to Private, users won't see the work guide unless they are explicitly shared into the record. Setting it to Public Read/Write (if your security policy allows) is the easiest way to ensure Queue/Public Group members can see their tasks.
We are using flow orchestration heavily for some new product approvals. After the end user has submitted the approval, while it's waiting to be approved, is there some way I can show them who the current assigned group is, so that they know who to follow up with if they have questions. we have a few different groups depending on different criteria.
3 respostas
Hi @Brad Bennion Hopefully you found a solution but if not (and for anyone else looking into this) the Spring 25 release introduced a specific Approval Orchestration that allows you to add an 'Approval Trace' component to a record page. There's also a central app for users to be able to view all of their approvals. It has some other useful features specific to approvals too Automate Your Approvals with Flow Approval Processes
I'd imagine you could rebuild your orchestration using the existing flows you've already built and it would then be able to make use of the new features (you might need to update the API settings for the flows to be sure).
David
Hey everyone,
I have an error that just popped up which is now preventing me from saving my Orchestration - "Required fields are missing: [TargetName]". While this error is non-descript I seem to have broken something in the core of the Flow because if I close it out and then open my last saved version (and only version), modify something unimportant such as a description, then try saving the flow I get the same error. So somehow the Flow let me save it when the error existed and I now need to abandon this Orchestration and start from scratch as I can't figure out what [TargetName] is referring to.
Has anyone run into this issue yet?
2 respostas
@Riley Schill we identified what was causing this problem and it will be fixed in our next release. In the meantime, you need to go through each interactive step in your orchestration and switch the exit condition to "When the specified evaluation flow returns true" then switch it again to "When all steps have been marked complete".
This should clear out the bad data. Please let me know if it solves your problem.
Forum Ambassador
publicou em Dynamic Forms for Flow (beta)As a Flow Builder,
I want Labels and API Names to be consistent on Screen Flows,
So that I know what to do
Please upvote here; https://ideas.salesforce.com/s/idea/a0B8W00000QcijGUAR/make-api-name-and-label-behaviour-consistent-for-screen-flows
#Salesforce #Salesforce Admin #Salesforce Developer #Flow #CRM Configuration #TrailblazerCommunity #AwesomeAdmins
@* Salesforce Developers * @* Salesforce Platform * @* Salesforce Administrators * @Flow Toolbelt @Flow Orchestration @Flow Reactive Screen Components (GA) @Flow for Nonprofit Admins @Lightning Flow Discussions @Salesforce Flow Automation @Screen Flow Screen Action
1 comentário
Thanks Tom - I responded to your Idea to provide my thoughts / reasons for the inconsistency.
Hello, it looks like we are not able to disable the Step assignment notification and replace with a custom notification.
Is there any way to at least change the notification Sender and Email template? Our Orchestration would be customer facing and Salesforce branded notifications will not work for us.
Edit: Adding SF Idea that was mentioned by Tom Bassett below.
Thank you
fyi @Jacob Carroll
7 respostas
We are looking to adopt Orchestration for Rapido Cloud.
This simple issue is a showstopper and hinders us from adopting the whole feature.
I aim to trigger this flow with a quick action when the Opportunity status is "Closed-Won," capture a date entered by the user, and then route to a subflow for Contract generation. How can I set up the flow to populate fields (including the captured date) in the new Contract? Any insights or examples would be invaluable. Thank you for your help!
7 respostas
Manoj Nambirajan (Dell Technologies)
Forum Ambassador
@Cássia Queiroz i can only think of a URL hacking approach which should work in lightning experience.. below link can help
https://theblogreaders.com/url-hacking-back-salesforce-lightning-experience-spring-20-release/
Please Read: Posting Questions to Receive Support
Hi all, I can see that you've been posting your questions here on the Developer Forums Migration Support Hub when you're stuck and need help with your development.
However, this group is for the migration only and there are not many people here; you want your post to have the widest coverage possible to get answers from experts in the community.
Posting a Question
- Locate the correct group where the members are experts in the field for which you have a question. For example, you can always post your question on the @* Salesforce Developers * group; you can also use @Lightning Web Components @Flow Orchestration @Agentforce Vibes IDE and lots more!
- Once you find your group, post your question in that group's feed.
- Add topic tags to help people understand what you're asking about, e.g., #MuleSoft Anypoint Code Builder, #Apex, or #LWC.
There is a quick walkthrough video which goes over this process by @Juspreet Kaur; have a look!
4 comentários
Hey folks, I'm wondering if this may be a standard limitation, or if I´ve got something wrong. I tried to assign a work item to a standard event record and received the following error in my orchestration flow.
Info
Error Occurred:
Context Record ID: id value of incorrect type: 00U01000003IAUwEAO
As you can see by the first three characters, the value being passed in is an Event record, and you will have to trust me that the record does exist in my org. I know we cannot relate a standard task to an event. Perhaps the Work Item object has the same limitation. I haven´t found specific documentation for this scenario.
4 respostas
Thank you both for your feedback. A bit more investigation confirmed my suspicions that this is a limitation. Per the Salesforce Developer object reference guide for Flow Orchestrator Work Items, the related record Id cannot be an Event.