Leave a message in this thread and the user's contacts will be shown to you
Since this morning no process is created for the supplier. This action stopped working at the process stage:
[file]20752[/file]
[file]20753[/file]
Gives an error:
[file]20752[/file]
[file]20753[/file]
Here is the BP: https://crm.sportmarket.ua/admin/shop/workflowstatus/4968/action/new/
[file]20752[/file]
[file]20753[/file]
I understand that this is some kind of bug after the update tonight, not only we have it, for example: https://1b.app/ru/forum/supplier-and-price-list-management/17314-ne-sozdaetsya -zakaz-postavshchiku/
[file]20752[/file]
[file]20753[/file]
The work is worth it. Please fix it immediately!
[file]20752[/file]
[file]20753[/file]
Thank you!
[file]20752[/file]
[file]20753[/file]
OneBox: crm.sportmarket.ua
[file]20752[/file]
[file]20753[/file]
Since this morning no process is created for the supplier. This action stopped working at the process stage:
I think it would be right to add the ability to select the update branch to BOX: - beta (updated once a day) - stable (updated ~ 14 days after beta release)
I think it would be right to add the ability to select the update branch to BOX:
- beta (updated once a day)
- stable (updated ~ 14 days after beta release)
... by increasing the cost of conditional improvements and licenses in the 1st time?
This point is not completely clear, please explain.
[quote]
... by increasing the cost of conditional improvements and licenses in the 1st time?
[/quote]
This point is not completely clear, please explain.
dividing the product into stable and beta branches complicates development, bug fixes, etc., which in turn slows down development, which in turn increases its cost, which leads to an increase in the cost of improvements and the development of new functionality. If you do not want to receive any updates, then you can create a separate branch and ask to disable some box from updates. If you want to receive updates in the form of new functionality, make improvements to your system, etc., then several times a year such incidents are possible that are fixed within an hour for all clients. Yes, you lost 1 hour waiting for the update and could not place an order with the supplier, but this is 0.001% of your total time in boxing, is it worth complicating and increasing the cost of software development for the sake of 0.001 stability?
dividing the product into stable and beta branches complicates development, bug fixes, etc., which in turn slows down development, which in turn increases its cost, which leads to an increase in the cost of improvements and the development of new functionality. If you do not want to receive any updates, then you can create a separate branch and ask to disable some box from updates.
If you want to receive updates in the form of new functionality, make improvements to your system, etc., then several times a year such incidents are possible that are fixed within an hour for all clients. Yes, you lost 1 hour waiting for the update and could not place an order with the supplier, but this is 0.001% of your total time in boxing, is it worth complicating and increasing the cost of software development for the sake of 0.001 stability?
I agree, the simpler, the more reliable. Maybe everything is much more complicated, and than just choosing a branch of the repository or the frequency of updates... Just suggested. Before that, you better know how the update process happens or should happen in practice. Thanks for the comprehensive answer.
I agree, the simpler, the more reliable.
Maybe everything is much more complicated, and than just choosing a branch of the repository or the frequency of updates... Just suggested. Before that, you better know how the update process happens or should happen in practice.
Thanks for the comprehensive answer.
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