In Able 7.x, we had a parameter for triggerEvents on the _Basket.Checkout() method. It was invaluable when a client wanted a completely behind-the-scenes checkout to occur. Most often during a web service call.
In Gold, the checkout service has no such parameter. And the old method on the basket class is depreciated and ignores the third parameter.
Is there another way to accomplish it without customizing full source?
Thought I'd ask before I submit it as a feedback suggestion. We have full source for this project, so we can add it ourselves if we have to. I just want to make sure there's isn't another way to suppress triggers during the actual checkout execution.
Checkout service and triggerEvents parameter
Checkout service and triggerEvents parameter
Joe Payne
AbleCommerce Custom Programming and Modules http://www.AbleMods.com/
AbleCommerce Hosting http://www.AbleModsHosting.com/
Precise Fishing and Hunting Time Tables http://www.Solunar.com
AbleCommerce Custom Programming and Modules http://www.AbleMods.com/
AbleCommerce Hosting http://www.AbleModsHosting.com/
Precise Fishing and Hunting Time Tables http://www.Solunar.com
- ForumsAdmin
- AbleCommerce Moderator
- Posts: 399
- Joined: Wed Mar 13, 2013 7:19 am
Re: Checkout service and triggerEvents parameter
OK. It appears that this optional parameter got overlooked in AC Gold. Probably because it was never needed the way AC Gold checkout service was implemented. Anyway we will have to restore this parameter to make it compatible with AC7 API. We will do this in R6.
For now there are two solutions
1. Implement your own custom Checkout Service.
2. If you have the source code available for this project, just make the update directly to the source and recompile
Unfortunately there is no easy way to to pass the 'triggerEvents' parameter to the checkout service because the service contract is already defined and it does not have this parameter available. Although we will update the service contract in R6 to make this parameter available, but in the mean time if you change code you can either change the service contract or you can pass this additional parameter by making it part of 'CheckoutRequest' parameter. It appears that in any case you will have to make some changes to the CommerceBuilder code.
For now there are two solutions
1. Implement your own custom Checkout Service.
2. If you have the source code available for this project, just make the update directly to the source and recompile
Unfortunately there is no easy way to to pass the 'triggerEvents' parameter to the checkout service because the service contract is already defined and it does not have this parameter available. Although we will update the service contract in R6 to make this parameter available, but in the mean time if you change code you can either change the service contract or you can pass this additional parameter by making it part of 'CheckoutRequest' parameter. It appears that in any case you will have to make some changes to the CommerceBuilder code.
Re: Checkout service and triggerEvents parameter
Ok thanks. We'll add the additional interface definitions and overloads to support the additional parameter. Comparing it to the 7.x code shows it's a simple implementation.ForumsAdmin wrote:It appears that in any case you will have to make some changes to the CommerceBuilder code.
Joe Payne
AbleCommerce Custom Programming and Modules http://www.AbleMods.com/
AbleCommerce Hosting http://www.AbleModsHosting.com/
Precise Fishing and Hunting Time Tables http://www.Solunar.com
AbleCommerce Custom Programming and Modules http://www.AbleMods.com/
AbleCommerce Hosting http://www.AbleModsHosting.com/
Precise Fishing and Hunting Time Tables http://www.Solunar.com
- ForumsAdmin
- AbleCommerce Moderator
- Posts: 399
- Joined: Wed Mar 13, 2013 7:19 am
Re: Checkout service and triggerEvents parameter
Yes it is pretty straightfoward if you have code.Comparing it to the 7.x code shows it's a simple implementation.