Replies: 2 comments 2 replies
-
And here is a version of the JSON which we have started to manually configure using the drag and drop editor, but in which the new damage report components are not yet connected to anything: |
Beta Was this translation helpful? Give feedback.
2 replies
-
Thanks. I now want to do two things simply
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have been trying to implement this JSON file via GMS both manually using the UI, and also via docker, but not having much luck. Can we get some guidance on how to implement our workflow either using the workflow manager, or using the attached code. We basically want to create a Damage Report function that the PP can initiate, and then the VVB can approve, which leads to a token identified in a Damage Report schema being retired. It should have similar functionality to a Monitoring report in the VM0044 methodology (with the ability to revoke etc) but result in the Owner retiring a previously minted token. What is the best way to do this (using the VM0044 workflow/JSON code and the enclosed schema, which we have added alongside the other VM0044 schemas)?
json file for new policy v2.json
schemas_1712270189626.xlsx
Beta Was this translation helpful? Give feedback.
All reactions