This report displays the chapter members that are in danger of expiring
in 30, 60, and 90 days, since the roster does not designate the chapter
members that have renewed. This report does not include chapter members
that have already renewed their membership, but it does include chapter
members in their grace period. After the grace period has passed for a
chapter member, the report will no longer include him/her. If no grace
period exists for the chapter member, then the report will no longer include
him/her after the cycle end date has been reached. In addition, this report
does NOT include chapter members that have already expired; it only includes
constituents that still have active or grace membership in the chapter.
When a chapter member transfers to another chapter, the initial begin
date is carried over to that new order. After configuring the Report control
to run the Chapter Members Nearing Expiration - MBR1012 report on the
web, a chapter manager will see the report display similar to what is
shown here. For more information about this report, refer to Chapter
Members Nearing Expiration - MBR1012.
The section below details how to set up the Report control to display this report on your website. The instructions are intended for a user with web admin/host privileges.
This report must be deployed in the BusinessObjects server before group managers are able to run this report on the web. See BusinessObjects Installation for more information. In addition, this control uses the service operation "GetOnlineReportGenerateURL" from data services. The control uses this URL, which connects to the BusinessObjects server, to open or render the report in the current page in the form of PDF. Through the service operation "GetOnlineReportGenerateURL", data services generate the URL. See Personify Data Services for more information.
You
MUST have a proper named user license in order to be able to view the
report(s) online.
For
every Crystal or Webi-PDF report that you want a group manager to be able
to run, you will have to create a new page, and configure the Report control
for the report you want to run on that page. For example, if you want
a logged in web user to be able to run five different reports on your
website, you will have to create five different pages and configure the
control five different times on each page. As a best practice, create
a landing page that contains links to the separate pages that contain
the different reports, as shown below. If you are using DNN, you can use
the Links Module. See Configuring
the Links Module for more information. The only exception to this
is for Webi-HTML reports, which open right on the page (i.e., Analysis
of Chapter Member Health).
To configure the web settings for the Report control:
1. Add the
"PersonifyBoReport" to the desired page. For more information,
please see Adding a Page on
Your Site Using DNN.
The Control Settings for this control display, as shown below.
Text fields
have a 250 character limit.
2. If
necessary, in the Additional CSS Class for Control
field, enter the CSS class.
This option allows you to add additional layout to the skin by developing
a new DOTNETNUKE style, which requires an advanced understanding of HTML
and CSS. See Applying
a Default Site Container for information.
3. If
necessary, select or create a new Error Message.
The error message will display on the control for the action that was being
performed at the time of the error.
a. If left blank, the default error message, "An error occurred while performing [Insert Action]. If the problem persists, please contact the site administrator", will display. [Insert Action] will be substituted with the action the control was performing at the time of the error.
b. If you wish to change the default error message, customize it with a PWF Parameter. See Setting up PWF Parameters to learn more about these parameters and why your website's redirect URLs are managed there.
Although
there are more fields listed on the Report control, the settings listed
are the only values necessary in order to run this report on the web.
4. In the Param 01: Key field,
enter "SubgroupMasterCustomerID".
This is the report parameter key. This is the group master customer ID
for which the report is being run.
5. In the Param 01: Value field,
enter "pb_AFMRosterBag%$%GroupMCID".
This is the report parameter value. See Logic
Behind the Report Control for more information.
6. In the Param 02: Key field,
enter "SubgroupSubCustomerID".
This is the report parameter key. This is the group sub customer ID for
which the report is being run.
7. In the Param 02: Value field,
enter "pb_AFMRosterBag%$%GroupSCID".
This is the report parameter value. See Logic
Behind the Report Control for more information.
8. Leave the Param 3-15 Value and Key fields empty.
9. Leave the Parameters to Exclude and Report Name Key fields empty.
Although
there are more fields listed on the Report control, the settings listed
are the only values necessary in order to run this report on the web.
10. In the Report Name Value
field, enter "Chapter Members Nearing Expiration-MBR1012".
The "Report Name Value" field tells BusinessObjects the type
of report you want to render. It needs to be an EXACT match, since BusinessObjects
is searched based on the report's name in order to render the report on
the web. If you do NOT know this value, the report will not run and no
results will be rendered. See BusinessObjects
for more information.
11. From the Report Type drop-down, select "Web-PDF".
12. Click Save.