feat: add asset recipient support for guardrails#432
Conversation
60a4237 to
4e6b3c2
Compare
| app_folder_path: str, | ||
| version: int, | ||
| assignee: str, | ||
| recipient: AgentEscalationRecipient, |
There was a problem hiding this comment.
Do we have a similar class, but not tied to the low coded agent? We tried to not use such objects here. Instead we mapped from agent-related objects to core objects, in the guardrails_factory
There was a problem hiding this comment.
At the moment there's no core recipient object available. As discussed with @ctiliescuuipath and @dianapirvulescu, this type of object will be added in their changes regarding adding support for groupId and userId, where they'll need to make resolve_recipient_value return an actual object to preserve its type (not just a string).
There was a problem hiding this comment.
reading you comments right now I was thinking if should be a better place to convert resolve the assets into guardrails_factory. @dianagrecu-uipath do you know if assets will be used for guardrails also in coded agents ?
There was a problem hiding this comment.
@ctiliescuuipath no sorry, I don't know if assets will be used in coded agents as well
There was a problem hiding this comment.
@valentinabojan @ctiliescuuipath are you good with merging these changes?
4e6b3c2 to
9b0d817
Compare
cb9f1b5 to
dd50883
Compare
Add Asset Recipient support for Guardrails