Flow Designer issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 07:25 PM
Hi Team ,
I have created a flow for a catalog item ,
As a admin when i was doing testing it is working fine , CTASK is getting generated .
When my client is doing testing , CTASK is not getting generated . Please find below snip .
what was the issue in flow i am not able to find ,
This is my flow properties,
How to resolve this issue can any one please me here .
Thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 07:34 PM
Hi,
Can you change "Run as" in Flow properties to "System User"?
MVP 2025 ✨
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 07:42 PM
What was the difference b/w - System user & user who intaites seesin,
If i select user who intaites seesin, why it is bheving like this .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 07:50 PM
When a Flow is executed with the "User who started the session" option selected, it runs in the context of the user who initiated the Flow. This means that any actions or operations performed within the Flow will be carried out with the permissions and access rights of that user.
On the other hand, when a Flow is executed with a system user, it runs in the context of that system user, which may have different permissions and access rights compared to the user who initiated the Flow.
The user who started the session typically has permissions and access rights limited to their own data and resources. They may not have permissions to access or modify certain data owned by other users or restricted resources.
System users, on the other hand, may have elevated permissions and access rights that allow them to perform actions or operations that regular users cannot. They may have access to sensitive data or system resources that are restricted to regular users.
When a Flow is executed with the "User who started the session" option selected, it can only access and manipulate data that the user has permission to view or modify. This means that the Flow may be subject to data visibility restrictions based on the user's role and permissions.
System users may have broader data visibility and access permissions, allowing them to access and manipulate a wider range of data and resources within the system.
If my answer helped you in any way, please mark it as correct/helpful 🙂
Regards,
Isaac Vicentini.
MVP 2025 ✨
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 07:54 PM
@nameisnani, in your case, if it was a requester who triggered the Flow, they indeed don't have permission to generate a Task, so the Flow must be executed as the System User.
MVP 2025 ✨