Closed rootelement closed 3 years ago
Also, after i fixed the terms in the DB and went to edit it, the agreeability type is correct, but it doesn't show the field:
I assume editing if the field worked wouldn't update that either. The API handles the docusignTemplateId in the POST and PUT requests, so that shouldn't be the problem here:
if (termsOfUse.docusignTemplateId) {
await TermsOfUseDocusignTemplateXref.create({
termsOfUseId: created.id,
docusignTemplateId: termsOfUse.docusignTemplateId
})
}
@rootelement it seems like a Terms API issue, because Admins App sends docusingTemplateId
in the POST request:
But Terms API doesn't return it the response:
After I'm trying to load created Terms I get an error from API so it's hard to test the second issue with the missing field:
But if I open any existent Terms with correct docusignTemplateId
(ex: http://local.topcoder-dev.com:3001/#/index/terms/edit/7245bb7d-d7c9-45a0-9603-d5ff05af0977) this field is shown correctly to me:
Ah, I've got the second issue https://github.com/topcoder-platform/admin-app/issues/171#issuecomment-723318461.
If it happens to you on PROD but not on DEV, then AGREE_FOR_DOCUSIGN_TEMPLATE
might be misconfigured on PROD. It should point to the id of DocueSignable Aggreability Type in the PROD DB.
Fixed. Thanks!
Steps to Reproduce
If you try to edit that challenge, you'll see there's no docusign id returned.
It looks like the POST on creating a challenge is not sending the docusignId value from the field. I filled in these values:
And this was the POST body from the console:
Notice there's no
docusignTemplateId