I wanted to do something similar, and couldn’t figure it out. My blueprint only work-around was:
- Make an interface to define the names of the callback functions. Using the OP example, the names of the functions would be “OnCancel” and “OnConfirm”
- Pass an instance of the interface to the node. In the example, the promptUserForConfirmOrCancel node
- Have the node call the interface functions at the appropriate times
Not a great solution, as you can’t look at the blueprints and see clearly when the callback functions get called, and it constrains the developer to which function names can be used as callbacks.