-
Notifications
You must be signed in to change notification settings - Fork 316
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
Agent Hierarchy / Tags in Streams API #621
Comments
This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment to keep this active. |
bump... |
This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment to keep this active. |
bump... |
We are also finding ourselves in need of reading/writing tags (configuration) using streams. |
Any update on this one? having access to tags from Streams would be very useful for us too |
Bump. |
This bug was first opened in December 2022, is there an update? Any timelines as to when ACS could provide the missing agent configuration data? We require this data as well, especially the hierarchy group data including the ARN and/or ID of the hierarchy group for all five levels. |
This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment to keep this active. |
bump... |
Would be very useful, ... |
Any update on this will be very helpful i have to use agent heirarchyGroupId, |
This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment to keep this active. |
bump ... |
Incomplete agent configuration data still being returned since hierarchy and tags have been introduced to the platform.
connect.version 2.4.2
connect.core.getAgentDataProvider().getAgentData()
The text was updated successfully, but these errors were encountered: