- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2025 01:15 AM
The management system in the company requires that some of the users should notice that some instance happened but does not get involve the instances.
I've tried to view on the watchlist but find that it is not able to track whether the users confirmed on the records or not. Getting emails notification is not good enough for the management system. The company requires that the user should see the instance and marked the instance as seen/noticed.
Thus, I now need a button for some users that I can mark they've seen/noticed the records and continues to the approval state. I've also tried the approval button but since that these users should not be able to reject, the reject button is not what I want.
Is there any method I can pause the flow and custom a button to mark that users have seen the instance, after the users are marked seen, the flow continues on usual approval state?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2025 03:14 AM
Hey cindy,
Why do you not use a simple approval record to perform this action? You could ask for approval from this user before moving forward. The advantage is, that the approval of the user is stored in the system. This allows a better history tracking, than just a button click.
A more complex solution includes the new action Wait For Message action. I never tried it, but if you have enough experience you could try to build a button, that posts a message, that the flow continues to work.
I hope my anser helps
Kind regards
Sebastian

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2025 03:14 AM
Hey cindy,
Why do you not use a simple approval record to perform this action? You could ask for approval from this user before moving forward. The advantage is, that the approval of the user is stored in the system. This allows a better history tracking, than just a button click.
A more complex solution includes the new action Wait For Message action. I never tried it, but if you have enough experience you could try to build a button, that posts a message, that the flow continues to work.
I hope my anser helps
Kind regards
Sebastian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2025 06:00 PM
Hi Sebastian,
The reason is that the user should not be able to reject the incident, the reject button should be disable in this flow. I am trying now to make the reject button invisable.
However, the Wait For Message action seems like a simpler solution to me. I will try on that!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2025 11:26 PM
Perfect. I would be interested to hear an update, if the wait for message action worked for your use case.