Skip to Content
Product Information
Author's profile photo Nina Kou

Release Status on Manage Customer Returns App

The ‘Release Status’ a concept existed on Manage Customer Returns app, which in accelerated return header level is used to identify if the accelerated return is released, and subsequent document like returns delivery is created, then we can go ahead for next step. It is coming from the accelerated return item. If release status is ‘Released’ for all items, the release status on header is ‘Released’; if release status is ‘Released’ for one of the items, the release status on header is ‘Partially Released’; if release status is ‘Not Released’ for all items, the release status on header is ‘Not Released’. According to the release status, you could determine the next process. Once the status is released, the item will be disabled and cannot the changed anymore.

Before CE2111, when you click ‘Save and Release’ on the Manage Customer Returns app, no matter if the subsequent document is created, the release status became released. It will cause an issue that error may happened when creating subsequent document, the subsequent document indeed does not be created, but user does not have opportunity to change the item or fix it anymore.

From CE2111, the logic for release status is enhanced. If subsequent document is created would be checked when set release status. If the subsequent document is not created, the release status is ‘Not Released’. But please note, there has time spent for creating subsequent document, depending on the system performance (May 2 or 3 seconds). If you found the status has not changed to ‘Released’ after you click ‘Save and Release’, please refresh the page seconds later or move to process flow to check if subsequent document is created.


Release Status on Header Level


Release Status on Item Level

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Vivian Mett
      Vivian Mett

      Any made purchase will still be recorded even when a user makes a refund, and actually gets the refund. The same is true when you (the developer/app owner) issue a refund/revoke request for the in-app product.

      The only difference will be the purchase's "purchaseState". The problem here with Google's Billing Library is that they mask this "purchaseState" value in the purchase.getPurchaseState() call to either PENDNG or PURCHASED state. See in the decompiled code:

      public int getPurchaseState() { switch(this.zzc.optInt("purchaseState", 1)) { case 4: return 2; // PENDING default: return 1; // PURCHASED