User bio
404 bio not found
Member since Jun 17, 2017
Posts:
show all 2
Replies:
show all 7
Nic Lorenzen · Dec 28, 2017 go to post

If performance is your concern, then avoid handing off work to additional Processes or Operations and do all the work within the Business Service, or better yet, outside of Ensemble (see: %SOAP.WebService) . Invoking synchronous requests to Business Processes/Operations is costly when dealing with high volume concurrent traffic. 

Nic Lorenzen · Jun 18, 2017 go to post

Thanks for the answer. Unfortunately, modifying this class isn't an option. 

Nic Lorenzen · Apr 17, 2016 go to post

I see where you are coming from with having a status code returned to notify a problem exists. 

Personally, I'd calculate comissions in a seperate single responsibility class that extends an abstract class for interface segregation. That class implements three public methods: Calculate(), HasError(), GetError()

//calculate then commission: 

Set tCommission = tUsedCarCommission.Calculate()

If tUsedCarCommission.HasError() 

      //log the error or do something with it 

It's very similar to what you'd do with traditional status types but without having to deal with passing in references. Also, IMO, it's very clear what's going on if the commission has an error. 

Certifications & Credly badges:
Nic has no Certifications & Credly badges yet.
Followers:
Nic has no followers yet.
Following:
Nic has not followed anybody yet.