- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi,
I tend to think of SCTASKS as internal process tasks, which is not intended for communication with the Requestor. If a process is defined, and each task is clearly defined, then what communication is needed from the tasks to the Requestor?
I mean, if the Requestor ordered a product X, then he/she is probably not interested in knowing that the different SCTASKS handling components to deliver product X is finished. They only want to know when to recieve X.
If you're really going forward with this, it's a simple thing to create a Flow that generates an additional comment (or other email content) containing data from all the tasks when a certain criteria (change on the RITM) happens.