Skip to main content
Solved

User confirmation options.

  • November 25, 2024
  • 5 replies
  • 65 views
Simon Vassallo
Forum|alt.badge.img+4

Hi All,

I am looking at removing a button presented in a notification to the user.

Specifically I want to remove a button so the user only has two options.

 

The button I want to remove from the notification shown is “Edit request” to avoid user confusion.

Currently selecting “Yes” instructs the middleware to execute a remote action against the machine and clicking “Yes” again will fail as the remote action cannot be executed more than once on the middleware system.

I cannot see anything in the CREST Event workspace that would refer to what looks like a consent option to proceed with the choice as shown above.

Best answer by Ajay Merchia

Just to close things off here…

The edit request button is a part of an event triggered path. Event triggered paths keep the edit request option in case the AI agent hallucinated something. It gives the user a chance to inspect, verify, and tweak the values before submitting to the API.

We don’t recommend removing it, and I don’t believe we have controls to allow for this.

We will consider this feedback for future iterations as we drive up AI performance and reliability

    This topic has been closed for replies.

    5 replies

    rgeroulo
    Forum|alt.badge.img
    • rgeroulo
    • Employee
    • November 25, 2024

    Hey ​@Simon Vassallo!

    Is this a Path use case or an Agentic Automation Plugin?

    Simon Vassallo
    Forum|alt.badge.img+4

    Hi ​@rgeroulo 

    It is an Event use case.

    Kind regards,

    Simon

    rgeroulo
    Forum|alt.badge.img
    • rgeroulo
    • Employee
    • November 26, 2024

    ​@Simon Vassallo 

    It is not possible to render buttons via an Event API. Per your screenshot, I assume this is a Path that hits an API endpoint and then you send an Event back to that same user from your iPaas tool.

    Currently, those 3 buttons in the Path will always be consistent when confirming an action with the user. Incase the slot that is extracted from the user is not correct, we will always want to allow the user to update the slot before firing off the API call. 

    I hope this helps!

    Best,

    Ryan

    Simon Vassallo
    Forum|alt.badge.img+4

    Thank you Ryan, one of the MW CS team is now assisting our request for the API consent buttons.

      Ajay Merchia
      Forum|alt.badge.img+2
      • Ajay Merchia
      • Community Manager
      • Answer
      • March 18, 2025

      Just to close things off here…

      The edit request button is a part of an event triggered path. Event triggered paths keep the edit request option in case the AI agent hallucinated something. It gives the user a chance to inspect, verify, and tweak the values before submitting to the API.

      We don’t recommend removing it, and I don’t believe we have controls to allow for this.

      We will consider this feedback for future iterations as we drive up AI performance and reliability

      Terms & ConditionsCookie settingsAccessibility statement