Flow design: Add value in task variable through Flow design
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 06:45 AM
In my catalog item, there is a List collector variable "Mass Folder Selection" which is just to add file folder path to get access. It can add any amount of path.
For each path, there were be individual approvals.
There are two TASK variables. "Mass folder selection" and "Rejected Folder"
The Path which are approved will stay in "Mass folder selection" and the path whose approval was rejected will be added to "rejected folder" variable. And the Task will be created.
Can anyone help me how can I achieve that in Flow design?
I achieved till Parallel approval of each Path. But I don't know how to add value in Task variable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 10:10 PM
No. This is in different instance and using workflow. I need to create exact same thing in new instance using FLOW DESIGN.
After getting approved/Reject, the path is not getting added to its respective folder. I need help with that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 10:21 PM
so what did you start with and where are you stuck in flow?
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 10:37 PM - edited 03-23-2025 10:38 PM
Why are you asking so many questions? I have already explained my requirement many times that I want to know how to add value in catalog variable. If you can help please do. Otherwise stop replying and let others help.
Please dont ask same question over and over again.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2025 12:41 AM
Hi, yes your requirement is beginning to clear, but your process is still not clear to me.
Why would you need to move rejected paths to a different variable.
What's the purpose of that?
I would recommend an entirely different approach, generate a task to fulfill a requested folder once a folder gets approved. It will instead generate one task for each approved folder.