Hi Adam
Thanks for pointing this out. What probably should happen is that we should align AgreementAuthorization with the existing Authorization schema, which does have the fields you are interested in (take a look at the Quote API which uses this schema).
I have opened a JIRA issue for this, of course I cannot promise if and when this will be dealt with.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Jul 21, 2020 11:43
From: Adam Augustyn
Subject: TMF651 AgreementAuthorization
Hi,
I have problem with AgreementAuthorization and the field signatureRepresentation.
In the documentation the field is described as: "A string. Indication that represents whether the signature is a physical paper
signature or a digital signature."
So for me it sounds like a description of the way of signing (paper or digital).
But in the example there is something like:
{
"date": "2018-04-24T00:00Z",
"signatureRepresentation": "Dr Mabuse",
"state": "approved"
}
And it looks like the name of the person who probably signed that.
Do you have any sugestions how to deal with that field? In my opinion information about the person who authorized something is more relevant than the way of signing.
Best Regards,
------------------------------
Adam Augustyn
Comarch S.A.
------------------------------