05-01-2017, 05:37 PM
AFAIK there is nothing more than what you can find in the wiki.
There is a test script which I use to test the implementation where you can see an example of a call and play with some of your own maps:
https://github.com/tsolucio/corebos/blob/master/modules/cbMap/testMap.php#L77
which would be called like:
http://your_server/your_corebos/index.php?module=cbMap&action=testMap&record={cbMap record ID}
The goal of the Condition Query and Condition Expression maps are to give the user control over conditions in your code. In other words, they are developer's maps.
Imagine that you need to get a discount for an account. Instead of hard coding that discount/logic you can use one of these maps to get the value. That way, when you need to change the logic in obtaining the value you can simply change the mapping functionality. Your code will stay the same as it will simply call the map and get the value, how it is actually calculated stays in the map and can change when needed.
Another example, suppose that you can set an invoice due date to 30 days for all accounts that have more than 10 paid invoices. Instead of hard coding that "10" in your custom validations you launch the query in a map, so when direction comes and changes the condition to 5 or "10 in the last two months" you simply change the map, not your code.
Keep asking.
There is a test script which I use to test the implementation where you can see an example of a call and play with some of your own maps:
https://github.com/tsolucio/corebos/blob/master/modules/cbMap/testMap.php#L77
which would be called like:
http://your_server/your_corebos/index.php?module=cbMap&action=testMap&record={cbMap record ID}
The goal of the Condition Query and Condition Expression maps are to give the user control over conditions in your code. In other words, they are developer's maps.
Imagine that you need to get a discount for an account. Instead of hard coding that discount/logic you can use one of these maps to get the value. That way, when you need to change the logic in obtaining the value you can simply change the mapping functionality. Your code will stay the same as it will simply call the map and get the value, how it is actually calculated stays in the map and can change when needed.
Another example, suppose that you can set an invoice due date to 30 days for all accounts that have more than 10 paid invoices. Instead of hard coding that "10" in your custom validations you launch the query in a map, so when direction comes and changes the condition to 5 or "10 in the last two months" you simply change the map, not your code.
Keep asking.
Joe
TSolucio
TSolucio