Test successful in folio-snapshot

 creating additional stories sounds logical to me as the scope of this story should only including Canceling order.

One correction to your statement above for story 2:

2. Story : Update logic of the payment status for "Cancel" ongoing order flow
When closing ongoing order with reason for closure NOT EQUAL to canceled. Payment status is set to Fully paid.
When closing ongoing order with reason for closure EQUAL to canceled. Payment status is set to Canceled.

Actually I think that was my error from the post above yours. I have corrected it in both places. When ongoing order is canceled the Payment status would be set to Canceled unless it is already in a "Resolved" status like 'payment not required' as per our previous stories.

Hi

When the order is canceled or closed, the logic of changing payment status for ongoing orders works differently than you suggested above.

We obviously already got confused in the test cases that are the scopes of this story. Move over Case 2 was added by me after questions about "ReOpen" flow.

I propose to remove the Case 2 from the current story and create 2 new ones:

1. Story( Case 2) : Update POLs payment status and encumbrances for "ReOpen" flow after cancelling order.
I propose to remove case 2 from the current story, as it relates to the ReOpen logic and clarify the test cases for encumbrances and payment status for both types of one-time and ongoing orders.

2. Story : Update logic of the payment status for "Cancel" ongoing order flow
When closing ongoing order with reason for closure NOT EQUAL to canceled. Payment status is set to Fully paid.
When closing ongoing order with reason for closure EQUAL to canceled. Payment status is set to Fully paid.

After getting a more accurate picture of the test cases, Nina will go through them again and mark the ones that don't work as expected. Then back-end proceed with the implementation.

What do you think?

Thank you in advance

 Case 2 already describes all scenarios where the encumbrance status should be set to Unreleased. The encumbrance status would only be Released if the Payment status = Fully paid OR Canceled.

The problem this may cause is that when we Close an ongoing order FOLIO is releasing the encumbrances. However, the payment status could still be ongoing because we do not automatically change it to "Fully paid". We may need to add this logic so we can rely exclusively on the Payment status to release encumbrances. This would mean:

When closing ongoing order with reason for closure NOT EQUAL to canceled. Payment status is set to Fully paid.

When closing ongoing order with reason for closure EQUAL to canceled. Payment status is set to Canceled.

 would this make sense to you? If so I believe we will need a separate story for this. 

Otherwise it will be possible to have a Closed Ongoing order with a payment status of Ongoing and encumbrances status of Released. Would this cause a problem currently?

Hello thanks for your answer! So move In review. And could you please update CASE 2 description consider with "Release" Encumbrance status if order has related approved or paid invoices?