We are pleased to announce our next CaseMaster® develoers event on Decvember 6th in the Mansfield i-Centre. Starts around 13:00. A great opportunity to meet co developers and learn about CaseMaster®. Coffees and teas on the house and opportunity for networking afterwards. The agenda is as follows:
Contact email@example.com for more info! Hope to see you all soon!
We are pleased to announce that Mosaic Digital Media has recently joined our list of Value Added Resellers. Mosaic is a fast growing digital media agency that offers a wide range of services such as web-sites, SEO, social media support and email campaigns. To help their clients making the most of their sales and marketing, they now also provide CRM solutions for which they have selected the CaseMaster® platform.
Soon we will make the Q1-2017 release available for beta testing. A couple of important fixes have been applied as well as some security patches and browser support issues. Keep an eye on the developers portal for download and details.
A presentation has been added to the CaseMaster® developers' portal that presents a number of tools / tips and hints to performance tune CaseMaster® applications.
If you do not have access to the developers' portal, you can download it here.
A new module is begin test that should simply performance tuning of larger CaseMaster® systems: performance tracing. It logs all system key events that typically contribute to a heavy server load (such as dynamic attributes, methods, queries, etc) and writes them to an XML file. This makes much easier for developers to trace costly operations (e.g. an inefficient query) back to a system feature. Especially easy to use in combination with the pageflow logger.
We expect to make this available for beta download soon.
A new frameno has been added to the list of frameno's of a ref.
'AjaxAsync' works like 'Ajax' but is designed for asynchronous logic where we are not interested in waiting for a response.
This new feature can, for example, be used to trigger some server-side logic without any visual activity on the current page.
The standard behavior of an edit form is that the system tries to set the cursor on the first editable field that is not an option list (reason for not setting the cursor on an option list is that it is too easy to change its' value by accident).
This is normally fine but can be undesirable on complex, multi-action pages; for example where an edit form follows a list form.
A new tag has been added to the edit form action that, when the value evaluates to '1', overrules this standard behavior. The name of the tag is:
(Don't worry, it appears in the list of available tags in the repository editor).
A new function has been added to the BO function handler that allow you to remove a BO from the BO context. Example of use:
This function will return a warning when no BO with name 'name' exists in the BO context.