Good afternoon.
We set up automatic payment binding, respectively, set the action "Switch the stage if a payment is received", and it turns out that the system proceeds to this stage even when it has already passed before.
In more detail: We went to the "details sent" stage, then the payment came in and the system tied it up and transferred it to the next stage of the "Payment received" BP, then we go through the BP and the system constantly transfers the BP to the "Payment received" stage, how to set it up happened once?
Good afternoon. We set up automatic payment binding, respectively, set the action "Switch the stage if a payment is received", and it turns out that the system proceeds to this stage even when it has already passed before. In more detail: We went to the "details sent" stage, then the payment came in and the system tied it up and transferred it to the next stage of the "Payment received" BP, then we go through the BP and the system constantly transfers the BP to the "Payment received" stage, how to set it up happened once?
This action is set in steps: "Details sent" "The order has been sent" "Order received" "Deferment of payment" It turns out that if the payment is received at the "details sent" stage, then the system will continue to transfer to the "Payment received" stage when going to the above stages.
This action is set in steps:
"Details sent"
"The order has been sent"
"Order received"
"Deferment of payment"
It turns out that if the payment is received at the "details sent" stage, then the system will continue to transfer to the "Payment received" stage when going to the above stages.
Hmm ... a strange situation, it seems according to the settings of actions - this should not be. Judging by the comments, the switches were made on behalf of different users. If you install the "OneBox User Logs" application - we can see where the stage change was initiated from - and perhaps get a more specific answer.
Hmm ... a strange situation, it seems according to the settings of actions - this should not be.
Judging by the comments, the switches were made on behalf of different users.
If you install the "OneBox User Logs" application - we can see where the stage change was initiated from - and perhaps get a more specific answer.
Andrey wrote: In this action, nowhere is it possible to check the box "do not proceed if you have already been at this stage of the BP"
Probably because it's not there.
[quote]
Andrey wrote:
Installed the "OneBox User Logs" application
An example of a translated order for a second BP stage http://box.agro-him.com.ua/23107/
[/quote]
http://box.agro-him.com.ua/app/history/orders/23107/?systemchange=1&filter2_key=valueold&filter2_type=search&filter2_value=&filter3_key=valuenew&filter3_type=search&filter3_value=&fieldkey=&filtercdatefrom=&filtercdateto=
now you can see that it was this action that switched 1 time
[quote]
Andrey wrote:
In this action, nowhere is it possible to check the box "do not proceed if you have already been at this stage of the BP"
[/quote]
Probably because it's not there.
Read the description of the action - it says "The action once a minute looks for a payment with the amount (process amount + shipping cost) taking into account the error and transfers to the status if such a payment was in progress." You have a switching action on receipt of payment added at several stages http://box.agro-him.com.ua/admin/shop/workflowstatus/352/action/new/http://box.agro-him.com.ua /admin/shop/workflowstatus/353/action/new/ http://box.agro-him.com.ua/admin/shop/workflowstatus/354/action/new/ Actually, when you switch to one of the statuses, it checks by the minute crone that the payment was made - and makes the switch. Correct setting of the BP (leave the action at the pending payment stage) will solve your problem.
[quote]
Andrey wrote:
http://box.agro-him.com.ua/23107/
This is the third time transferring to received payment.
[/quote]
Read the description of the action - it says "The action once a minute looks for a payment with the amount (process amount + shipping cost) taking into account the error and transfers to the status if such a payment was in progress."
You have a switching action on receipt of payment added at several stages http://box.agro-him.com.ua/admin/shop/workflowstatus/352/action/new/ http://box.agro-him.com.ua /admin/shop/workflowstatus/353/action/new/ http://box.agro-him.com.ua/admin/shop/workflowstatus/354/action/new/
Actually, when you switch to one of the statuses, it checks by the minute crone that the payment was made - and makes the switch.
Correct setting of the BP (leave the action at the pending payment stage) will solve your problem.
I didn’t quite understand “leave the action at the stage of waiting for payment”, the task for us, when receiving payment, is to transfer to the BP stage “payment received”, there are no problems on the BP where there is no deferred payment, one action is set at the “Details sent” stage and, accordingly, when the funds arrive , the system ties up and transfers to the stage "Payment received" - the issue is resolved. But there is a BP where there is a deferred payment, and payment can enter at any of the stages, respectively, we have set 4 actions at those stages when payment can enter, what should be the action so that the system translates to "Payment received" only once and if payment is already there, then nothing happened regardless of the BP stage?
I didn’t quite understand “leave the action at the stage of waiting for payment”, the task for us, when receiving payment, is to transfer to the BP stage “payment received”, there are no problems on the BP where there is no deferred payment, one action is set at the “Details sent” stage and, accordingly, when the funds arrive , the system ties up and transfers to the stage "Payment received" - the issue is resolved.
But there is a BP where there is a deferred payment, and payment can enter at any of the stages, respectively, we have set 4 actions at those stages when payment can enter, what should be the action so that the system translates to "Payment received" only once and if payment is already there, then nothing happened regardless of the BP stage?
Andrey wrote: I didn’t quite understand “leave the action at the stage of waiting for payment”, the task for us, when receiving payment, is to transfer to the BP stage “payment received”, there are no problems on the BP where there is no deferred payment, one action is set at the “Details sent” stage and, accordingly, when the funds arrive , the system ties up and transfers to the stage "Payment received" - the issue is resolved.
Andrey wrote: But there is a BP where there is a deferred payment, and payment can enter at any of the stages, respectively, we have set 4 actions at those stages when payment can enter, what should be the action so that the system translates to "Payment received" only once and if payment is already there, then nothing happened regardless of the BP stage?
I see 2 options: 1. rebuild the business process in such a way that after the "Payment received" stage, you do not have transitions to stages with the action of switching again upon receipt of the same payment 2. finalize the setting "Do not switch to the stage if the process was already at the stage before" in this action - it will take 1 hour
[quote]
Andrey wrote:
I didn’t quite understand “leave the action at the stage of waiting for payment”, the task for us, when receiving payment, is to transfer to the BP stage “payment received”, there are no problems on the BP where there is no deferred payment, one action is set at the “Details sent” stage and, accordingly, when the funds arrive , the system ties up and transfers to the stage "Payment received" - the issue is resolved.
[/quote]
I repeat once again:
[quote]
Tyndyk Maxim Vadimovich wrote:
You have a switching action on receipt of payment added at several stages http://box.agro-him.com.ua/admin/shop/workflowstatus/352/action/new/ http://box.agro-him.com.ua /admin/shop/workflowstatus/353/action/new/ http://box.agro-him.com.ua/admin/shop/workflowstatus/354/action/new/
Actually, when you switch to one of the statuses, it checks by the minute crone that the payment was made - and makes the switch.
[/quote]
[quote]
Andrey wrote:
But there is a BP where there is a deferred payment, and payment can enter at any of the stages, respectively, we have set 4 actions at those stages when payment can enter, what should be the action so that the system translates to "Payment received" only once and if payment is already there, then nothing happened regardless of the BP stage?
[/quote]
I see 2 options:
1. rebuild the business process in such a way that after the "Payment received" stage, you do not have transitions to stages with the action of switching again upon receipt of the same payment
2. finalize the setting "Do not switch to the stage if the process was already at the stage before" in this action - it will take 1 hour
Andrey wrote: Previously, we talked about the refinement of other points, where can I write the entire list of necessary improvements?
For separate improvements, create separate topics.
[quote]
Andrey wrote:
Previously, we talked about the refinement of other points, where can I write the entire list of necessary improvements?
[/quote]
For separate improvements, create separate topics.
You should have been invoiced for this revision. If there are other topics where you need to invoice - write a question in the relevant topics.
[quote]
Andrey wrote:
Who to contact for billing?
[/quote]
You should have been invoiced for this revision.
If there are other topics where you need to invoice - write a question in the relevant topics.
Improved the setting "Do not switch to a stage if the process was already at a stage earlier" into the action "Switch a stage if a payment is received"
Improved the setting "Do not switch to a stage if the process was already at a stage earlier" into the action "Switch a stage if a payment is received"
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Donate
You don't have enough funds in your account Top up