We recently got through our first migration and upgrade process, and among other things, we are noticing some differences between the new v11 default header and our "old" v10 headers. It's nice to see that the Navigator appears on the right regardless of what header is loaded, but two things we missed right away were the inherited constituencies, and the constituent type icons.
I see that we can calculate "all_consts" in our header sprocs with the new v11 FS_CONST_STRING to get the inherited constituencies, but is there an approved way to add the constituent type icons to our custom headers?
Thanks.
Chris,
As you've seen, we have a new function in v11, FS_CONST_STRING_NEW(), which returns constituencies from Primary affiliates (and the household on an individual with a primary household). You can simply swap out the old for the new in your custom header procedure for this.
As for the icons, take a look at the ld_sample_constituent_header datawindow in the SampleCustomScreens library. This is a copy of the standard header (not the flex header). It has references to image resources embedded in the client files, as well as a reference to a new column in the constituent header result set cust_group. To get these to work in your custom header, you should only have to do two things:
1. Edit your custom procedure to return "cust_group" from TR_CUST_TYPE based on T_CUSTOMER.cust_type.
2. Copy and paste the image objects from ld_sample_constituent_header into your custom header datawindow. There are six overlapping image controls in the object, one for each cust group (organization, individual, household) and an inactive version of each.
Hope that helps!
Ryan
Ah, those graphics are so easy to miss in that sample header! I had just reinvented that wheel with jpgs triggered by cust_type, but I will move to the icon method you describe.
Thanks!