For one of the BC Gov IAS testing cases we delete the OOB record so an agent can accept the same invitation again. In that I'd added a call for the AFJ agent to do this.
It's very bare bones compared to the other connection management calls, doesn't do a defer to wait for state changes, but that may(?) be appropriate for a simple delete record call the way this is invoking AFJ oob.deleteById
Would be good to pull this simple call in at least so the BCGov IAS tests don't need manual/forked Akrida changes to run, if more feature/additional complexity needed could iterate on it later.
For one of the BC Gov IAS testing cases we delete the OOB record so an agent can accept the same invitation again. In that I'd added a call for the AFJ agent to do this.
It's very bare bones compared to the other connection management calls, doesn't do a defer to wait for state changes, but that may(?) be appropriate for a simple delete record call the way this is invoking AFJ
oob.deleteById
Would be good to pull this simple call in at least so the BCGov IAS tests don't need manual/forked Akrida changes to run, if more feature/additional complexity needed could iterate on it later.