My Code stopped working on Commercial Portal, still works on FedRamp Portal

Here's the scenario. I have 2 Approvers (For example, Bob and Mary). Bob has just 1 signature field. Mary has a signature field and a Label. Bob signs first. Before Mary signs I programmatically update her Label field so when she goes to sign she sees the Label Value I inserted. Mary then signs. On the FedRamp Portal (https://signer-sandbox-gov.esignlive.com) I am able to update a field's value after Bob's signs using this POST REST call: URL = https://signer-sandbox-gov.esignlive.com/api/packages/ybNmjNKYIQy8KyTO-Yjvv6JL2YM=/documents/ReviewForm/approvals/MySigAO1/fields/MyField1 JSON = {"id":"MyField1","value":"Some very important information"} The process of learning how to do this was explained in an earlier Topic of mine titled "Looking for options for a multistep signing process" Sadly, this does not work on the Commercial Portal anymore. It stop working in early fall of 2016. I get this error when I try "The remote server returned an error: (403) Forbidden." On both Commercial and FedRamp, I'm able to do this "Update an existing field related to an existing approval" PUT /packages/{packageId}/documents/{documentId}/approvals/{approvalId}/fields/{fieldId} (From REST API guide). Unfortunately this only works if the document is in DRAFT mode, and a document can't be put in DRAFT mode if someone already signed it. Besides this doesn't really update an existing field, it just adds a new one. My app is only going to run on the FedRamp Portal, but I'm worried that it's code will be updated to work like the Commercial portal and my app will stop working. So can you either fix this issue on Commercial or verify that it will always work on FedRamp Thanks Jim O