IMODULES PRODUCT RELEASE September 2012

Transcription

1 IMODULES PRODUCT RELEASE September 2012 imodules-client Proprietary Information Data Management Import tool notification changes: The subject line in administrative notification s for imports now displays more information, including "errors occurred," "no data updated," "import complete," or "ignored columns" as appropriate. Additionally, ignored columns and links to error and success logs will be included in the . Search criteria updates: If you currently have a computed column built in your Encompass database that searches multiple fields, please note that the system now has a criteria limit of 10 values/options per search field. If you have questions about your computed fields or experience limitations that you don't understand, please contact Application Support. *Note: the two enhancements above were released prior to the September release dates. New non-member merge capability: In addition to Identity Checkpoint, this enhancement provides a new opportunity to keep your Encompass database records up-to-date and accurate and benefit from a more precise and holistic view of member activity. This new non-member merge functionality allows your administrators to use a prepared import.csv file to merge non- during the Identity member and member accounts either missed by Identity Checkpoint or ignored by the member Checkpoint process. This functionality also allows your administrators the option to "batch" merge accounts during an overnight import process, without the manual work of clicking each record in the Member Merge Grid. Your administrators choose if the records should be placed in the Merge Grid for a final review, or if the records should be directly merged into the database during the overnight merge process. HOW DOES IT WORK? From the administrative tools - Data menu, choose Identity Checkpoint Merge to locate the new import option:

2 The.csv is created using three column headers: A) The appropriate column header for your Constituent ID B) The appropriate column header for your imodules Member ID (usually"member_id") C) The column header for the third column will always be review The value/action in each row of this third column will be either "review" or "merge," depending on whether you want to place the records in the Merge Grid for review or directly merge them during the overnight merge process. If review is placed in the final column of the file, the non-member record will be added to the Identity Checkpoint Merge grid immediately upon file processing and you can then review the items and take the appropriate action. Note: Items added to the grid using the import file will be missing a Control Name. If merge is placed in the final column of the file, the system will merge the non-member information into the member account overnight and the non-member account will then be deleted. The record will not be placed in the Identity Checkpoint Merge Grid for review prior to the merge. Note: There is a 10,000 record limit per file upload. To learn more about preparing the import file and the process of merging records, please view our short tutorial available on the September Product Release page: Please note: You must have Identity Checkpoint enabled on your imodules site in order to use this import feature. You do not need to enable Identity Checkpoint on any forms, but it needs to be activated within your site tools in order to access to the Merge Grid. If Identity Checkpoint has not been activated on your site yet, please register for an Identity Checkpoint modular training via the Client Community. Marketing Release Step: The Subject Line has been added to the Release Step. Categories Opt-Out Report: The Opt-Out Report report generated through the Categories tool now includes a column with the name (header:" _name") that drove the member to opt out. (Note: "N/A" in the column denotes that the member did not opt out directly from an .) 2

3 Queue: Enhancements have been made to improve the imodules queue performance, allowing for faster processing of s through the queue. Event Management Event registration update (this enhancement will not be released until October 1, 2012): After October 1, 2012, your constituents can access their event registrations and edit those registrations directly through the confirmation . HOW DOES IT WORK? When your administrators create a new event in Encompass, a checkbox will appear in the Registration Settings area to "Enable Edit Registration Link in Confirmation ." This checkbox will be checked by default. This feature presents a link in the member registration confirmation with the verbiage "Click here to edit your registration information". (This link verbiage can be changed by your administrators in the member confirmationn editing tool.) Clicking the link will take the constituent back to the event registration form and present a pop-up window asking the constituent to confirm the action of editing the registration. (This window prevents multiple registrants from using the same address to register, and also ensures that the link in the was used to reach this editing step.) 3

4 Once the confirmation button is clicked, the form will appear for editing. Note: verbiage will display on the registration form letting the constituent know that registrations/purchases can be added, but not reduced (and that they will need to contact the institution for refunds). After editing a registration, the constituent registration change/details. will receive another confirmation , outlining the most recent Reporting: In event reporting, only one line per constituent will display for non-commerce registration changes. For registration changes that involve commerce, reporting will display one line per transaction. When reporting on date ranges, the system will look at both the date added and the last updated date. For example: 7/1 - Member registered for event 7/3 - Member came back and edited the event registration 7/4 - Member came back in and edited the event registration again Running the report on 7/2 with a date range of 7/1-7/1 would return the original registration only. Running the report on 7/5 with a date range of 7/1-7/1 would show the registration with the updates from 7/3 and 7/4. Running the report on 7/4 prior to the 7/4 edit with a date range of 7/3-7/3 would show the two rows from 7/1 and 7/3. Running the report on 7/4 after the 7/4 edit (or at any time in the future) with a date range of 7/3-7/3 would not return any rows (since last updated is now 7/4). Notes: 1. The confirmation the constituent receives AFTER making a change to the initial event registration will not reference the previous registration details. For example, if the constituent purchases four tickets initially, and then edits the registration by purchasing another two tickets, the second confirmation will only reference the two tickets purchased. 2. Please note that if this option is chosen by an administrator during event creation, it cannot be unchecked once a registration has been collected through the system for the event. Forms Edit header on billing page: An enhancement was made to allow administrators to add content / edit the header of the billing page on commerce forms. 4

5 HOW DOES IT WORK? A new item now appears under the administrative Manage Form drop down menu to "Edit Billing Page Header": Selecting the menu item will open a new content editor window, allowing you to insert customized content: The content will appear at the top of the billing page (under the breadcrumbs, if enabled). 5

6 Edit default button verbiage: An enhancement was made to allow for global changes to the default values for the following buttons: Campaign Donate Button Campaign Purchase Button Event Registration Button Event Attendees List Button Event Photos Button Event Message Boards Button Membership Purchase Button Note: Any verbiage change made will be applied across all events, campaigns, or memberships (as applicable). imodules will need to make these verbiage changes for you; please contact Application Support or , Option 4 for assistance. Login New data fields: Two new data fields are available to reflect member site registration and login activity. The new fields are titled "Date Registered" (reports on when the member accepted the Terms & Conditions) and "Last Logged In" (reports on when the member last logged in). These fields can be added to a profile form, used in queries, used for marketing, etc. in order to better facilitate understanding of member activity and communication efforts. Shibboleth: imodules has developed platform support for Shibboleth authentication using the SAML 2.0 standard. The Shibboleth system is a standards based, open source software package for web single sign-on. In order to provide the secure sharing of credentials required by Shibboleth and SAML, imodules has also joined the InCommon Federation ( as a Sponsored Partner. This integration and support of the Shibboleth and SAML standards into the imodules authentication system provides clients a powerful new alternative for handling the identify management and authentication of their constituents. System Updates New imodules IP Addresses: Over the next two months, imodules will be implementing hardware upgrades to improve our product and better support your system. We are very excited about the new capabilities that the upgrades will bring, but we need your help to ensure a smooth transition. If your organization has to whitelist IPs for login and e-commerce, we need your attention, please! Clients who whitelist IP addresses for login (including LDAP) and clients with certain e-commerce providers will be affected. The e-commerce providers are: Agilis (Agilisco)/Tecstra Bluefin Chase Paymentech PayPal Touchnet We need you to whitelist the following IP addresses by October 1, 2012 in order to ensure the smoothest transition after our upgrades secure7.imodules.com secure8.imodules.com secure9.imodules.com admin7.imodules.com adminlb.imodules.com securelb.imodules.com secure.imodules.com - existing admin.imodules.com - existing secure3.imodules.com secure4.imodules.com 6

7 Alternatively, our CIDR notations are: / /25 Please contact your Account Manager or Application Support with any questions Issue Resolutions The following issues have been resolved: Some admin actions placed the admin in other communities where they were not granted admin rights. If a Content Management System (CMS) only admin record attempted to log in, they received an error message. This only happened with CMS admins that weren't tied to member records. Lapsed auto-renewals were showing in the Membership Auto-Renewal Grid as active. If a content admin was CMS only and the rights were not tied to a member record the admin was unable to save content changes. SFTP Import Tool was not adding files to the queue. Imports were temporarily not processing for certain Canadian sites. If you cloned a campaign that had a gift matching field, the new form will error out whenever you tried to submit a form using that field. In Express s only, Document Manager links were created as relative URLs. Kickback reporting was returning zero results from 7/31/12 and later. The kickback reporting has now been updated to reflect the accurate data. Undeleted activities on deleted steps still appeared on the Activity List and were carried over when cloning. An error was thrown when trying to edit a campaign or event or publish to Facebook wall in Social Apps Manager. Trying to log in to sites using the Facebook login option was showing an error. Certain scheduled reports were dropping rows that should be included unless the record was created that day. Reporting was off for some international clients due to Identity Checkpoint update statement failing 8/13/12. Users with invalid addresses were not able to move off the "update bad page" after an admin marked them as valid. Underscores were being added to export column header in report output. Due to timestamps updated by the member merge process, the scheduled designations report does not include all the designations for the transactions included in the reconciliation report. When you added a date range to any of the "Tracking Action Filter" custom filters in Data Viewer, the system added the date portion of the query incorrectly. Some clients experienced an error running a saved report. Some clients are reporting missing scheduled report notification s on 8/3/12. In DataViewer Custom Filters, saving the query produced an error. Auto-renewals temporarily did not work for payment gateways that require tokenization for recurring billing info@imodules.com 7400 West 132 nd Street, Suite 300 Overland Park, Kansas imodules-client Proprietary Information 7