Three years ago I wrote about what I call the "Back to the Web" pattern. This week that pattern came up twice and we added some functionality related to it. Read on to refresh your memory.

A common use case of coreBOS is to control the amount of money a client owes us or that he has prepaid us. Information we need to know in order to reclaim those amounts or to reimburse them in subsequent purchases.

Making Decisions in coreBOS just got a lot easier. We already had Condition Expression and Condition Query Business Maps which were put together in coreBOS Rules to give developers a very powerful condition evaluation engine, and, now, we have added upon this another business map to make it even more flexible: Decision Table Business Maps.

Continue reading to learn how to use this new functionality.

I am very happy to publish this guest post from our community member Guido Goluke. Luke is practically the coreBOS Netherlands branch and very active participant in the coreBOS development process. In the last few days, he has added an interesting enhancement to the web service interface which he explains in this post.

Do you need the ability for clients to click a button in an email and have it automatically change the Status of an associated Ticket? If so, you have come to the right place to learn how to implement what I call the Get back into the web pattern.

A very common use case in business software applications is to have a set of defined steps or a procedure to follow when an event happens. The implementation pattern explained here shows how to do this in coreBOS.