-
Notifications
You must be signed in to change notification settings - Fork 21
feat: add taskSource field to task in action center #1236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| } | ||
|
|
||
| task_source = { | ||
| "sourceName": "Agent", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should not be hardcoded, needs to be exposed as an argument and set by the escalation tool (or even above this)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, can make a constant internally, wherever it makes sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- would this value be the same across coded agents and lowcode agents?
- would there be any situations where the customer would want to opt out of this value being set?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed offline
- Fine to have the same value across coded and lowcode, provided the API contracts and fields remain the same
- None. Even if a future case comes, we can gate them from our backend, which stores the TaskSource data consolidated for Agents, Maestro and RPA workflows
9e1dd1e to
35ead0a
Compare
Add taskSource field to task in action center