You need to understand exactly how it works.
I have 2 orders. They are at different stages of the same process.
Each step has an action with a checkmark next to Change the process step when there are enough products in stock
[file]849[/file]
By what logic does it distribute? It takes all the orders at this stage, scatters them one by one (by creation date), then proceeds to the next stage and does exactly the same?
Or does it check all stages of all business processes at once, where are these actions and scatter products by the date the order was created?
The thing is, at the stage where the action to reserve products should be transferred, that is, all orders will definitely not have enough products that have been added to the warehouse. Conventionally, there are more orders than a product, and you need to understand by what logic it will scatter these products. Tell me please.
+ What date does it take? The date the order was created or the date you moved to the stage with this action
You need to understand exactly how it works. I have 2 orders. They are at different stages of the same process. Each step has an action with a checkmark next to Change the process step when there are enough products in stock
By what logic does it distribute? It takes all the orders at this stage, scatters them one by one (by creation date), then proceeds to the next stage and does exactly the same? Or does it check all stages of all business processes at once, where are these actions and scatter products by the date the order was created? The thing is, at the stage where the action to reserve products should be transferred, that is, all orders will definitely not have enough products that have been added to the warehouse. Conventionally, there are more orders than a product, and you need to understand by what logic it will scatter these products. Tell me please. + What date does it take? The date the order was created or the date you moved to the stage with this action
If we are talking about launching once a minute / hour, then actions are selected according to sorting separately by status. For example, you have 2 statuses on which this action is set - and where it is set higher (and possibly what was added earlier) - that will work initially. Then it takes the processes in the given status, sorted by ascending ID, and processes them one by one.
If we are talking about launching once a minute / hour, then actions are selected according to sorting separately by status.
For example, you have 2 statuses on which this action is set - and where it is set higher (and possibly what was added earlier) - that will work initially.
Then it takes the processes in the given status, sorted by ascending ID, and processes them one by one.
Tyndyk Maxim Vadimovich Administrator wrote: For example, you have 2 statuses on which this action is set - and where it is set higher (and possibly what was added earlier) - that will work initially.
It turns out if I have 2 stages - New order ( it has stage id = 10 ) - waiting for availability ( it has stage id = 11 ) And at these 2 stages, this action is set with the same settings and the checkbox "do not transfer if there are earlier orders" is checked. Then it will first take all orders to the "new order" stage, and then it will go "waiting for availability" and also begin to transfer with sorting according to the id section of each stage taken?
[quote]
Tyndyk Maxim Vadimovich
Administrator wrote:
For example, you have 2 statuses on which this action is set - and where it is set higher (and possibly what was added earlier) - that will work initially.
[/quote]
It turns out if I have 2 stages
- New order ( it has stage id = 10 )
- waiting for availability ( it has stage id = 11 )
And at these 2 stages, this action is set with the same settings and the checkbox "do not transfer if there are earlier orders" is checked.
Then it will first take all orders to the "new order" stage, and then it will go "waiting for availability" and also begin to transfer with sorting according to the id section of each stage taken?
Gubko Alexander Sergeevich wrote: It turns out if I have 2 stages - New order ( it has stage id = 10 ) - waiting for availability ( it has stage id = 11 ) And at these 2 stages, this action is set with the same settings and the checkbox "do not transfer if there are earlier orders" is checked. Then it will first take all orders to the "new order" stage, and then it will go "waiting for availability" and also begin to transfer with sorting according to the id section of each stage taken?
If both actions are set first in the step - they have the same sort - then by status order. And if, for example, at the stage with id = 11 it is set first, and at the stage with id = 10 it is set third, then it will first work out what is set above (it has more priority).
[quote]
Gubko Alexander Sergeevich wrote:
It turns out if I have 2 stages
- New order ( it has stage id = 10 )
- waiting for availability ( it has stage id = 11 )
And at these 2 stages, this action is set with the same settings and the checkbox "do not transfer if there are earlier orders" is checked.
Then it will first take all orders to the "new order" stage, and then it will go "waiting for availability" and also begin to transfer with sorting according to the id section of each stage taken?
[/quote]
If both actions are set first in the step - they have the same sort - then by status order.
And if, for example, at the stage with id = 11 it is set first, and at the stage with id = 10 it is set third, then it will first work out what is set above (it has more priority).
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