Is your feature request related to a problem? Please describe.
There are use cases where the history of operations that update the attributes of a token is referenced for auditing purposes.
The information currently held in update_token TBL is the history of the transaction execution, not the history of the operation (and not the history of the POST parameters received.)
Because of this, records with trigger=Update in the update_token TBL will not be used.
When a request is made to the issue token or update token attribute APIs, the value of the POST parameter needs to be stored and saved as a history of the operation.
Describe the solution you'd like
Add a new TBL to hold the history of the update operations for the token attribute, holding the POST parameter for each API request.
Not to store data to update_token table when token attribute update API is called.
Is your feature request related to a problem? Please describe.
update_token
TBL is the history of the transaction execution, not the history of the operation (and not the history of the POST parameters received.)trigger=Update
in theupdate_token
TBL will not be used.Describe the solution you'd like
update_token
table when token attribute update API is called.