You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when a request is created it has a status of "pending", it must then be submitted to a vote which, but because the submission happens in the voting app and not directly in the token request app we do not have an event to process and update to a "submitted" status... which is confusing for users as they can't easily determine which requests have already been submitted.
It may also be possible to update from submitted to rejected based on the outcome of the vote, depending on the capability of the forwarder api that Autark has been working on to improve cross application ux.
Currently when a request is created it has a status of "pending", it must then be submitted to a vote which, but because the submission happens in the voting app and not directly in the token request app we do not have an event to process and update to a "submitted" status... which is confusing for users as they can't easily determine which requests have already been submitted.
It may also be possible to update from submitted to rejected based on the outcome of the vote, depending on the capability of the forwarder api that Autark has been working on to improve cross application ux.
As far as I'm aware the only documentation available at the moment is in this update https://blog.autark.xyz/agp-19-close-out-agp-73-kick-off/ but we can ask the autark guys to point us in the right direction and advise.
The text was updated successfully, but these errors were encountered: