Personify360 7.7.0 Release Notes

Personify360 Release Notes
Version 7.7.0
October 2018
7.7.0 RELEASE NOTES
Table of Contents
Introduction ............................................................................. 4
Features .................................................................................. 4
National Change of Address ................................................................................ 4
Questionnaires Everywhere ................................................................................. 5
Payment Schedules Online .................................................................................. 6
Pricing By World Bank Region ............................................................................ 7
Populate Purchasing Groups ............................................................................... 8
Coupons in CRM360 ............................................................................................. 8
Membership Join/Renew Enhancements............................................................ 9
Additional Enhancements .................................................................................. 10
Architecture and Third-Party Support Upgrades ............................................. 15
Resolved Issues .................................................................... 16

Accounting .......................................................................................................... 16
Application .......................................................................................................... 18
Awards ................................................................................................................. 19
Certifications/Transcripts................................................................................... 19
Committees ......................................................................................................... 20
Credit Card Processing ...................................................................................... 20
Customers ........................................................................................................... 20
Digital Content Delivery...................................................................................... 22
e-Business ........................................................................................................... 22
EFT ....................................................................................................................... 25
Group Management ............................................................................................ 25
Inventoried Products .......................................................................................... 25
Lockbox ............................................................................................................... 26
PROPRIETARY AND CONFIDENTIAL

2
7.7.0 RELEASE NOTES
Marketing ............................................................................................................. 26
Meetings .............................................................................................................. 27
Membership ......................................................................................................... 27
Moves Management ............................................................................................ 28
Notifications ........................................................................................................ 28
Orders .................................................................................................................. 28
Packages ............................................................................................................. 30
Products .............................................................................................................. 30
SSO/IMS ............................................................................................................... 31
Subscriptions ...................................................................................................... 31
Third-Party Integrations ..................................................................................... 32
Upgrading to 7.7.0 ................................................................. 33

Before You Begin ................................................................................................ 33
Upgrading from 7.6.2 .......................................................................................... 34
Technical Changes ................................................................ 66

API Base Changes .............................................................................................. 66
API Core Changes ............................................................................................... 69
Configuration Template Changes ...................................................................... 70
Database Changes .............................................................................................. 70
Form Changes ..................................................................................................... 77
Notification Server Changes .............................................................................. 77
SSO/IMS Changes ............................................................................................... 78
TRS Changes....................................................................................................... 80
Universe Changes ............................................................................................... 85
Web Changes ...................................................................................................... 85

3
7.7.0 RELEASE NOTES
Introduction
The Personify360 7.7.0 release includes new features, as well as resolved issues. This
document describes the features added and provides general explanations of the resolved
issues. It also includes technical changes and upgrade instructions.
Features
National Change of Address
National Change of Address (NCOA) is a secure dataset of approximately 160 million

change-of-addresses going back 48 months that enable organizations to update mailing lists
with new addresses from individuals, families and businesses that have moved. While it is
recommended you process NCOA before every mailing, most organizations update their
database quarterly and many Personify clients have created custom processes to export
to/import from the third-party of their choosing. Personify360 version 7.7.0 contains a new
base NCOA process that can be configured for your third-party file of choice.

4
7.7.0 RELEASE NOTES
Questionnaires Everywhere
Prior to Personify360 version 7.7.0, questionnaires could only be defined for Meeting
products. As of 7.7.0, that functionality has been expanded to allow questionnaires to be
added to all subsystems, giving organizations not only the opportunity to personalize the
member experience and deliver greater value, but also greater opportunities for members to
self-serve and manage their own data updates.
For membership products, there is also a new, configurable Demographics control to allow
population of those answers to write back to the constituent record.

5
7.7.0 RELEASE NOTES
Payment Schedules Online
Looking to add flexibility to your annual membership? Want to attract members who may be
unable to pay for an annual membership up front? In Personify360 version 7.7.0, Personify
has added an enhancement to eBusiness to allow users to select a monthly payment
schedule for their membership products.
The user can choose to pay for the full year all at once (defined from a 1-year rate code) or
pay in monthly installments while paying the first installment upfront (defined from the 1-year
installment rate code).

6
7.7.0 RELEASE NOTES
Pricing By World Bank Region
As of Personify360 version 7.7.0, pricing can be defined based on World Bank Region.
Membership and other products can be made more affordable depending on the customer’s
location. This feature allows organizations to serve emerging or upcoming markets, and
provides opportunities to share and expand on research, driving non-dues revenue.
Enhancements include a new System Type for World Bank Region and codes for Low,
Medium, and High, as well as the ability to associate a country with a particular World Bank
Region. This feature is available from the Personify360 back office client, PersonifyGO,
Personify eBusiness, and when using the ORD650 TRS process.

7
7.7.0 RELEASE NOTES
Populate Purchasing Groups
As of Personify360 version 7.7.0, a new TRS process called PGR100 has been created to
populate purchasing groups. Organizations can use the new process to pull a list from Data
Analyzer to populate the purchasing groups, making purchases more accessible to more
constituents.
Using Data Analyzer, organizations will be able to generate a simple or complex list to
populate a purchasing group in bulk.
Coupons in CRM360
As of Personify360 version 7.7.0, coupons earned and used by a customer now display on a
new task in CRM360. This features provides insight into constituent engagement by
providing more accessible constituent data. Information displayed includes what coupons
are available versus used, expiration dates for each coupon, and quick links to the order the
coupon was earned or used on.

8
7.7.0 RELEASE NOTES
Membership Join/Renew Enhancements
Enhancements have been made to the online membership join and renew workflows,
allowing users to change or add a chapter membership, associated subscriptions, and
Special Interest Groups during the workflow.

9
7.7.0 RELEASE NOTES
Additional Enhancements
ZIP100 & ORD650 Enhancements
ORD650 now has a new parameter added to renew payment schedules. This feature will
save staff time and improve the order renewals process.
ZIP100 now has a new parameter added to allow inclusion or exclusion of USPS approved
city misspellings. This features allows organizations to manage their own city data and
prevent confusion when selecting cities when entering a constituent’s address.

10
7.7.0 RELEASE NOTES
reCAPTCHA
A new, configurable web control has been added for Personify360 version 7.7.0 allowing
your organization to add reCAPTCHA security across several areas of your website,
including when adding a new credit card, checking out, during membership join, one click
donation, and guest checkout. This feature improves security across your eBusiness site.

11
7.7.0 RELEASE NOTES
Launch Screen Redesigns
As of Personify360 version 7.7.0, the launch screens within the Personify360 back office
client have been redesigned to have a more modern and clean look and feel. The launch
screens that have redesigned include the Product Launch, Marketing Launch,
Communication Launch, Accounting Central Launch, Advertising Central Launch, FND
Launch, and Volunteer Central Launch screens, as well as the Constituent Header,
Constituent Placeholder Avatars, and the Personify360 Home Screen.

12
7.7.0 RELEASE NOTES
Customer-Facing Report Redesigns
For Personify360 version 7.7.0, many customer-facing reports have been redesigned to
have a more modern and clean look and feel. Reports that have been redesigned include
the Customer Profile Report (CRM1000), Donor Profile Reports (FND1210, FND1211),
Committee Rosters, Meeting Rosters, Acknowledgement Letters, Pledge Reminder Letters,
and Order Invoices (ORD660).

13
7.7.0 RELEASE NOTES
Notification Enhancements
Updates to Notifications include the ability to resend a notification using a Resend Email
button, allowing your organization to quickly remediate member satisfaction issues.
Additionally, organizations now have the ability to add an ICS calendar file directly within a
notification. Recipients of the notification email will be able to click an Add to Calendar link to
add meetings and events to their default email client calendar.
eBusiness Configuration File
In Personify360 version 7.7.0 clients now have the ability to render their eBusiness site in
the language of their choosing. This version includes a resource file that allows someone
with technical experience to customize the labels of eBusiness controls without the need to
modify source code or recompile.

14
7.7.0 RELEASE NOTES
Meeting Attendance
Personify360 version 7.7.0 includes the ability to hide or show meeting attendees on the
web, allowing your organization to maintain meeting attendee privacy where necessary or
desired. This feature includes a new web control configuration on the Meeting Detail page
that allows for hiding meeting attendees.
Architecture and Third-Party Support Upgrades
PBBI/Spectrum 12.2 Upgrade
Spectrum™ Technology Platform is a system that improves the completeness, validity,

consistency, timeliness, and accuracy of your data through data standardization, verification
and enhancement. Ensuring that your data is accurate, complete, and up to date enables
your firm to better understand and connect with your customers. Please see the Spectrum
12 Release Notes for a full list of features.
As of the PBBI Spectrum 12.2 upgrade, please note the following:
 French addresses are able to be entered correctly when the ‘Include a Standard
Address’ check box is not checked. However, when it is checked French addresses
are not entered correctly. This is a PBBI issue.
 Rural to Urban address conversion takes place correctly when ‘Include a Standard
Address’ check box is checked. However, it does not work correctly when the check
box is unchecked.
Thycotic DLL
As of Personify360 version 7.7.0, Thycotic DLL has been removed.

15
7.7.0 RELEASE NOTES
Resolved Issues
Accounting
 When the user attempted to run EFT680 for a product with the short pay rule set
to ADJUST, the process did not activate the order and the transaction entries
were not distributed.
(TFS: 10857; SFDC: 1045)
 When the user attempted to perform an advanced adjustment for an FND
product when no default accounts were set for the FND subsystem, they
received an error and were unable to perform the adjustment.
(TFS: 10859; SFDC: 1064)
 When the Allow Price Update flag was checked on a membership product with
dues basis defined, upon renewal the renewed order was not recalculated when
the dues basis changed.
(TFS: 10914; SFDC: 1043)
 When a user with a preferred currency that was not USD attempted to check out
on the web, non-USD receipt types were not available for payment.
(TFS: 12276; SFDC: 1571)
 When the user adjusted the price of an order with a 100% discount, the revenue
was not adjusted when selecting the Adjust the Revenue or Adjust Revenue to
Zero option.
(TFS: 13480; SFDC: 1981)
 When the user checked the Automatically Renew checkbox on an order with no
Auto-Pay method defined, the auto-pay was automatically set to Credit Card,
which when saved displayed an error message.
(TFS: 14067; SFDC: 2367)
 When the user renewed a membership order with the Block Tax checkbox
checked, the renewal order did not have the Block Tax checkbox checked and
tax was charged on the renewal order.
(TFS: 14085; SFDC: 2379)
 When the user attempted to write off an order line balance on a cancelled order
with a refund, they received an error message and were unable to perform the
write-off.
(TFS: 14182; SFDC: 2435)
 When the user ran FAR680 for an order in a foreign currency where the
exchange rate was different for different order lines, the exchange rate was not
calculated correctly.
(TFS: 14321; SFDC: 2539)

16
7.7.0 RELEASE NOTES
 When the user clicked the Calculate Discount and Shipping button to recalculate
the order pricing on an order with a Manual Override discount, the order amounts
changed and a Debit/Credit memo was created for the order.
(TFS: 14372; SFDC: 2564)
 When the user selected Line Receipt as the Transfer Mode for a receipt transfer,
the number zero did not display by default in the Line drop-down.
(TFS: 14386; SFDC: 2570)
 When the user attempted to post a batch with a very large number of receipts,
the action timed out and the batch was not posted.
(TFS: 14409; SFDC: 2586)
 When the user applied an overpayment to an order line with a MBR or MTG
product with the Short Pay set to Adjust and the Max Adjusted Price set to zero,
the overpayment was not applied correctly.
(TFS: 14447; SFDC: 2620)
 When the user ran FAR610 with the Include Unapplied Receipts parameter set to
Y, the Customer Minimum Debit and Customer Minimum Credit amount
parameter fields were ignored for unapplied receipts.
(TFS: 14479; SFDC: 2637)
 When the user reversed a write off transaction, the system did not reverse the
original account used for the write off, causing incorrect financials on the order.
(TFS: 14563; SFDC: 2708)
 When the user attempted to save EFT information on an order where the bank
information already existed on the customer's record, an error message
displayed.
(TFS: 14571; SFDC: 2714)
 When the user attempted to select Asset accounts for the Fundraising
subsystem, only Revenue and Expense accounts were displayed in the chooser.
(TFS: 14620; SFDC: 2761)
 When the user adjusted an order amount after revenue recognition, incorrect
credit/debit memo entries were created when the product was defined with two
revenue account pairs.
(TFS:14688, SFDC: 2821)
 When the user ran the FAR695 process for an unapplied receipt with a write off,
the write off created did not match the balance.
(TFS: 27531; SFDC: 3012)

17
7.7.0 RELEASE NOTES
Application
 When the user attempted to only show certain report setups by checking the
Public checkbox on the default parameter setup screen, the checkbox did not
function.
(TFS: 10883; SFDC: 1066)
 When the user attempted to make changes to the report details for any online
report, the application type automatically changed from Online Report to Batch
Process.
(TFS: 12366; SFDC: 1594)
 When a user who was not a Super User attempted to view the Submission
Status (TRS200) screen, the Mark Selected for Deletion button was not available
for selection.
(TFS: 12688; SFDC: 1687)
 When the user attempted to use the scroll bar in a text box that was read-only,
they were unable to use the scroll bar or read the rest of the text within the box.
(TFS: 14209; SFDC: 2447)
 When the user attempted to add a new Type to system types and codes, the
system opened the New Code screen, not allowing the user to select the
subsystem.
(TFS: 14458; SFDC: 2624)
 When the system attempted to run a scheduled job where Org and Org Unit were
parameters, the default parameters were not retained and the job failed.
(TFS: 14483; SFDC: 2640)
 When the user attempted to access the ORD660 Invoice report from the Print
Invoice task on the ORD001 screen, the company logo did not display on the
invoice.
(TFS: 14493; SFDC: 2648)
 When the user attempted to add new questions to the Question Definition Screen
(APP020), the Default Answer drop-down options always came from the APP
subsystem, regardless of the subsystem selected.
(TFS: 14582; SFDC: 2722)
 When the user worked with large number of orders and receipts for extended
period of time, the application lags and had to be restarted.
(TFS: 27381; SFDC: 2900)

18
7.7.0 RELEASE NOTES
Awards
 When two different constituents nominated the same nominee for an award, the
attachment provided by the first constituent was overwritten by the attachment
provided by the second constituent.
(TFS: 14172; SFDC: 2417)
Certifications/Transcripts
 When the user attempted to run the CRT500 process for a customer, the
credential description was not updated and credentials were only removed from
the Primary address.
(TFS: 12367; SFDC: 1595)
 When the user attempted to cancel an order with a certifiation, the certification
remained as Pending on the customer's record.
(TFS: 13263; SFDC: 1827)
 When a requirement was completed for a certification, the system updated the
CE credit value but did not mark the requirment option as completed.
(TFS: 14099; SFDC: 2384)
 When the user entered Ad hoc CE credits without specifying the credit type and
then later entered additional CE credits with the type specified, the credits were
recorded but the option never moved to completed.
(TFS: 14134; SFDC: 2389)
 When the user marked a requirement as completed on the CRT002 screen, the
Add to Transcript checkbox defaulted to checked.
(TFS: 14430; SFDC: 2607)
 When the user attempted to view the ASCII Upload for Ad Hoc Transcript screen
(TRN005B) when a large number of records existed in the TRN_UPLOAD table,
the screen did not load.
(TFS: 14543; SFDC: 2690)
 When adding a required exam to a transcript program, the grade code
autopopulated, but on save, the system displayed the Missing Property Viewer
window and prompted the user to enter a grade code value.
(TFS: 14718; SFDC: 2847)
 When the user attempted to create a renewal for a certification with no expiration
date set, an error message displayed stating "Recertification program to be used
for renewal must not be expired" and the renewal was not created.
(TFS: 27332; SFDC: 2865)

19
7.7.0 RELEASE NOTES
Committees
 When the user attempted to open a document saved to a committee under the
Maintain Minutes task in Committee Central, an error was displayed and the
document was not opened.
(TFS: 12621; SFDC: 1654)
 When the user attempted to add a new committee member to a committee, the
end date and voting status were not auto-populated from committee structure.
(TFS: 13255; SFDC: 1822)
Credit Card Processing
 When the user returned multiple of the same product and ran CCP610 to settle
the refunds, only the first order line was refunded.
(TFS: 27488; SFDC: 2974)
Customers
 When the user changed the type of customer being created during customer
creation from Individual to Company, fields that did not apply to company records
were not cleared, creating faulty data on the company record.
(TFS: 11003; SFDC: 1185)
 When the user attempted to delete a customer alert, a confusing message
displayed in the pop-up confirmation box.
(TFS: 11086; SFDC: 1260)
 When the user attempted to convert a prospect to a customer, the duplicate
check process prevented the prospect from being converted and no customer
record was created.
(TFS: 11179; SFDC: 1325)
 When the user added a new list demographic for a customer in CRM360, the
cursor focus did not change to the correct input field.
(TFS: 11229; SFDC: 1402)
 When the user attempted to select the "Mark as Bad and Add New" option for an
address in the FormattedAddressChooser window, the application crashed.
(TFS: 11313; SFDC: 1440)
 When an address containing an ampersand was linked to a constituent and the
address was changed, the address was incorrectly truncated.
(TFS: 12238; SFDC: 1545)

20
7.7.0 RELEASE NOTES
 When the user attempted to add contact information on a customer record in

CRM360 and changed the contact Type during creation, an error was shown and
the user was unable to save the contact information.
(TFS: 12277; SFDC: 1572)
 When the user attempted to merge two customers, any documents attached to
the retain customer were unable to be opened after the merge.
(TFS: 13108; SFDC: 1739)
 When the user attempted to view a customer in CRM360 who had committee
memberships, the Involvement section on the CRM360 home page did not show
committee memberships in the correct order.
(TFS: 13129; SFDC: 1747)
 When the user clicked the Refresh button on the CRM360 home page several
times in a row, an error message displayed.
(TFS: 13879; SFDC: 2251)
 When the user attempted to refresh the engagement score on the CRM360
home page for a customer with no scoring data, the refresh date was not
updated.
(TFS: 13973; SFDC: 2321)
 When the user attempted to open a document from the Attached Files task in
CRM360 that was already open in another tab, the document could not be
viewed.
(TFS: 14198; SFDC: 2443)
 When the user attempted to select Customer Credentials for a customer record
in CRM360, the user was able to add credentials that did not have the Active flag
checked in system types and codes.
(TFS: 14210; SFDC: 2448)
 When the user viewed the Customer Financial Analysis screen, the text
contained a spelling error.
(TFS: 14230; SFDC: 2477)
 When the user attempted to add credit card information to a customer record
where the customer has a BLANK address, an error message displayed and the
credit card information was not saved.
(TFS: 14259; SFDC: 2504)
 When segmentation was set to N and the user attempted to create a customer,
the Organization and Organization Unit were automatically populated for the new
customer.
(TFS: 14322; SFDC: 2541)
 When the user attempted to add an employment relationship for a customer with
no existing employment relationship, the Primary Employer flag was not checked

21
7.7.0 RELEASE NOTES
by default.
(TFS: 14345; SFDC: 2547)
 When the user attempted to merge two customers, the retained customer record
contained the primary email, phone, and fax of the merged customer.
(TFS: 14394; SFDC: 2577)
 When the user added different credentials to a customer record, the
NAME_CREDENTIALS and LABEL_NAME columns in the Customer table did
not have spaces after the commas.
(TFS: 14437; SFDC: 2615)
 When the user ran CUS530, the Latitude and Longitude values were not updated
on the Voter and Other Information screen for an address.
(TFS: 14547; SFDC: 2697)
 When the user updated an address, the ADDRESS_STATUS_CODE was not
updated in both tables CUS_ADDRESS and CUS_ADDRESS_DETAIL, causing
the ADDRESS_STATUS_CODE to not be in sync.
(TFS: 14570; SFDC: 2585)
 When the user attempted to add a new address to the customer record in
CRM360, they were able to leave the Address Line 1 field blank even though it
was set to required.
(TFS: 27366; SFDC: 2895)
Digital Content Delivery
 When the user attempted to update the file for an ECD/DCD product with a new
file, the old file was not overwritten and was not updated.
(TFS: 10942; SFDC: 1113)
e-Business
 When the user attempted to use a specific address setup with the Country field
blank, the eBusiness My Account page did not function.
(TFS: 11068; SFDC: 1263)
 When the user applied a market code that was not associated with any discount
to their Shopping Cart on the web, the text "Free" displayed after the market
code was applied.
(TFS: 13550; SFDC: 2031)
 When the user attempted to view their certification status in the Certification
History control, the status did not display correctly.
(TFS: 13802; SFDC: 2202)

22
7.7.0 RELEASE NOTES
 When the user attempted to add a Middle Name from the Name and
Demographics control on the web, the middle name was not updated in
Personfy360 Operations.
(TFS: 14204; SFDC: 2405)
 When the user attempted to register for a multi-day meeting with a daily rate
setup defined, when the user changed the price from Standard to One Day and
then back to Standard without choosing a Daily rate, the user is unable to
proceed to the next step.
(TFS: 14206; SFDC: 2444)
 When the user applied a 100% discount coupon during checkout on the web and
then removed the coupon, the order totals updated correctly but the user was
unable to process their payment and complete the order.
(TFS: 14214; SFDC: 2452)
 When the user viewed an umbrella product with a preorder/backorder INV and
ECD product as linked products on the web, the Add to Cart button did not
display.
(TFS: 14303; SFDC: 2529)
 When the user attempted to register for a meeting on the web and had to reset
their password, they were not returned to the workflow correctly after completing
the password reset.
(TFS: 14331; SFDC: 2545)
 When a meeting product was linked to a Transcript program, the CE credits
defined in the transcript program did not appear on the Product Listing, Product
Detail, Event Calendar, or Event Detail pages on the web.
(TFS: 14361; SFDC: 2555)
 When the user attempted to make a donation on the web and used an already
existing email address, the email validation did not display and a duplicate
customer was created.
(TFS: 14370; SFDC: 2562)
 When the user attempted to use the photo control to upload images on the web,
if they were not PNG files then they did not display.
(TFS: 14377; SFDC: 2566)
 When a constituent had the Include Profile in Web/Mobile Directory flag
unchecked within CRM360, they still displayed within the Member Directory on
the web.
(TFS: 14378; SFDC: 2567)
 When a new constituent record was created, the Include Profile in Web/Mobile
Directory flag defaulted to being unchecked.
(TFS: 14379; SFDC: 2568)

23
7.7.0 RELEASE NOTES
 When a record was selected wihtin the online Member Directory, the Country
code displayed within the address on the details page instead of the Country
description.
(TFS: 14380; SFDC: 2569)
 When the user attempted to select the specific size/color combination under an
umbrella product on the web, the star rating of the umbrella product did not
display.
(TFS: 14392; SFDC: 2576)
 When the user attempted to use the Pay Open Orders control to pay for their
renewal membership order, after using a promo code that took the balance to
zero, no Complete Order button displayed.
(TFS: 14434; SFDC: 2613)
 When an anonymous user attempted to donate on the web and the
corresponding FND donation product had a component that was out of stock, an
error message displayed and duplicate addresses were created for the donor.
(TFS: 14481; SFDC: 2639)
 When the user attempted to go through the checkout process on the web, the
process incorrectly passed the primary address instead of the billing address to
the CCP_REQ_ANS table.
(TFS: 14610; SFDC: 2747)
 When the user attempted to view the Pay Open Balances screen on the web, if
more than 60 orders existed for the customer then all orders did not display.
(TFS: 14626; SFDC: 2768)
 When the user attempted to edit and change the product type of an umbrella
product in their Shopping Cart online, the system did now allow them to make
any changes.
(TFS: 27344; SFDC: 2876)
 When the user attempted to add an HTML module to a page on the web, the
DNN Rich Text Editor did not work.
(TFS: 27351; SFDC: 2884)
 When the user attempted to select their membership subscription benefits during
membership join on the web, the benefits displayed incorrectly.
(TFS: 27382; SFDC: 2901)
 When the user attempted to add more than one of the same donation product to
their cart on the web, they received a duplicate product message in the cart.
(TFS: 27403; SFDC: 2917)
 When the user attempted to purchase a BPA audited Subscription product on the
web and entered invalid credit card information, no validation message
displayed.
(TFS: 27432; SFDC: 2940)

24
7.7.0 RELEASE NOTES
 When the user purchased a zero-dollar product on the web, the order line for the
product was not updated to Active in the back office.
(TFS: 27502; SFDC: 2985)
 When a new customer was created from the web, the Demographics Source
drop-down in the back office did not populate.
(TFS: 27536; SFDC: 3017)
 When the user added a product to their cart on the web and then the product
became unavailable to view because the web display dates had ended, the price
displayed as FREE.
(TFS: 27547; SFDC: 3024)
 When a company name had a prefix, the Company field on the meeting badge
was populated incorrectly online.
(TFS: 27560; SFDC: 3035)
 When the user attempted to add a phone number with spaces on the web, an
error message displayed and the number was not saved.
(TFS: 27561; SFDC: 3036)
EFT
 When the user ran EFT681, the Prenote Status was changed to
PRENOTE_FAILED and the Prenote Status date was removed.
(TFS: 14266; SFDC: 2510)
Group Management
 When the user attempted to add a new individual in group management on the
web, after adding the individual's details and email address and moving to the
membership join workflow, the email address was not passed.
(TFS: 14211; SFDC: 2449)
 When the user added a new employee with an address type of Home using
Company Group Management on the web, the new address did not display on
the employee's online profile.
(TFS: 14212; SFDC: 2450)
Inventoried Products
 When the user attempted to run the INV2006 online report for a specific
Warehouse and Product Class, the generated report displayed products having

25
7.7.0 RELEASE NOTES
the specified Product Class but not belonging to the specified warehouse.
(TFS: 10941; SFDC: 1123)
 When the user performed a price adjustment on a backordered product so that
the order balance was brought to 0, the line status for the product changed from
Backordered to Active.
(TFS: 10978; SFDC: 1156)
 When the user attempted to select a product code that containted an ampersand
for the INV635 process, only the portion of the code prior to the ampersand was
populated.
(TFS: 13569; SFDC: 2043)
 When the user attempted to purchase an INV product online where partial
inventory was available, the order line with quantity available was back-ordered
and the order line with the quantity not available was active.
(TFS: 13986; SFDC: 2331)
 After the user returned an inventoried product, the FAR003a screen no longer
displayed the Warehouse Info fields.
(TFS: 14665; SFDC: 2795)
Lockbox
 When the user attempted to submit the LCK100 process, when arriving at the
LCK001 screen, the user was able to enter an amount that was greater than
what was provided on the File Upload.
(TFS: 11163; SFDC: 1322)
Marketing
 When the user attempted to run the MKT500 process with the "Load Records for"
parameter set to Both, the system was unable to handle apostrophes in data
fields.
(TFS: 10875; SFDC: 1052)
 When the user attempted to create a List Communication from the MKT006
screen, the selected Send Mode was not retained upon moving to the second
step.
(TFS: 13316; SFDC: 1865)
 When the user ran the MKT800 process, non-active customers were not
considered skipped records and were included in the processed list.
(TFS: 13583; SFDC: 2055)

26
7.7.0 RELEASE NOTES
 When the user attempted to search for a Prospect customer list on the MKT003
screen, an error displayed and the ProspectChooser did not display.
(TFS: 13835; SFDC: 2223)
 When the user attempted to create a list code on the MKT002 screen after
changing the Org Unit, an error was displayed.
(TFS: 14593; SFDC: 2727)
Meetings
 When the user clicked the Show Meetings Dashboard link on the MTGCentral
screen, the dashboard was not displayed.
(TFS: 12266; SFDC: 1565)
 When the user attempted to view a meeting session product, the meeting
location was incorrect when the product was first opened.
(TFS: 12606; SFDC: 1648)
 When the user attempted to run the MTG510 process, the job completed
successfully but no output report was generated.
(TFS: 14183; SFDC: 2436)
Membership
 When the user renewed a membership order with components, the component
products did not renew with the correct cycle end dates.
(TFS: 14165; SFDC: 2412)
 When the user attempted to renew a membership order with ECD components,
the ECD components were not populated on the renewal order.
(TFS: 14330; SFDC: 2544)
 When the user ran MBR900, the process did not update the Cycle Begin Date in
the CUS_Current_Membership_Info table.
(TFS: 14436; SFDC: 2614)
 When the user transferred a membership order and changed the Transfer Date,
the proration did not update.
(TFS: 27368; SFDC: 2897)
 When the user attempted to apply a 100% discount in the back office to a
renewal order where the order method code was "Web", an error displayed and
the order was not activated.
(TFS: 27379; SFDC: 2898)

27
7.7.0 RELEASE NOTES
Moves Management
 When the user attempted to end the Current Solicitor relationship, upon setting
the end date and saving, the Previous Solicitor record was not updated.
(TFS: 13847; SFDC: 2233)
 When the user attempted to assign a solicitor to a prospect, two relationships
with the solicitor were created for the same date.
(TFS: 13857; SFDC: 2238)
 When the user attempted to add more than one prospect for a solicitor with the
same Donor name, the system saved the duplicate prospects with no validation.
(TFS: 13860; SFDC: 2241)
 When the uset attempted to convert a prospect to a customer and a potential
duplicate was found, the system did not allow the prospect to be converted.
(TFS: 14246; SFDC: 2492)
 When the user attempted to view the Prospect Moves Plan Management scree,
the Primary Search Group did not match with the corresponding field value on
CRM360 under Demographics.
(TFS: 14530; SFDC: 2677)
Notifications
 When the user attempted to locate the Notify Service User Expiration base
notification on the Notification Maintenance screen, the stored procedure and
email template were missing.
(TFS: 14431; SFDC: 2610)
 When the Meeting Order Created notification was sent, the template displayed
the salutation field label as Bill-To Customer instead of Line Level Ship-To
Customer.
(TFS: 14505; SFDC: 2657)
Orders
 When the user attempted to run the ORD650 process with the Default Value as
THREEMONTHSOUT, the date mask defaulted to the first of the month.
(TFS: 10921; SFDC: 1104)
 When the user attempted to renew an order with component order lines with
different Ship-to customers, the Ship-to customers of the additional order lines
were copied from the third component line.
(TFS: 10994; SFDC: 1161)

28
7.7.0 RELEASE NOTES
 When the number of rows in the Quick Pick product sidebar on Order Entry was
greater than the DEFAULT_MAX_QUERY_SIZE set in the application
parameter, the correct number of quick pick products did not display.
(TFS: 11044; SFDC: 1220)
 When the user attempted to change the primary address for a customer and the
Address Propagation screen propagated the new address to all orders, coupon
discounts were removed from the orders, resulting in faulty order balances.
(TFS: 11156; SFDC: 1356)
 When the user created a dues basis schedule and limited associates, then
changed the maximum associates and renewed a MBR order, no error message
was thrown for the renewal order even though the number of max associates
was exceeded.
(TFS: 11178; SFDC: 1316)
 When the user attempted to change the ship-to address on a paid and invoiced
order to a non-taxable state, the tax was recalculated on the order resulting in a
credit balance.
(TFS: 11195; SFDC: 1363)
 When the user attempted to create a renewal order in a batch with a future date,
the order date incorrectly defaulted to today's date.
(TFS: 12209; SFDC: 1527)
 When the user attempted to input a status change reason for an order
cancellation, upon saving the cancellation the status change reason was not
retained.
(TFS: 12664; SFDC: 1673)
 When the user attempted to renew a non-INV order with a shipping surcharge at
the product level using the ORD650 process, the shipping was not calculated
correctly on the renewed order.
(TFS: 13343; SFDC: 1886)
 When the user attempted to change the Ship-to or Bill-to address on a past
order, the rate structure was updated for that order based on past date, causing
current members to not receive member pricing.
(TFS: 14224; SFDC: 2470)
 When the user changed the component quantity on a membership order and
then renewed the order, the updated component quantity was not reflected on
the renewal order.
(TFS: 14249; SFDC: 2495)
 When the user ran ORD660, the generated output report included inactive and
not accepted receipt types.
(TFS: 14280; SFDC: 2518)

29
7.7.0 RELEASE NOTES
 When a membership order had a digital subscription as a member benefit, the

order was not renewable if the member did not have an email address but the
ORD650 process still updated the Renewal Created Flag to Y.
(TFS: 14463; SFDC: 2625)
 When the user attempted to reduce the screen size while on the ORD001
screen, the grid and detail portion of the order was unusable if more than one
order line was present.
(TFS: 14545; SFDC: 2694)
 When the user attempted to renew an order that had been transferred, the
renewal order contained duplicate membership order lines.
(TFS: 14546; SFDC: 2695)
 When an order had the Bill-to as tax exempt, the order was incorrectly charged a
tax by ORD650.
(TFS: 14641; SFDC: 2781)
 When the user created a multicurrency order, the Order Line Total and the
Schedule Amount on the payment schedule screen displayed an incorrect
balance.
(TFS: 27442; SFDC: 2953)
Packages
 When the user created an order for a member and then changed ship to to a
non-member, a member rate structure was incorrectly applied to components in
a select package.
(TFS: 14287; SFDC: 2523)
Products
 When the user changed the Available From Date value to a new date while
copying a product, the Pre-order Available Date value was updated, but the user
was unable to save the dates.
(TFS: 11007; SFDC: 1203)
 When the user attempted to create an order for a product with a component with
a different rate code than the main product, the component rate code was
incorrect.
(TFS: 11153; SFDC: 1310)
 When the user attempted to copy a product, the system allowed the user to enter
more than 12 characters in the level 2 and level 3 fields.
(TFS: 14022; SFDC: 2343)

30
7.7.0 RELEASE NOTES
 When the user added a new rate code to a product and checked the Default Rate
checkbox after selecting the Rate Structure and before selecting the Rate Code,
the check was not removed from the previous default rate code.
(TFS: 14659; SFDC: 2791)
SSO/IMS
 When the user attempted to give access to the

SSOCustomerGetByCustomerToken webservice, the webservice did not exist.
(TFS: 11092; SFDC: 1257)
 When the user created an SSO login in the Personify360 application and chose a
username containing a comma, the user was unable to log in to the DNN
website.
(TFS: 13068; SFDC: 1721)
 When the user attempted to log in to SSO using a password containing a period,
they were unable to log in.
(TFS: 14396; SFDC: 2578)
 When the user attempted to log in from the SSO login page, if there were any
spaces after the username they were unable to log in.
(TFS: 14487; SFDC: 2644)
 The SSO Inline Login did not log the customer in when the token URL was
accessed within the "AutoLoginLinkExpiryInSeconds" period.
(TFS: 14726; SFDC: 2853)
 When a logged-in user attempted to navigate to the SSO login page, the user
was prompted to log in again instead of being redirected to the appropriate home
page.
(TFS: 27353; SFDC: 2885)
 When the user attempted to log in to the SSO login page using a password with
special characters, they were unable to log in.
(TFS: 27535; SFDC: 3016)
Subscriptions
 When the user attempted to modify the Issue Date for a subscription product, the
field was read-only and uneditable.
(TFS:14239; SFDC: 2486)
 When the user ran SUB670, the process skipped records if the prefix of the
customer was NULL.
(TFS: 14662; SFDC: 2794)

31
7.7.0 RELEASE NOTES
Third-Party Integrations
 When Business Objects Enterprise went down, it caused the Application service
to crash.
(TFS: 14506; SFDC: 2658)
 When the user attempted to validate an address using PBBI Spectrum, the user
received an error message "Geocoded Postal Code Only" and no System
Generated Address was available for the entered address.
(TFS: 14510; SFDC: 2663)

32
7.7.0 RELEASE NOTES
Upgrading to 7.7.0
Use the information below to upgrade the Personify360 database from 7.6.2 to 7.7.0. You
must install the 7.6.2 release before you can upgrade to the 7.7.0 release. If you are
performing a fresh installation, please refer to the Personify360 7.7.0 Installation and
Configuration Guide in the Documentation folder in the 7.7.0 package.
Personify360 7.7.0 has been developed and tested on the following platform:
 Database servers – Windows Server 20012 R2 Standard or above and SQL

Server 2016 SP1
 All Application Servers and TRS servers – Windows Server 20012 R2 Standard
or above
 e-Business and other web applications – Windows Web Server 2012 or above
 Operating system – Windows 10 with minimum screen resolution 1366x768
Before You Begin
Before you begin the upgrade, please perform the following:

1. Verify your servers have the operating systems mentioned above. These can be
upgraded to the existing servers or new servers.
2. Please refer to the "Personify360 Architecture Matrix" document in the
Documentation folder in the 7.7.0 package for more information on the minimum and
recommended software for this release.
This includes Infragistics 16.2, .NET Framework 4.5.2, DNN 9.0.1, and DevExpress
10.2.
3. Verify all open batches are closed and all unsettled credit cards are settled.
4. Backup your existing Personify360 database if you currently run Personify360. This
ensures that, if you encounter problems while upgrading Personify360, the Personify
contact can assist you in resolving the problem. Please create a full backup of the
following databases (as applicable):
 Personify360 database
 Personify360 Installation database
 e-Business DNN database
 PA-DSS audit logging database
 SSO database
Please refer to the following location for more information on how to back up
databases in SQL Server: http://msdn.microsoft.com/en-us/library/ms187510.aspx.

33
7.7.0 RELEASE NOTES
5. Back up all files and folders for the Application Service, Notification Service, TRS
Service, Web Services, and e-Business websites. This should also include all
*.config, config.xml, and * default.
You must log on as "Administrator" or a similar privilege to perform the upgrade.
6. Stop the Application Service, Notification Service, TRS Service, and Web Server
until the upgrade is complete.
The upgrade process should be performed locally.
Upgrading from 7.6.2
Upgrading to 7.7.0 from a previous release involves upgrading all or some of the servers
and interfaces, including the following:
 Databases
 Application Server
 Back Office Client
 BusinessObjects
 SSO/IMS
 Data Services
 e-Business
 PA-DSS
 Unified Search
 Notification Service
 Third-Party Interfaces
 TRS
 Home Page
 Passkey
 Image Services
 Online Help
 Custom Components
The following sections detail how to upgrade each of these items.
Do not modify any of the installation database values when performing the
upgrade. Those values include Version Number, Association Name, Environment Name,
Application Type, and Database Connection. If you modify any of these values, then you
cannot log in as Host to the e-Business site. You need to update in all locations including
databases.

34
7.7.0 RELEASE NOTES
Databases
Before you can install and configure the Online Store and App Data Cache on the system,
please ensure the following steps have been completed:
Please see the Personify360 7.7.0 Installation Guide for more information on
these specific steps.
If you are already using the SQL Server 2016, please skip the first 2 steps below and start
with step 3:
1. Upgrade to SQL 2016 of SQL Server.
2. Configure SQL Server service to run using a Domain User Account.
3. Start SQL Server Agent Service on SQL Server.
To create a user defined data type for Personify360 database:
1. The Modify_DataType_Script.sql script must be executed where Personify360
databases reside within the instance of the SQL Server:
a. Open SQL and login using SQL Login for the "SA" account.
b. Start a new query with the "Master" database selected.
c. Double-click the file.
2. Press F5 on your keyboard to run the script.
Please login to SQL Server with the SA account to execute this script. The
Personify360 application does not require SysAdmin permissions and should not be granted
SysAdmin permissions just to allow this script to execute.
If the Personify360 Installation database entry contains "7.6.2", then please change it to
"7.7.0".
To upgrade the Personify360 databases:
1. Restore the backup of the Personify360 database.

For more information on how to restore a database backup to the new SQL Server
2012, please refer the article located here: http://msdn.microsoft.com/en-
us/library/ms177429.aspx.
2. Create a login for the new server to be used by the Personify360 application. Provide
permission to the required login (on the new server) to the restored database and

35
7.7.0 RELEASE NOTES
provide the required role.
3. Run the following query:

USE [master]
ALTER DATABASE <personify database name> SET COMPATIBILITY_LEVEL =
130
GO
4. Navigate to the ...\Databases\Upgrade Scripts folder.
5. Locate the command script file Runner.cmd and open the file using a text editor,
such as Notepad.
6. Replace the following parameters based on the table below.
Parameter Replace with
<SQL Server The name of your SQL Server. In most installations, this will be the
Name> name of your workstation or laptop.

36
7.7.0 RELEASE NOTES
<Database The name of the SQL Server database that you want to upgrade.
Name>
<SQL User The SQL Server User ID you use to log on to your Personify database.
ID> In most instances, this User ID will be either "TIMSS" or "Personify".
<SQL The password you have assigned to the SQL User ID. If you do not
Password> know this password, please contact a system administrator or enter a
Helpdesk ticket with Personify to assist you in recovering your
password.
7. Save your changes.

8. Double-click Runner.cmd to execute the database upgrade.
If you are running it from the database server itself (Windows 2008), you may need
to select Run as Administrator.
Running this command may take considerable amount of time to

complete depending on the size of the database.
9. Review the [DatabaseName]_Upgradeto770.log file and verify the upgrade was

successful.
10. Review the APP_NEXT_NUMBER_ERROR table to ensure no errors have been
recorded.
If you find any errors in this table, please discontinue the upgrade process and
contact your Customer Support Representative.
11. If necessary, set up maintenance and disaster recovery tasks as required for the
organization.
12. Please follow the same process for the Installation database and any other
databases (if applicable).
13. To upgrade the Personify360 database with Notification service changes (if you are
already using Notification service in 7.6.2 then proceed with the upgrade):
Notification service is not a mandatory install for Personify360. If you like

to install Notification service, then please see the Personify360 7.7.0 Installation
Guide for more information on these specific steps.
a. Navigate to the ...\Databases\Notification_Event_Procedures from 7.6.2

folder.
b. Locate the command script file Runner.cmd and open the file using a text
editor, such as Notepad.
c. Replace the following parameters based on the table below.

37
7.7.0 RELEASE NOTES
<SQL Server Name> The name of your SQL Server. In most installations, this will be
the name of your workstation or laptop.
<Database Name> The name of the SQL Server database that you want to
upgrade.
<SQL User ID> The SQL Server User ID you use to log on to your Personify
database. In most instances, this User ID will be either "TIMSS"
or "Personify".
<SQL Password> The password you have assigned to the SQL User ID. If you do
not know this password, please contact a system administrator
or enter a Helpdesk ticket with Personify to assist you in
recovering your password.
d. Save your changes.

e. Double-click Runner.cmd to execute the database upgrade.
If you are running it from the database server itself (Windows 2008), you may
need to select Run as Administrator.

f. Review the [DatabaseName]_NTS_Upgradeto770.log file and verify the

upgrade was successful.
SQL Job Creation

To create two SQL Jobs for the Personify360 database:
GDPR SQL Job Creation
This step involves executing SQL scripts available in release package sub-folder
“...\Version.XX\Databases\SQL_EXECUTIVE_SCHEDULED_JOBS\GDPR”.
The scripts in this folder must be executed in the Personify360 database only.
There is only one SQL Job script listed and one readme file in this folder:
 Read me file - ReadMe_FIRST.txt
 SQL Job - GDPR_CLEANUP_DATA_JOB.sql
Please read the instructions in readme file before creating the SQL Jobs.
 SQL job – [DatabaseName] _GDPR_CLEANUP_DATA_JOB

38
7.7.0 RELEASE NOTES
o This SQL Job will be used to delete the history data from the
APP_GDPR_MASTER_RETENTION_REFERENCE table depending upon
the value of the application parameter
"GDPR_DEFAULT_EXPIRATION_DAYS". The default schedule for this SQL
job is to run at every 10 minutes daily. This schedule can be modified as
required for each Personify360 installation.
Script Execution Instructions:
 This script must be executed by a user that has sysAdmin privileges on SQL
Server.
 Please specify the SQL User that will be used to run the SQL Job. Replace value
‘sa’ with SQL User name in line 110.
 Please specify the Database Name by doing a global replace of keyword
"DatabaseName" with the name of the Personify360 database. There should be
5 instances of this keyword that will be updated.
PopulateBOEReports SQL Job Creation
This step involves executing SQL scripts available in release package sub-folder
“...\Version.XX\Databases\SQL_EXECUTIVE_SCHEDULED_JOBS\PopulateBOEReports”.
The scripts in this folder must be executed in the Personify360 database only.
There is only one SQL Job script listed and one readme file in this folder:
 Read me file - ReadMe_FIRST.txt
 SQL Job - Populate_BOE_DATA_JOB.sql
Please read the instructions in readme file before creating the SQL Jobs.
 SQL job – [DatabaseName]_POPULATE_BOE_DATA_JOB
o This SQL job will call usp_Populate_RPT_DATA Stored Procedure populate
BOE reports data "GDPR_DEFAULT_EXPIRATION_DAYS". The default
schedule for this SQL job is to run at every 10 minutes daily. This schedule
can be modified as required for each Personify360 installation.
Script Execution Instructions:
 This script must be executed by a user that has sysAdmin privileges on SQL
Server.
 Please specify the SQL User that will be used to run the SQL Job. Replace value
‘sa’ with SQL User name in line 110.
 Please specify the Database Name by doing a global replace of keyword
"DatabaseName" with the name of the Personify360 database. There should be
5 instances of this keyword that will be updated.

39
7.7.0 RELEASE NOTES
Application Server
Make sure your Application Server Service is still set up with a user who can
send emails AND the Personify.Server.Application.Server.exe has the correct email
server updated in the  section.
As of 7.5.2, Personify360 no longer supports Workflow Designer.
To upgrade the Application Server:

1. Ensure that the Personify360 Application Service is stopped.
2. Deploy all of the files from the ...7.7.0\Package\Services\ApplicationServer folder
to the Personify360 Application Server root directory.
3. Open your command prompt and open the App Service install folder.
4. Run the following queries to re-install the performance counters for “Queries without
where clause”:
 Personify.Server.ApplicationServer.exe /RemoveCounters
 Personify.Server.ApplicationServer.exe /InstallCounters
5. Start the Personify360 Application Service.
If the Application Service does not start, you can troubleshoot by enabling the
diagnostics in the Personify.Server.ApplicationServer.exe.config file.
Back Office Client
To upgrade the Back Office Client:

1. Deploy the files from the ...7.7.0\Package\BackofficeClient folder to the
corresponding folder on the new file server.
Please refer to Database Changes before you deploy any .xml, .config,
or .isl files.
2. Open the Config.xml file in a text editor, such as Notepad.

3. Navigate to the <Section Name="Settings"> section and “HelpViewer” item.
4. Update the following text in HelpViewer item, as shown below:
ContentSensitiveHelp="index.htm?rhcsh=1&rhmapid={0}"

40
7.7.0 RELEASE NOTES
5. Save the Config.xml file.

6. With the 7.4.1 release and onwards, all taskbar items will be expanded by default. If
you want to retain this default behavior, please skip to the next step. To change the
taskbar control to auto-collapse, perform the following:
a. Navigate to the ...7.7.0\Package\BackOfficeClient\Config folder.
b. Modify the "Taskbar" tag inside the Container.xml file and change
AutoCollapse = “True”.
<Taskbar Name ="TaskBar" Caption="What do you want to
do?" Style="Office2003" Width="262" UseAppStyling="False"
BackGroundColor="#7F8FAE" GroupFontSize="11"
ItemFontSize="10" ItemIcon="bullet-white.png"
TitleForeColor="Snow" GroupForeColor="AliceBlue"
ItemForeColor="White" TitleFontSize="11" AutoCollapse =
"False">
</Taskbar>
7. Launch Personify Enterprise using Auto Updater and ensure that the application
works as expected.
Do NOT run the TIMSS.exe directly from the server folder as it may wipe out the
screen XML and TASK files.
BusinessObjects
With the 7.7.0 release, Personify is supporting Business Objects 4.2 SP5 version.
For more information on installing BusinessObjects, please see the

Personify360 7.7.0 Installation Guide.
To update P360 BusinessObjects reports:

1. Upload the universes to your current environment using synchronizer from the
following location:
...7.7.0\Package\BusinessObjects\Upgrade\Universes.

41
7.7.0 RELEASE NOTES
2. Make sure all the universes have a valid connection before running the synchronizer
to assign Webi’s to universes.
Make sure the Identity Management Roles universe has a valid universe
connection pointing to the SSO database.
3. Make sure that webi reports are having valid universe connection by running
Synchronizer and update "Webi Universe Connection" for the Webi reports.
4. Upload the Online and TRS Reports using synchronizer to your current environment.
Be sure to install Flash Player (PPAPI based) to show dashboard reports in

Data Analyzer. For more information, please see the Breaking Changes section.
BusinessObjects Promotion Management Wizard application installation:
The Promotion Management Wizard is a tool that aims to ease the task of CMS content
copy. Instead of using the Command Line Interface (CLI), the Promotion Management
Wizard offers a Graphic User Interface (GUI) for performing a full copy or a selective copy.
LCMBIAR files are the same compared to the CMC or CLI versions of Promotion
Management.
If you are upgrading from BI 4.2 SP4 to SP5, once the install is done you wouldn’t notice
Promotion Management Wizard by default. Perform the below steps to install promotion
management wizard (These instructions are only of upgrading for SP4 or lower version to
SP5, Full Install should be fine).
1. After installation of SP5 upgrade package, navigate to control Panel  Programs
and Features
2. Right click on your base install (i.e., SAP BusinessObjects BI Platform 4.2 SP4) and
click on uninstall
3. In the resultant screen select Modify option

42
7.7.0 RELEASE NOTES
4. In the select features screen under administrator tools, select Promotion

Management Wizard and click Next

43
7.7.0 RELEASE NOTES
5. Follow the prompts to install the feature.
SSO/IMS
From 7.4.1 release onwards SSO/IMS configuration is mandatory. If you have

not already installed/configured SSO/IMS, please follow instructions provided in
Personify360 7.6.0 Installation Guide.
To upgrade SSO Website:
1. Before upgrading, please take a backup of SSO website and database, IMS Web
Service, and IMS Windows Service.
2. Database upgrade scripts are available in the following location:
...7.7.0\Package\WebApplications\SSO_IMS\Database\Upgrade
3. Modify the Runner.cmd file to provide the valid SSO database credentials.
4. After you update the Runner.cmd file, double-click the command file to execute the
scripts on SSO database.

44
7.7.0 RELEASE NOTES
5. Review the [DatabaseName]_Upgradeto770.log file after DB scripts execution is

complete to make sure the Database scripts were executed successfully.
6. Navigate to the “SSO_WEBSITE” folder in your web server.
7. Deploy all of the files from the
...7.7.0\Package\WebApplications\SSO_IMS\SSO_WEBSITE folder to the SSO
web site root directory.
Do not overwrite the web.config and LoginTemplates\SSOSetting.xml files in your
installed folder.
8. If you have already configured SSO with 7.5.2, then proceed to step number 12
directly.
a. Rename the Template_SSOSetting.xml file to SSOSetting.xml, which is available
in the following package folder:
...7.7.0\Package\WebApplications\SSO_IMS\SSO_WEBSITE\LoginTemplates
\
b. Open the SSOSetting.xml file and update the "ActiveURL" with the Data Service
URL, as shown below.
Before the 7.5.2 release, ActiveURL was pointing to the e-business site URL. As
of 7.5.2, ActiveURL needs to be pointed to Data Services.
<ActiveAccount Enable="False"
ActiveURL="http://[DATASERVICES_WEBSERVER_NAME]/[DATASERVIC
ES_WEBSITE_NAME]/">
c. By default, the email reminder for Forgot Password, Forgot User Name are sent
to the user entered email addresses. If the email addresses are shared between
different customers and the email is found to be duplicate, the customer has to
enter some more information to identify the correct account to reset. The
“resetUserNameOrPassword” is set to True by default.
The following section has to be added to the SSOSetting.xml.
<ResetUserNameOrPassword Enable="True"
ActiveURL="http://[DATASERVICES_WEBSERVER_NAME]/[DATASERV
ICES_WEBSITE_NAME]/">
<add key="LastName" text="Last Name"
CaseSensitive="false" />
<add key="FirstName" text="First Name"
CaseSensitive="false" />
</ResetUserNameOrPassword>
ActiveURL: should be the URL for the data services. The

ValidateAccount.aspx page should be under the folder pointed by the Data

45
7.7.0 RELEASE NOTES
services URL. SSO calls this page to make Personify calls for identifying the
correct customer.
The keys last name and first name represent the information the user has to
enter to identify the correct account. These keys are configurable and can be
any field in the Customer table.
d. Save and close the SSOSetting.xml file.
9. Open the Web.config file in a text editor, such as Notepad.
10. Add the following entries in Web.config file, as shown below:
a. Update Connection string for DNN and SSO databases.
<connectionStrings>

<add name="SiteSqlServer"
connectionString="Server=[DNN_DB_SERVER_NAME];Database=[DNN
_DB_DATABASE_NAME];user
id=[DNN_DB_USER_ID];password=[DNN_DB_USER_PASSWORD]"
providerName="System.Data.SqlClient" />

<add name="SSO.ConnectionString"
connectionString="Server=[SSO_DB_SERVER_NAME];Database=[SSO
_DB_DATABASE_NAME];user
id=[SSO_DB_USER_ID];password=[SSO_DB_USER_PASSWORD]"
providerName="System.Data.SqlClient" />
</connectionStrings>
b. Add the following keys for the Data Service integration.

<appSettings>

<add key="svcUri"
value="http://[DATASERVICES_WEBSERVER_NAME]/[DATASERVICES_W
EBSITE_NAME]/PersonifyData.svc/"/>
<add key="EnableBasicAuthentication" value="true"/>
<add key="TIMSSSearchCount" value="100" />

46
7.7.0 RELEASE NOTES
Web.config changes reference:
11. Please cross verify web.config changes in your web server once with the web.config
file delivered with the package.
a. Add the following keys in the <SSOSettings><LoginTemplates> section to
support mobile:
<SSOSettings>
<LoginTemplates>
<add key="MOBILE_CD"
value="LoginTemplates/MobileContractDocumentLogin.aspx"/>
<add key="MOBILE_DEFAULT"
value="LoginTemplates/MobileLogin.aspx"/>
</LoginTemplates>
</SSOSettings>
b. Add the following <system.net> node at the end of the web.config file before the
</configuration> node closure to send emails for reset password/username.

<system.net>
<mailSettings>
<smtp from="[From EmailAddress]">

47
7.7.0 RELEASE NOTES
<network host="[SMTP Server information]" port="25"

defaultCredentials="true" />
</smtp>
</mailSettings>
</system.net>
</configuration>
c. Add the following SSO.CusEmailValidtionRegex key at the end of the

“appSettings” section in web.config file.
<add key="SSO.CusEmailValidtionRegex" value="^[a-zA-Z0-
9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-zA-Z0-
9!#$%&'*+/=?^_`{|}~-]+)*@((\[[0-9]{1,3}\.[0-
9]{1,3}\.[0-9]{1,3}\.)|(([a-zA-Z0-9\-]+\.)+))([a-zA-
Z]{2,12}|[0-9]{1,3})(\]?)$" />
12. The following settings were added with the 7.7.0 release. Add the following entries in
the web.config file if you are already on the 7.6.2 release.
i. Go to <configuration> / <Configuration
type="Generic.Foundation.Configuration, Generic.Foundation"> / <Custom> /
<Values> section.
ii. Add following two entries for User Name strength and Auto Login link expiry
respectively
<KeyValue Key="UserNameRegularExpression" Value="^[^,]+$" />
<KeyValue Key="AutoLoginLinkExpiryInSeconds" Value="60" />
13. Save and close the web.config file.

14. Delete Thycotic.Data.dll file from SSO_WEBSITE environment BIN folder.
15. Reset IIS.
To upgrade IMS Web Service and Windows Service:
1. Before upgrading, please take a backup of IMS Web Service and IMS Windows
Service, including the configuration files.

48
7.7.0 RELEASE NOTES
2. Deploy all of the files, excluding the web.config file, from the following location to the
IMS Web Service installed folder:
...7.7.0\Package\WebApplications\SSO_IMS\IMS_WebService
3. Delete Thycotic.Data.dll file from IMS Web Service environment BIN folder.
4. Deploy all of the files, excluding the IMSWinService.exe.config and Install.config
files, from the following location to the IMS Windows Service installed folder:
...7.7.0\Package\WebApplications\SSO_IMS\IMS_WindowService
5. Delete Thycotic.Data.dll file from IMS Windows service environment folder.
6. Start the IMS Windows Service.
Data Services
To upgrade the Personify360 Data Services to be compatible with the 7.7.0 e-Business site
default web controls setup, please refer the upgrade/fresh installation guide of Personify360
Data Services available at the following location:
“..\SeparatelyPackagedComponents\PersonifyDataServices\2.0.0\Personify Web Services
Designer Release Notes.pdf”.
Configuration Changes
The following configuration files have to be modified in order to support the new features.
Web.config
If you are upgrading from an earlier version of Personify360 Data Services, update the
Web.Config.XML with the following, make sure you take a copy of the existing
Web.config.XML file before you start the upgrade:
A template of the Web.Config.XML is also available at the following location:
..\PersonifyDataServices\2.0.0\Package\Personify.DataServices\Personify.DataService
s.Base\Upgrade\Template_Web.Config.
Any entry in your existing Web.Config not included in this template may be
commented or removed.
1. Add the following new entries in the <system.webServer> section, if they are not
already available:
<security>

<requestFiltering>
<requestLimits maxUrl="4194304" maxQueryString="4194304" />
</requestFiltering>
</security>

49
7.7.0 RELEASE NOTES
2. Add the following new entries in the <system.web> section, if they are not already
available:

<httpRuntime maxUrlLength="2097151" maxRequestLength="4194304"
maxQueryStringLength="2097151"/>
e-Business
If you have not already installed SSO, please follow the instructions in the
"Installing SSO and IMS" section of the Personify360 7.7.0 Installation Guide.
Step 1: Install Personify DNN modules

1. Upgrade the Personify360 DNN Modules using following steps:
a. Navigate to the following file path in your upgrade package:
...\WebApplications\E-Business\Upgrade\PersonifyWebParts\Webparts
b. Copy the All Personify Web Parts.zip file to your local temporary folder.
c. Unzip the file.
d. Copy the unzip files (*.zip) to Personify e-Business root folder > Install >
Module directory.
e. Open your Personify360 e-Business site and go to:
www.[YourDomain]]/[DNNWebSiteURL]/install/install.aspx?mode=installreso
urces
f. It will create modules based on your web parts inside the folder specified in
command line.

50
7.7.0 RELEASE NOTES
2. If you are already using the PersonifySkin, which was part of the 7.4.1 e-Business
site installation, update/install the skin using following instructions:
a. Copy the PersonifySkin.zip file to Personify e-Business root folder > Install >
Module directory.
b. Copy the Container.zip file to Personify e-Business root folder > Install >
Container directory.
3. Open your Personify e-Business site and go to:
www.[YourDomain]]/ [DNNWebSiteURL]/install/install.aspx?mode=installresources
4. Check for any errors.
5. If you like to use Personify-Branded skin, which is part of 7.7.0 e-business site
installation, update/install the skin using following instructions:
a. Copy the Personify-Branded.zip file to your local temporary folder.
b. Unzip the file.
c. Copy all the files to Personify e-Business root folder > Portals > _default >
Skins > Personify-Branded directory.
d. Copy the Personify-Branded.zip file to Personify e-Business root folder >
Install > Module directory.
6. Delete Thycotic.Data.dll file from Personify e-Business root folder > BIN folder.
Step 2: Modifying the Web.Config File

1. Open the web.config file in a text editor, such as Notepad.
2. Remove references of “FiftyOne.Foundation” library from following locations.

51
7.7.0 RELEASE NOTES
a. Go to <system.webServer> section and then go to <modules> section and

find the name called “Detector” and delete the key.
<add name="Detector"
type="FiftyOne.Foundation.Mobile.Detection.DetectorModule,
FiftyOne.Foundation" preCondition="managedHandler" />
b. Go to <runtime> section and then go to “assemblyBinding” section and find
the assemblyIdentity called "FiftyOne.Foundation" and delete corresponding
assemblyIdentity.
<dependentAssembly>
<assemblyIdentity name="FiftyOne.Foundation"
publicKeyToken="e967ae578dabd98e" />
<bindingRedirect oldVersion="0.0.0.0-32767.32767.32767.32767"
newVersion="3.2.3.2" />
</dependentAssembly>
c. Go to <dotnetnuke> section and then find the “clientcapability”
defaultProvider "FiftyOneClientCapabilityProvider" and delete corresponding
clientcapability.
<clientcapability defaultProvider="FiftyOneClientCapabilityProvider">
<providers>
<clear />
<add name="FiftyOneClientCapabilityProvider"
type="DotNetNuke.Providers.FiftyOneClientCapabilityProvider.FiftyOneClient
CapabilityProvider, DotNetNuke.Providers.FiftyOneClientCapabilityProvider"
providerPath="~\Providers\ClientCapabilityProviders\FiftyOneClientCapability
Provider\" />
</providers>
</clientcapability>
3. Globalization is updated to use ResourceProvider to support multiple languages.
Update globalization by going to <system.web> section and add the
resourceProviderFactoryType to the key. Key can be find in the following:
<globalization culture="en-US" uiCulture="en" requestEncoding="UTF-8"
responseEncoding="UTF-8" fileEncoding="UTF-8"
resourceProviderFactoryType="Personify.WebControls.ResourceProvider.ExternalRes
ourceProviderFactory, Personify.WebControls.ResourceProvider, Version=1.0.0.0,
Culture=neutral"/>
4. DotNetNuke default provider is changed. To point to new provider go to
<dotnetnuke> section and find the “htmlEditor”. Replace the htmlEditor section with
the following new section.
<htmlEditor defaultProvider="DNNConnect.CKE">
<providers>
<clear/>

52
7.7.0 RELEASE NOTES
<add name="DNNConnect.CKE"
type="DNNConnect.CKEditorProvider.CKHtmlEditorProvider,
DNNConnect.CKEditorProvider"
providerPath="~/Providers/HtmlEditorProviders/DNNConnect.CKE/"
settingsControlPath="~/Providers/HtmlEditorProviders/DNNConnect.CKE/Module/Ed
itorConfigManager.ascx" />
</providers>
</htmlEditor>
5. Telerik version is changed. So please update the version bindings accordingly.
<dependentAssembly>
<assemblyIdentity name="Telerik.Web.UI"
publicKeyToken="121fae78165ba3d4" />

newVersion="2014.3.1209.40" />
6. “Telerik.Web.Design” library is used in this version. So please add the following
reference if already not exists. If this library reference is already exists please make
sure that version number matches with the library version.
<dependentAssembly>
<assemblyIdentity name="Telerik.Web.Design"
publicKeyToken="121fae78165ba3d4" />
newVersion="2013.02.717.40" />
7. Save the web.config file.
Step 3: ReCaptcha settings in the web.config file:

1. ReCaptcha can be configured with 7.7.0 e-business site. We are using google API to
set up ReCaptcha for the e-business site.
2. Add following keys in the <appSettings> section.

<add key="g-SecretKey" value="" />
<add key="g-SiteKey" value="" />
<add key="g-ReCaptchaJS" value="https://www.google.com/recaptcha/api.js" />
<add key="g-API" value="https://www.google.com/recaptcha/api/siteverify" />

3. Save the web.config file.

53
7.7.0 RELEASE NOTES
Step 4: Update Alternate Preview Page Path Changes in the Web Server
1. Go to your server where the site is hosted. Explore to site folder and in the following
path:
Portals\_default\Skins\PersonifySkin\js\
2. Open the personify-skin.js file in a text editor, such as Notepad.
3. Search for AlternatePreview.aspx and replace /[YOUR_e-BUSINESS_WEBSITE]/
with your sites virtual directory name.
4. Click Save.
5. Update the following PersonifySkin files (i.e., *.ascx extension) for responsive
design setup:
 cart.ascx
 full-width-responsive.ascx
 index-responsive.ascx
 index-store-responsive.ascx
 join1-responsive.ascx
 left-main-responsive.ascx
 onecol-responsive.ascx
 product-listing-responsive.ascx
 threecol.ascx
 main-full-width-responsive.ascx
 myAcct.ascx
 myAcct-responsive.ascx
 left-main-responsive-account.ascx
a. Replace [EBUSINESS_WEBSERVER_NAME] with your web server name (e.g.,
“dev.personifycorp.com”).
b. Replace [EBUSINESS_WEBSITE_NAME] with your virtual directory name (e.g.,
“personifyebusiness”).
6. Reset IIS.
Step 5: Update Alternate Preview Page Path Changes in the Web Server for the
new Theme called Personify-Branded
1. With 7.7.0 release, we have changed the default theme to Personify-Branded.

54
7.7.0 RELEASE NOTES
2. Go to your server where the site is hosted. Explore to site folder and in the following
path:
Portals\_default\Skins\Personify-Branded\js\
3. Open the personify-skin.js file in a text editor, such as Notepad.
4. Search for AlternatePreview.aspx and replace /[YOUR_e-BUSINESS_WEBSITE]/
with your sites virtual directory name.
5. Click Save.
6. Update the following Personify-Branded files (i.e., *.ascx extension) for responsive
design setup:
 cart.ascx
 threecol.ascx
 2col-main-right.ascx
 cart.ascx
 index-store-responsive.ascx
 left-main-responsive-account.ascx
 left-main-responsive.ascx
 left-main-right-myaccount.ascx
 main-full-width-responsive.ascx
 myAcct.ascx
 threecol.ascx
a. Replace [EBUSINESS_WEBSERVER_NAME] with your web server name
(e.g., “dev.personifycorp.com”).

55
7.7.0 RELEASE NOTES
b. Replace [EBUSINESS_WEBSITE_NAME] with your virtual directory name

(e.g., “personifyebusiness”).
7. Reset IIS.
Step 6: Update the Default DNN files of DNN Framework and Fixes for DNN
Framework Database
You can also find the DNN 9.0.1 upgrade instructions in detail from the following
path …\WebApplications\E-Business\DNNUpgrade\Personify - DNN 9.0.1 Upgrade
Document.doc [on page 17, step 5 for fixing the possible home page setting issue]. Please
read the script file instructions for details.
1. To update the default DNN source files, which come from the DNN framework, copy
the contents from the below folder to the e-Business root folder in the web server:
...\WebApplications\E-Business\Upgrade\DNN_SiteRoot_Fix\
Step 7: Update the DNN Framework Database for Performance Improvement

1. Navigate to the ...\ Package\WebApplications\E-
Business\Upgrade\DNN_Database_Fixes folder.
2. Locate the command script file Runner.cmd and open the file using a text editor,
such as Notepad.
3. Replace the following parameters based on the table below.
<SQL Server The name of your SQL Server where DNN (EBusiness) database
Name> exists.
<Database The name of the DNN (EBusiness) database that you want to
Name> upgrade.
<SQL User ID> The SQL Server User ID you use to log on to your Personify360
database. In most instances, this User ID will be either “TIMSS” or
“Personify.”
<SQL The password you have assigned to the SQL User ID. If you do not
Password> know this password, please contact a system administrator or enter a
Helpdesk ticket with Personify to assist you in recovering your
password.
4. Save your changes.

5. Double-click Runner.cmd to execute the database upgrade.
If you are running it from the database server itself (Windows 2008), you may need
to select “Run as Administrator.”

56
7.7.0 RELEASE NOTES

6. Review the UpgradeDatabase.log file and verify upgrade was successful.
If you are using web controls in your site, after the DNN (e-Business) site is
upgraded to 7.6.0, you must upgrade to the latest version Data Services and Web Controls
packages from release area.
PA-DSS
There are no changes in functionality. If you are performing a fresh installation of PADSS
Audit Logging Service, please see to the Personify360 7.7.0 Installation Guide.
Unified Search
There are no changes in functionality. If you are performing a fresh installation of Unified
Search, please see to the Personify360 7.7.0 Installation Guide.
Notification Service
If you are performing a fresh installation of notification services, please see to the
Personify360 7.7.0 Installation Guide. If you already have notification services, then please
follow the upgrade steps below.
To upgrade the Notification Service:
1. Stop the Notification Services, if already running.
2. Copy all of the files from the
...\7.7.0\Package\Services\NotificationServer\Upgrade folder to the Notification
Service folder.
3. Copy all of the SQL files from the
...\7.7.0\Package\Services\NotificationServer\Upgrade\Notification_Event_Proc
edures folder to the same folder for the new server.
This must be taken from the upgrade package.
4. If you are using Windows Server 2012, right-click the ConfigureNotificationService
file and select the “Run as Administrator” option.
Verify the configuration parameters as appropriate for the new environment, such as

57
7.7.0 RELEASE NOTES
the name of the database server, connection information, etc.
In a typical upgrade, no settings need to be changed on this screen. You

only need to change the settings if you have a new database server or email server.
5. Execute all modified SQL files on the Personify database by replacing the QUEUE
name with the queue name already installed in your production server. SQL files are
available in Base Procedures and Event Procedures tabs. Execute all SQL scripts.
This is will add the newly created notifications. Modified notification SQL files
information can be found in the Technical Changes > Notification Server
Changes section.
6. As of 7.6.2, the following SQL scripts in the
…\Databases\Notification_Event_Procedures From 7.6.2 folder need to be run
against the Personify360 database.
7. Open the Windows Service Management Console by clicking Start > Control Panel
> Administrative Tools > Services.
8. Restart the Notification Service.
Third-Party Interfaces
For information and instructions on upgrading each third-party interface application, please
refer to the related document. The following table lists the related document for upgrading
each third-party interface application.
Interface Application Related Documentation
ApexSQL Audit 2008 "APEXSQL Audit Logging" section of the 7.7.0 Online Help

58
7.7.0 RELEASE NOTES
The 7.7.0 Online Help can be accessed directly from your Personify360
application or via the Customer Support site. Please contact a Personify Business Analyst
for more information.
TRS
The TRS services should be reinstalled and the complete package should be deployed,
except for the customized processes. The customized process must be upgraded and
recompiled.
To upgrade TRS:
1. Stop the TRS Daemon Service, the Interface Service, and the TRS Cache Service.
2. Deploy all of the files from the ...7.7.0\Package\TRS\APPL folder in your upgrade
package to the TRS\APPL folder on your TRS Server.
See TRS Changes for more information on the changed executables.
3. Copy the TRSDaemonService.exe file and other files from the
...7.7.0\Package\Services\TRSServer folder to the TRSDaemon Service root folder.
4. Copy the TRSCacheService.exe file and other files from the
...7.7.0\Package\Services\CacheServer folder to the TRSCacheService root folder.
5. Copy the TimssInterfaceService.exe file and other files from the
...7.7.0\Package\Services\InterfaceServer folder to the TRSInterface Service root
folder.
6. Restart the following services:
 TRS Caching
 TRS Interface Service
 TRS Daemon Service
7. Rename TEMPLATE_Config.xml in the following folder to “Config.xml”:
...7.7.0\Package\TRS\APPL\Config
8. Open the Config.xml file.
9. Modify seat information and remoting entries for your organization, if changed.
Personify360 Home Page
To upgrade the Personify360 Home Page website to 7.7.0:
1. Make a backup of your site.

2. Copy all files from ...7.7.0\Package\PersonifyHomePage\Upgrade folder to the
Personify Home Page website root directory in the web server.
Passkey
To upgrade Passkey to 7.7.0:

59
7.7.0 RELEASE NOTES
1. Make a backup of your site.

2. Copy all files from ...7.7.0\Package\ThirdPartyInterfaces\Passkey folder to the
Personify passkey website root directory in the web server.
Image Services
If your organization allows mobile users to upload customer profile images or you include
product images on your product listing page, you should consider installing the Windows
Image Service. This service creates a Customer Images folder and helps you to standardize
the size of all uploaded images, ensuring that all customer profile images displayed in the
same size, as well as all product images. This way, your mobile users can upload an image
of any size and the application will not distort the image when it displays in the image space.
Additionally, if the back office Application Parameter is set in step 11 below, pictures will
display in Donor360® and CRM360®.
From the 7.4.1 release and onwards, Image Service is made mandatory
To install the Windows Service:
If Image Service is already configured then please proceed to step 6 directly.
If you have already configured Image service, proceed to step 15 (to upgrade
Image Service).
1. Update the ...7.7.0\Package\Service\PersonifyImageService folder path in the

Install.cmd and Uninstall.cmd files.
2. Open the Config.xml file and update the following:
 Seat Information
 App Service URL
3. The following values also appear in the PersonifyImageService.exe.config. You can
modify them as desired in the <appSettings> group.
Key Value Comments
CustomerImagePath (enter Web service will point to this directory for customer
the image URL.
URL)
ProductImagePath (enter Web service will point to this directory for product
the image URL.
URL)
EnableEventLogs False For Production

60
7.7.0 RELEASE NOTES
ProfileThumbnailHeight* 25 Customer Image

ProfileThumbnailWidth* 25 Customer Image
ProfilePictureWidth* 250 Customer Image
ProfilePictureHeight* 250 Customer Image
RefreshImageInterval 3600000 In milliseconds. Recommended 1 - 24 hrs.
These are the recommended values for the image sizes. The Profile
Height and width can go to 200 X 200 max. The image size should be < 100 K for
the best performance.
4. Save and close the Config.xml file.

5. Run the Install.cmd file from Command prompt.
6. If you are upgrading from 7.4.1 release, then please copy the TIMSS .dll files from
the following location to the Image Service installation folder:
...7.7.0\Package\Services\PersonifyImageService
7. Update “\ImageServer\Config\Config.xml” file by adding the following
“EnableAddModOperatorAlias” parameter:
<Item Name="UserInterface" SplashScreen="False"
ApplicationHostType="MDIMain"
StartupCommand="file://./HTMLPages\startscreen5.html"
ConfigFolder="Config" DefaultRole="CallCenterRep"
AdvancedThemes="True" DefaultTheme="TIMSS_Default.isl"
EnableAddModOperatorAlias="True" />
8. Go to services and click on Start to start the service.
If the service fails to start, check the application event log and/or your email for an
error report.
9. Go to your Web Server. Add a new Default Website; for example,
“CustomerImages”. Set the virtual directory path to CustomerImagePath from step 3.
For clients using Mobile this would be more secure Web server with
Public IP. For others, this can be any secure Intranet server.
Please make sure that “CustomerImages” path mentioned in

PersonifyImageService.exe.config file should match with the path mentioned in PIDB
database “T_##_AppInstance” table.
10. Login to the Personify back office.
11. From the Personify main toolbar, select System Admin > System Setup >
Application Parameters.
12. Search for the “APPLICATION_IMAGES_URL” parameter.

61
7.7.0 RELEASE NOTES
13. Enter the CustomerImagePath from step 3.

14. If staff wants to view pictures in the Donor360™ screen, then go to Applications
parameters, select the CUS subsystem, and update the
“USE_CONSTITUENT_IMAGES” value to ‘Y’.
To upgrade Image service:
1. Deploy all the content from ...7.7.0\Package\Services\ImageServer folder path to
the Image service root folder.
2. Make sure that SeatInformation key value in “ImageServer\Config\Config.xml” file
available in your local image service folder points to correct environment.
Online Help
With the 7.7.0 release, the Online Help files have been changed.
By default, the Help menu in Personify360 will open the local online help files
installed on the application server. Because these files are only the latest as of your
upgrade, the online help content will soon become out-of-date, as Personify is constantly
making improvements. Therefore, you have the option of configuring Personify360 to open a
centrally available Online Help:
https://resource1.personifycorp.com/PersonifyOnlineHelp/7.7.0/.
NOTE: This site requires a Single Sign-On (SSO) login. If some of your users do NOT have
a SSO login, it is recommended that you do NOT change the default configuration. You DO
have the option of providing BOTH links in the Help menu (see below for more information).
To upgrade Online Help to 7.7.0:
1. Delete all files and folders in your current Online Help folder configured under a
website.
2. Copy all files and folders from the following location to the Online Help website
folder:
...7.7.0\Package\OnlineHelp
3. It is recommended that you verify the following setting in the Config.xml and
Container.xml:
a. Open the Config.xml file in a text editor, such as Notepad.
b. Verify the values highlighted below:
<Item Name="HelpViewer"
Context="Personify"
Server="
http://[ONLINE_HELP_WEB_SERVER_NAME]/PersonifyOnlineHelp/"
ContentSensitiveHelp="index.htm?rhcsh=1&rhmapid={0}"
TOCFile="index.htm"

62
7.7.0 RELEASE NOTES
IndexFile="index.htm"
/>
c. Save the Config.xml file.

d. Open the Container.xml file in a text editor, such as Notepad.
e. Remove the following code if it exists:
<Tool Name="HelpIndex" Caption="_Index" Tooltip ="Index"
Command="cmd://App/ShowHelpIndex" Image="index.ico"/>
f. Customize your Help Desk to point to your organization’s help desk site by
changing the values as explained below and replacing contents highlighted:
<Tool Name="PersonifyCare" Caption="_PersonifyCare" Tooltip
="PersonifyCare"
Command="http://timsscare.tmaresources.com"
Image="lifebelt.ico"/>
 Name: the name of the support menu item.

 Caption: the name of the support menu item that will display in the Help
menu. For example, if you want this menu item to open your helpdesk site,
you may enter “_MyAssociation HelpDesk”.
Do NOT remove the underscore. For example:
Correct: “_MyAssociation HelpDesk”
Incorrect: “MyAssociation HelpDesk”
 Tooltip: the name of the tooltip that will display when users hover over the
menu item.
 Command: the support URL you want to open when the user clicks the
support menu item.
g. If you would like to provide a menu option to open the centrally located online
help (SSO login required), perform the following:
i. Enter the following code after the code shown in step 3f:
<Tool Name="OnlineHelp" Caption="_Online Help" Tooltip
="Online Help"
Command="cmd://App/Shell?FileName=https://resource1.personifyc
orp.com/PersonifyOnlineHelp/7.7.0/" BeginGroup="True"
Image="books.ico"/>
Please note that the context-sensitive help will still open the local online help
files when the user presses F1 on his/her keyboard. If you would rather have the centrally
located online help function as the context-sensitive help, you can enter

63
7.7.0 RELEASE NOTES
https://resource1.personifycorp.com/PersonifyOnlineHelp/7.7.0/ as the "Server" in the

Config.xml (see step 3b above).
4. Save the Container.xml file.
Custom Components
To upgrade your custom components to 7.7.0:
1. Launch Personify360 Enterprise through Auto Updater.

2. Launch the Database Designer and generate the Customer Generated Layer
(Personify.User.Generated.dll).
3. Deploy it to the following locations:
 Back Office Client Folder on the File Server
 e-Business Bin Folder (perform after upgrading the e-Business website)
 e-Business Web Service bin folder (perform after upgrading the e-Business web
service)
Do not run TIMSS.exe directly from the Server folder, as it would wipe out the
XML and TASK files for the screens.
5. Personify recommends that you rebuild/recompile the Customer Layer and deploy it
to the following locations:
 Back Office Client Folder on the File Server
 e-Business Bin Folder (perform after upgrading the e-Business website)
 e-Business Web Service bin folder (perform after upgrading the e-Business web
service)
6. If you have customized any base screens, identify the screen changes listed in Form
Changes and merge your changes using the Personify Application Designer.
Compile and publish all of the custom screens to the file server using the Personify
Application Designer.
7. Though publishing the screens is seamless using Personify Application Designer,
customer layer assemblies should be manually deployed.
After You Upgrade
1. Log in to the website.

If you are unsuccessful, then verify you configured ASP.NET and Network Service
properly.
2. Log in to the launcher.
3. Run a batch and an online report.
4. Reset the duplicate customer tables by performing the following:

64
7.7.0 RELEASE NOTES
a. Using the System Administrator persona, select Customers > Duplicate

Customers > Duplicate Customer Setup.
The Duplicate Customer Maintenance search screen displays.
b. On the search screen, click Tables to be Merged.
The Duplicate Customer - Related Tables screen displays.
c. Search for and select any table.
d. Uncheck the Active checkbox and click Save.
e. Check the Active checkbox again and click Save.
This generates the stored procedure that is used to merge customers. If you
perform this action for any one table, then all of the tables reset automatically.
After completing this step, you can confirm the

CUS595_UpdateDupCustomer_SP ran correctly by opening the stored
procedure and verifying the new date at the top of the SP.
5. Create a TRS User and Password account by performing the following:

a. From the Personify main toolbar, select System Admin > Configure and Verify
Interfaces.
b. From the TRS Interface task category, click Define User Account.
c. Define the "TRS_User_ID" and "TRS_USER_Password".
This is required for some TRS processes which use the Personify Dlls.
If your organization has multiple org units, you must create separate folders for
standard letters belonging to the different org units within your organization.

65
7.7.0 RELEASE NOTES
Technical Changes
API Base Changes
The following API base files were added or modified in this release:
File Location
AccountingValidationIssues. //API/Base/Namespaces/AccountingInfo/ValidationIssues/Ac
vb countingValidationIssues.vb
ApplicaitonProductQuestion. //API/Base/Namespaces/ApplicationInfo/Items/ApplicaitonPr
vb oductQuestion.vb
ApplicationGdprMasterCons //API/Base/Namespaces/ApplicationInfo/Items/ApplicationGd
entOptInOptOut.vb prMasterConsentOptInOptOut.vb
ApplicationOrganizationUnit. //API/Base/Namespaces/ApplicationInfo/Items/ApplicationOr
vb ganizationUnit.vb
ApplicationProductQuestion //API/Base/Namespaces/ApplicationInfo/Collections/Applicati
s.vb onProductQuestions.vb
ApplicationQuestionAnswer. //API/Base/Namespaces/ApplicationInfo/Items/ApplicationQu
vb estionAnswer.vb
ApplicationValidationIssues. //API/Base/Namespaces/ApplicationInfo/ValidationIssues/Ap
vb plicationValidationIssues.vb
ARReceipt.vb //API/Base/Namespaces/AccountingInfo/Items/ARReceipt.vb
ARReceipts.vb //API/Base/Namespaces/AccountingInfo/Collections/ARRece
ipts.vb
ARVouchers.vb //API/Base/Namespaces/AccountingInfo/Collections/ARVouc
hers.vb
Cancellation.vb //API/Base/Namespaces/OrderInfo/Helper/Cancellation.vb
CertificationCustomerCertifi //API/Base/Namespaces/CertificationInfo/Items/Certification
cation.vb CustomerCertification.vb
CertificationCustomerRequir //API/Base/Namespaces/CertificationInfo/Items/Certification
ementDetail.vb CustomerRequirementDetail.vb

66
7.7.0 RELEASE NOTES
CommitteeMember.vb //API/Base/Namespaces/Committee
Info/Items/CommitteeMember.vb
CommonHelper.vb //API/Base/Miscellaneous/CommonHelper.vb
Customer.vb //API/Base/Namespaces/CustomerInfo/Items/Customer.vb
CustomerActivities.vb //API/Base/Namespaces/CustomerInfo/Collections/Customer
Activities.vb
CustomerActivityDocument. //API/Base/Namespaces/CustomerInfo/Items/CustomerActivi
vb tyDocument.vb
CustomerActivityViewList.vb //API/Base/Namespaces/CustomerInfo/Collections/Customer
ActivityViewList.vb
CustomerAddress.vb //API/Base/Namespaces/CustomerInfo/Items/CustomerAddr
ess.vb
CustomerAddressDetail.vb //API/Base/Namespaces/CustomerInfo/Items/CustomerAddr
essDetail.vb
CustomerCommunication.vb //API/Base/Namespaces/CustomerInfo/Items/CustomerCom
munication.vb
CustomerCouponWithAmou //API/Base/Namespaces/CustomerInfo/Items/CustomerCoup
ntView.vb onWithAmountView.vb
CustomerDuplicateMergeTa //API/Base/Namespaces/CustomerInfo/Collections/Customer
bles.vb DuplicateMergeTables.vb
CustomerGdprActivities.vb //API/Base/Namespaces/CustomerInfo/Collections/Customer
GdprActivities.vb
CustomerGdprActivity.vb //API/Base/Namespaces/CustomerInfo/Items/CustomerGdpr
Activity.vb
CustomerHousehold.vb //API/Base/Namespaces/CustomerInfo/Items/CustomerHous
ehold.vb
CustomerRelatedDocument. //API/Base/Namespaces/CustomerInfo/Items/CustomerRelat
vb edDocument.vb
CustomerRelationship.vb //API/Base/Namespaces/CustomerInfo/Items/CustomerRelat
ionship.vb
Customers.vb //API/Base/Namespaces/CustomerInfo/Collections/Customer
s.vb

67
7.7.0 RELEASE NOTES
CustomerValidationIssues.v //API/Base/Namespaces/CustomerInfo/ValidationIssues/Cus
b tomerValidationIssues.vb
ExhibitionProductBooth.vb //API/Base/Namespaces/ExhibitionInfo/Items/ExhibitionProd
uctBooth.vb
FundRaisingCustomerSolicit //API/Base/Namespaces/FundRaisingInfo/Items/FundRaisin
orTeam.vb gCustomerSolicitorTeam.vb
FundRaisingProspectMoves //API/Base/Namespaces/FundRaisingInfo/Items/FundRaisin
Plan.vb gProspectMovesPlan.vb
LockBoxReceiptDist.vb //API/Base/Namespaces/LockboxInfo/Items/LockBoxReceipt
Dist.vb
MarketingMailMaster.vb //API/Base/Namespaces/MarketingInfo/Items/MarketingMail
Master.vb
MarketingProspect.vb //API/Base/Namespaces/MarketingInfo/Items/MarketingPros
pect.vb
NotificationserviceNotificatio //API/Base/Namespaces/NotificationServiceInfo/Items/Notific
nSentMessage.vb ationserviceNotificationSentMessage.vb
OrderAdvancedAdjustments //API/Base/Namespaces/AccountingInfo/Helper/OrderAdvan
.vb cedAdjustments.vb
OrderBalanceWriteoff.vb //API/Base/Namespaces/AccountingInfo/Helper/OrderBalanc
eWriteoff.vb
OrderDetail.vb //API/Base/Namespaces/OrderInfo/Items/OrderDetail.vb
OrderDiscounts.vb //API/Base/Namespaces/OrderInfo/Helper/OrderDiscounts.v
b
OrderMaster.vb //API/Base/Namespaces/OrderInfo/Items/OrderMaster.vb
OrderMasters.vb //API/Base/Namespaces/OrderInfo/Collections/OrderMasters
.vb
OrderPurchasingGroup.vb //API/Base/Namespaces/OrderInfo/Items/OrderPurchasingG
roup.vb
OrderTransfer.vb //API/Base/Namespaces/OrderInfo/Helper/OrderTransfer.vb
OrderValidationIssues.vb //API/Base/Namespaces/OrderInfo/ValidationIssues/OrderVa
lidationIssues.vb

68
7.7.0 RELEASE NOTES
PersonaSecurityOrganizatio //API/Base/Namespaces/PersonaSecurityInfo/Items/Persona
nMember.vb SecurityOrganizationMember.vb
Product.vb //API/Base/Namespaces/ProductInfo/Items/Product.vb
ProductAccount.vb //API/Base/Namespaces/ProductInfo/Items/ProductAccount.
vb
ProductCancelFee.vb //API/Base/Namespaces/ProductInfo/Items/ProductCancelFe
e.vb
ProductRateCode.vb //API/Base/Namespaces/ProductInfo/Items/ProductRateCod
e.vb
ProductRelation.vb //API/Base/Namespaces/ProductInfo/Items/ProductRelation.
vb
Products.vb //API/Base/Namespaces/ProductInfo/Collections/Products.vb
ReportingApplication.vb //API/Base/Namespaces/ReportingInfo/Items/ReportingAppli
cation.vb
Returns.vb //API/Base/Namespaces/OrderInfo/Helper/Returns.vb
Shipping.vb //API/Base/Namespaces/OrderInfo/Helper/Shipping.vb
SubscriptionIssue.vb //API/Base/Namespaces/SubscriptionInfo/Items/Subscription
Issue.vb
TranscriptProgramExam.vb //API/Base/Namespaces/TranscriptInfo/Items/TranscriptProg
ramExam.vb
WebShoppingCartItem.vb //API/Base/Namespaces/WebInfo/Items/WebShoppingCartIt
em.vb
API Core Changes
The following API core files were added or modified in this release:
File Location
AccountVerification.vb /API/Core/Third Party

Interfaces/PaymentHandlerInterface/AccountVerification.vb

69
7.7.0 RELEASE NOTES
ApplicationRuntimeParam /API/Core/Application/ApplicationRuntimeParameters.vb
eters.vb
Authorization.vb /API/Core/Third Party

Interfaces/PaymentHandlerInterface/Authorization.vb
CCProcessingInterface.vb /API/Core/Credit Card Interface/CCProcessingInterface.vb
CustomerProfile.vb /API/Core/Third Party

Interfaces/PaymentHandlerInterface/CustomerProfile.vb
Functions.vb /API/Core/Helper/Classes/Functions.vb
ISearchObject.vb /API/Core/Search/ISearchObject.vb
SearchObject.vb /API/Core/Search/SearchObject.vb
ApplicationRuntimeParam /API/Core/Application/ApplicationRuntimeParameters.vb
eters.vb
BusinessObject.vb /API/Core/BusinessObjects/BusinessObject.vb
CacheLoader.vb /API/Core/Application/CacheLoader.vb
Configuration Template Changes
The following configuration template files were added or modified in this release:
 TEMPLATE_Config.xml
Database Changes
The following database files were added or modified in this release:
Database Function Changes
 CheckIsCustomerTaxExempt.SQL
 GetCusRateStructure.SQL
 udf_ContactTrackingCount.sql
 udf_ContactTrackingList.sql
 udf_GetContactTrackingRecords.sql

70
7.7.0 RELEASE NOTES
 udf_GetCusInvolvementDataIncludingPrimaryEmployer.sql
 udf_GetCustomerInfoForOrder.sql
 udf_GetDefaultShipVia.SQL
 udf_GetDeliveryMethodForCustomerOptIn.sql
 udf_GetFavoriteItems.sql
 udf_GetFreeMembershipSubscriptions.SQL
 udf_GetLatestContactTraking.sql
 udf_GetMembershipChapters.SQL
 udf_getPayMethodInfo.SQL
 udf_GetRecentItemHistory.sql
 udf_GetSelectedDate.sql
 udf_GetSpecialInterestGroups.SQL
 udf_GetSystemDefaultAccounts.SQL
 udf_GetTaxRatesForProduct.sql
 udf_GetZipLinkedProducts.sql
 udf_IsCommitteeMemberValid.sql
 udf_IsDiscountQualifies.sql
 udf_OrderBalanceForOrderHistory.sql
 udf_ComputeFormalSalutation.sql
 udf_ComputeLabelName.sql
 udf_ComputeLastFirstName.sql
 udf_ComputeSearchName.sql
 udf_Concat_Name_Components.sql
 udf_GETCUS595_FILES_DATA.sql
 udf_GetQualifiedRateStructures.SQL
 udf_SplitStringToTable.SQL
Data Script Changes
 ADD_APP_PARAMETER_FOR_GDPR_CONSENT.SQL
 ADD_APP_PARAMETER_FOR_GDPR_CONSENT_OPTOUT_ACTIVITY_TEXT.sql
 ADD_APP_PARAMETER_FOR_GDPR_DEFAULT_ANONYMOUS_STRING.sql
 ADD_APP_PARAMETER_FOR_GDPR_DEFAULT_EMAIL_STRING.sql
 ADD_APP_PARAMETER_FOR_GDPR_DEFAULT_EXPIRATION_DAYS.sql
 ADD_APP_PARAMETER_FOR_GDPR_DNN_DEFAULT_STRING.sql
 ADD_APP_PARAMETER_FOR_GDPR_HEAD.sql
 ADD_PSM_APPLICATION_NOVUS_3.sql
 APP_CODE_COMM_TYPE_PREFERRED.sql
 APP_GDPR_DATA_SETUP.sql

71
7.7.0 RELEASE NOTES
 APP_PARAMETER_PASSPHRASE.sql
 APP_TYPE_CODE_FAVORITE.sql
 APP_TYPE_CODE_FOR_CUSTOMER_STATUS.sql
 APP_TYPE_CODE_FOR_GDPR.sql
 APP_TYPE_CODE_FOR_GDPR_CONTACT_TRACKING.sql
 APP_TYPE_CODE_FOR_GDPR_DATA_CATEGORY.sql
 APP_TYPE_CODE_FOR_NCOA.sql
 APP_TYPE_CODE_WORLD_BANK_REGION_DISCOUNT.SQL
 APP_TYPE_CODE_WORLD_REGION_DISCOUNT.SQL
 CRM360_SQLJOB_Old_Trigger_Drop.sql
 CUS_GDPR_INQUIRY_Online_Report_Setup.sql
 CUS_GDPR_Request_Received_List_Report_Setup.sql
 FND681_TRS_SETUP.sql
 Insert_APP_INTERFACE_PARAMETER_FOR_NCOA.sql
 NCOA_Online_Job_Process_Report_Setup.sql
 NCOA_Online_Job_Status_Report_Setup.sql
 NTS_RESEND_EMAIL_NOTIFICATION.sql
 ORD650_RETAIN_ORDER_PAYMENT_SCHEDULE_PARAM.sql
 PGR100_HELP_TEXT_UPDATE.sql
 PGR100_TRS_SETUP.sql
 PSM_APPLICATION_GDPR.sql
 PSM_APPLICATION_NOVUS_ACCOUNTINGBATCH.sql
 PSM_APPLICATION_NOVUS_COMMITTEE_CHOOSER.SQL
 PSM_APPLICATION_NOVUS_DASHBOARD.SQL
 PSM_APPLICATION_NOVUS_MEETING.SQL
 PSM_APPLICATION_NOVUS_ORDER.SQL
 PSM_APPLICATION_PERMISSION_FOR_GDPR.sql
 PSM_Application_ProspectChooser.sql
 PSM_PERSONA_MENU_BASE_GDPR.sql
 SchJobNCOAETLJobId.sql
 UPDATE_APP_TYPE_GDPR_DATA_CATEGORY.sql
 Update_Nts_Notification.sql
 UPDATE_NTS_NOTIFICATION_DETAIL.sql
 UPDATE_PSM_USER_RECENT_ITEM_HISTORY.sql
 UPDATE_ZIP100_TRS_APPLICATION_PARAMETER.Sql
 ADD_APP_PARAMETER_FOR_OUT_OF_STOCK_BACK_ORDER_SPLIT_FLAG.s
ql
 BaseDefect_14372_Script.sql

72
7.7.0 RELEASE NOTES
 PSM_ACCESSPOINT_TRS200_JOB_DELETION.sql
 UPDATE_MTG510_PROCESS_PARAMETER.sql
Stored Procedure Changes
 AddComponents.SQL
 AddPaymentSchedule.SQL
 CreateOrderDetail.SQL
 CreateOrderMaster.SQL
 CreateSalesTxn.SQL
 CRT_Renewal_SP.SQL
 CrtReAnalyze_sp.SQL
 FAR610_SP.SQL
 far675_set_data_sp.SQL
 FAR695_Process_SP.SQL
 GetSchedulePrice.SQL
 GetShippingAmount.SQL
 LCK100_CreateDonation_SP.SQL
 MBR900_InsUpd_CCMBI_SP.SQL
 OLS_PRODUCT_MTG_FACET_INFO_ADD_DATA.sql
 OLS_PRODUCT_MTG_FACET_INFO_ADD_DATA_INCREMENTAL.sql
 OLS_SEARCH_MTG_PRODUCT.sql
 ORD650_Process_Sp.SQL
 ord660_sp.SQL
 PGR100_PROCESS_SP.sql
 SaveOrder.SQL
 UpdateDiscount.SQL
 UpdateTax.SQL
 usp_ActivateOrderLine.SQL
 usp_AddWriteoffTransaction.SQL
 Usp_canactivateorderline.SQL
 USP_CLEAR_PURCHASING_GROUP_LIST.sql
 USP_FILL_CRM360_SQL_JOB_CHRONICLE.sql
 usp_GDPR_DATA_CLEANUP.sql
 usp_GDPR_FORGET_CONSTITUENT.SQL
 usp_GDPR_FORGET_CONSTITUENT_VALIDATE.sql
 usp_GDPR_PROCESS_REQUEST.sql
 usp_GDPR_RIGHT_TO_BE_FORGOTTEN.sql
 usp_GDPR_RIGHT_TO_BE_FORGOTTEN_ADDITIONAL_TABLES.sql

73
7.7.0 RELEASE NOTES
 usp_GetCusInvolvementInfo.sql
 usp_GetCusLatestOrders.sql
 usp_GetShippingAmount.SQL
 USP_ICS_FILE_CREATION.sql
 usp_InsertUpdateCusInvolvementInfo.sql
 usp_InsertUpdateRecentItemHistory.sql
 usp_MEMBERDIRECTORY_DETAIL_SEARCH_CHAPTER.sql
 usp_MEMBERDIRECTORY_DETAIL_SEARCH_NATIONAL.sql
 usp_MEMBERDIRECTORY_DETAIL_SEARCH_TRADE.sql
 usp_MEMBERDIRECTORY_SEARCH_CHAPTER.sql
 usp_MEMBERDIRECTORY_SEARCH_NATIONAL.sql
 usp_MEMBERDIRECTORY_SEARCH_TRADE.sql
 usp_NCOA_INPUT_FILE_CREATION_DATA.sql
 usp_NCOA_OUTPUT_FILE_CREATION_DATA.sql
 usp_NCOA_P360_UPDATE_CUS_ADDRESS.sql
 usp_NCOA_P360_VALID_RECORDS.sql
 usp_NCOA_P360_VALIDATION.sql
 usp_NCOA_VeriMove_VALIDATION.sql
 usp_ORD650_Process_SP.SQL
 usp_POPULATE_MEMBERDIRECTORY_DATA_INSERT.sql
 usp_Populate_RPT_DATA.SQL
 usp_RunCRM360_SQLJob.sql
 Usp_updatecommunicationhistory.SQL
 usp_UpdateOrderTotals.SQL
 usp_UpdateTax.SQL
 usp_Web_Get_Customers_By_Email.sql
 WEB_PRODUCT_INFO_ADD_DATA.sql
 WEB_PRODUCT_INFO_ADD_DATA_INCREMENTAL.sql
 AddComponents.SQL
 CreateCertification_On_Purchase_sp.SQL
 CreateOrderDetail.SQL
 CRT_Renewal_SP.SQL
 CRT500_SP.SQL
 CrtReAnalyze_sp.SQL
 MKT800_Process_SP.SQL
 ord660_sp.SQL
 UpdateCusCertReqDetCompletionInfo.SQL
 USP_FILL_CRM360_SQL_JOB_CHRONICLE.sql

74
7.7.0 RELEASE NOTES
 usp_Merge_CustomerNameDetails.sql
 usp_RunCRM360_SQLJob.sql
Table Changes
The following tables were added:
 APP_GDPR_CONSENT_OPT_IN_OPT_OUT_HISTORY.sql
 APP_GDPR_DATA_COLUMNS.SQL
 APP_GDPR_DATA_INQUIRY_HISTORY.sql
 APP_GDPR_DATA_TABLE.SQL
 APP_GDPR_MASTER_CONSENT_OPT_IN_OPT_OUT.sql
 APP_GDPR_MASTER_RETENTION_REFERENCE.sql
 APP_POSTAL_CODE.SQL
 CCP_VANTIV_FILE_RESPONSE_RECORDS.sql
 CUS_GDPR_ACTIVITY.sql
 FAR_RECEIPT_DETAIL_DTO.SQL
 NCOA_INPUT_JOB.sql
 NCOA_OUTPUT_JOB.sql
 NCOA_STAGING_CUS_ADDRESS.sql
 NCOA_TEMP_ADDRESS_DATA.sql
 NON_REFUNDABLE_LINE_DETAIL_DTO.SQL
 NTS_NOTIFICATION_SENT_MESSAGE.SQL
 OLS_MTG_PRODUCT_SEARCH.sql
 ORD_CANCELLATION_TAX_DETAIL_DTO.SQL
 ORD_PURCHASING_GROUP.SQL
 ORDER_DETAIL.SQL
 PGR100_PROCESS_RECORDS.SQL
 PRODUCT_PRICING.SQL
 PSM_USER_BOE_REPORTS_PARAMS.SQL
 PSM_USER_DASHBOARD_CARD_SETTING.sql
 PSM_USER_FAVORITE.sql
 PSM_USER_FAVORITE_ACTION.sql
 PSM_USER_FAVORITE_CONSTITUENT.sql
 PSM_USER_LOGIN_HISTORY.SQL
 PSM_USER_RECENT_ITEM_HISTORY.sql
 RATE_STRUCTURE_DEFAULT.SQL
 REFUND_DETAIL_DTO.SQL
 REFUND_DETAIL_ORDER_DETAIL_DTO.SQL

75
7.7.0 RELEASE NOTES
 REFUND_DTO.SQL
 REFUNDABLE_LINE_DETAIL_DTO.SQL
 RPT_CUSTOMER_DEMOGRAPHIC_WIDGET.sql
 RPT_CUSTOMER_SUMMARY_WIDGET.sql
 RPT_ORDER_SUMMARY_WIDGET.sql
 TRANSFER_DTO.sql
 TRANSFER_ORDER_DETAIL_DTO.sql
 WEB_SHOPPING_CART_ITEM_QUESTIONNAIRE.sql
 OLS_MTG_PRODUCT_SEARCH.sql
The following tables were modified:
 APP_COUNTRY.SQL
 CRM360_SQL_JOB_DATA_PREP.sql
 CUS_COMMUNICATION.SQL
 FAR_TXN.SQL
 MKT_MAIL_MASTER.SQL
 PSM_USER.SQL
Trigger Changes
 APP_GDPR_MASTER_CONSENT_OPT_IN_OPT_OUT_trgIU.sql
 Ccp_Req_Ans_TrgU.SQL
 COM_COMMITTEE_MEMBER_CRM360_SQL_JOB_trgIUD.sql
 COM_COMMITTEE_MEMBER_CRM360_SQL_JOB_trgUD.sql
 cus_address_trgIU.SQL
 CUS_GDPR_ACTIVITY_trgIU.sql
 FAR_TXN_CRM360_SQL_JOB_trgIUD.sql
 FAR_TXN_CRM360_SQL_JOB_trgUD.sql
 far_txn_trgI.SQL
 ORDER_DETAIL_COUPON_TRGI.SQL
 ORDER_DETAIL_COUPON_TRGU.SQL
 ORDER_MASTER_CRM360_SQL_JOB_trgIUD.sql
 ORDER_MASTER_CRM360_SQL_JOB_trgU.sql
 ORDER_MBR_ASSOCIATE_CRM360_SQL_JOB_trgIUD.sql
 ORDER_MBR_ASSOCIATE_CRM360_SQL_JOB_trgUD.sql
 PRODUCT_ONLINE_STORE_TRG_IUD.SQL
 trn_cus_transcript_trgI.SQL
 trn_cus_transcript_trgU.SQL
 ORDER_DETAIL_EFT_INFO_TRGIU.sql

76
7.7.0 RELEASE NOTES
 order_detail_trgIU.SQL
 Sec_Appl_trgIU.SQL
View Changes
 CUS_ACTIVITY_VW.sql
 CUS_BANK_ACCOUNT_CHOOSER_VW.sql
 CUS_COUPON_WITH_AMOUNT_VW.sql
 CUS_EMPLOYEE_SEARCH_BY_COMPANY_VW.SQL
 CUS_SEGMENT_MEMBER_VW.SQL
 CUS_STATUS_VW.SQL
 MTG_REGISTRANTS_VW.sql
 ORD_ORDER_HISTORY_VW.SQL
 ORDER_BALANCE_VW.SQL
 TRS_USER_PSM_ONLINE_REPORT_VW.SQL
 WEB_MBR_JOIN_PRODUCTS_VW.sql
Form Changes
The following forms were added or modified in this release:
 ORD001P.xml
 ORD001QA.xml
 ORD101.xml
 PRODUCTCENTRAL.xml
 ProspectChooser.xml
 ProspectFormattedDetails.xml
 SubgroupCentral.xml
 TRS100.xml
 TRS101.xml
 TRS103.xml
 TRS200.xml
Personify Home Page Changes
The following home page files were modified in this release:
 DefaultHomePage.aspx
 FundRaisingHomePage.aspx

77
7.7.0 RELEASE NOTES
Notification Server Changes
The following notification server files were added or modified in this release:
File Location
usp_NOTIFIY_RESEND_NOTI /Server/Personify.Server.Notification.Service/NTS_Event
FICATION.sql _Procedures/Events/usp_NOTIFIY_RESEND_NOTIFICA
TION.sql
usp_NOTIFY_NEW_MEETING /Server/Personify.Server.Notification.Service/NTS_Event
_ORDER.SQL _Procedures/Events/usp_NOTIFY_NEW_MEETING_OR
DER.SQL
usp_NOTIFY_NEW_MEETING /Server/Personify.Server.Notification.Service/NTS_Event
_REGISTRATION_CREATED_ _Procedures/Events/usp_NOTIFY_NEW_MEETING_RE
BY_SELF_OR_MANAGER.sql GISTRATION_CREATED_BY_SELF_OR_MANAGER.sq
l
usp_NOTIFY_RESEND_CHR /Server/Personify.Server.Notification.Service/NTS_Event
ONICLE.sql _Procedures/Chronicles/usp_NOTIFY_RESEND_CHRO
NICLE.sql
usp_NTS_NOTIFICATION_AD /Server/Personify.Server.Notification.Service/NTS_Event
D_BASE_NOTIFY_EVENTS.s _Procedures/Base
ql System/usp_NTS_NOTIFICATION_ADD_BASE_NOTIFY
_EVENTS.sql
usp_NTS_NOTIFICATION_SA /Server/Personify.Server.Notification.Service/NTS_Event
VE_MESSAGE.sql _Procedures/Base
System/usp_NTS_NOTIFICATION_SAVE_MESSAGE.sq
l
SSO/IMS Changes
The following SSO/IMS files were added or modified in this release:
File Location
Association.vb /SSO_IMS/SSO.Base/TIMSSSSO.Business/Association.vb

78
7.7.0 RELEASE NOTES
AutoLogin.aspx.vb /SSO_IMS/SSO.Base/TIMSSSSO.Web/AutoLogin.aspx.vb
Customer.vb /SSO_IMS/IdentityManagementSolution/IMSObjects/Custom
er.vb
Customer.vb /SSO_IMS/SSO.Base/TIMSSSSO.Business/Customer.vb
DeleteAnonymizedCustom /SSO_IMS/SSO.Base/TIMSSSSO.Common/Database/TMAR
er.sql /DeleteAnonymizedCustomer.sql
ExceptionMessages.vb /SSO_IMS/SSO.Base/TIMSSSSO.Business/ExceptionMessa
ges.vb
ForgotPasswordResetUser /SSO_IMS/SSO.Base/TIMSSSSO.Web/usercontrols/ForgotP
Control.ascx.vb asswordResetUserControl.ascx.vb
IMSRole.vb /SSO_IMS/IdentityManagementSolution/IMSObjects/IMSRole
.vb
LogHandler.vb /SSO_IMS/SSO.Base/TIMSSSSO.Business/LogHandler.vb
LoginUserBase.vb /SSO_IMS/SSO.Base/TIMSSSSO.Web/LoginUserBase.vb
RegisterUserControl.ascx.v /SSO_IMS/SSO.Base/TIMSSSSO.Web/usercontrols/Register
b UserControl.ascx.vb
service.asmx.vb /SSO_IMS/SSO.Base/TIMSSSSO.Web/webservice/service.a
smx.vb
Session.vb /SSO_IMS/SSO.Base/TIMSSSSO.Business/Session.vb
SSODeleteAnonymizedCu /SSO_IMS/SSO.Base/TIMSSSSO.Web/webservice/SSODele
stomer.vb teAnonymizedCustomer.vb
UserControlBase.vb /SSO_IMS/SSO.Base/TIMSSSSO.Web/usercontrols/UserCo
ntrolBase.vb
UserNameResetUserContr /SSO_IMS/SSO.Base/TIMSSSSO.Web/usercontrols/UserNa
ol.ascx.vb meResetUserControl.ascx.vb

79
7.7.0 RELEASE NOTES
Vendor.vb /SSO_IMS/IdentityManagementSolution/IMSObjects/Vendor.
vb
Vendor.vb /SSO_IMS/SSO.Base/TIMSSSSO.Business/Vendor.vb
WebServiceSecurity.sql /SSO_IMS/SSO.Base/TIMSSSSO.Common/Database/TMAR
/Data/WebServiceSecurity.sql
WebServiceSecurity.sql /SSO_IMS/SSO.Base/TIMSSSSO.Common/Database/TMAR
/Data/WebServiceSecurity.sql
TRS Changes
The following TRS files were added or modified in this release:
TRS Data Access Layer Changes
File Location
clsAccountingCommon.vb /TRS/Source/DataAccessLayer/TimssDB/Classes/Subsystems
/Accounting/clsAccountingCommon.vb
clsReceiptTransaction.vb /TRS/Source/DataAccessLayer/TimssDB/Classes/Subsystems
/Accounting/clsReceiptTransaction.vb
clsSaleTransaction.vb /TRS/Source/DataAccessLayer/TimssDB/Classes/Subsystems
/Accounting/clsSaleTransaction.vb
clsTRS.vb /TRS/Source/DataAccessLayer/TimssDB/Classes/Subsystems
/Reporting System/clsTRS.vb
TRS Interface Changes
File Location
clsCDQPSetup.vb /TRS/Source/Interfaces/TimssInterface_PABP/Classes/
clsCDQPSetup.vb

80
7.7.0 RELEASE NOTES
clsTimssADRInterface.vb /TRS/Source/Interfaces/TimssInterface_PABP/Classes/
clsTimssADRInterface.vb
clsVantivInterface.vb /TRS/Source/Interfaces/TimssInterface_PABP/Classes/
CCPInterface/Vantiv/clsVantivInterface.vb
TRS Process Changes
File Location
clsBusinessObjects.vb /TRS/Source/TRS_CrystalXI/TRSLibrary/Classes/clsBusinessObj
ects.vb
clsCCP610.vb /TRS/Source/TRS_CrystalXI/CCP610/Classes/clsCCP610.vb
clsCUS595.vb /TRS/Source/TRS_CrystalXI/CUS595/Classes/clsCUS595.vb
clsEFT680.vb /TRS/Source/TRS_CrystalXI/EFT680/Classes/clsEFT680.vb
clsFAR680.vb /TRS/Source/TRS_CrystalXI/FAR680/Classes/clsFAR680.vb
clsFAR681.vb /TRS/Source/TRS_CrystalXI/FAR681/Classes/clsFAR681.vb
clsFND681E.vb /TRS/Source/TRS_CrystalXI/FND681/Classes/clsFND681E.vb
clsFND681I.vb /TRS/Source/TRS_CrystalXI/FND681/Classes/clsFND681I.vb
clsLCK100.vb /TRS/Source/TRS_CrystalXI/LCK100/Classes/clsLCK100.vb
clsMKT500.vb /TRS/Source/TRS_CrystalXI/MKT500/Classes/clsMKT500.vb
clsORD650.vb /TRS/Source/TRS_CrystalXI/ORD650/Classes/clsORD650.vb
clsPayment.vb /TRS/Source/TRS_CrystalXI/EFT680/Classes/clsPayment.vb
clsPayment.vb /TRS/Source/TRS_CrystalXI/FAR680/Classes/clsPayment.vb
clsPGR100.vb /TRS/Source/TRS_CrystalXI/PGR100/Classes/clsPGR100.vb
clsSUB670.vb /TRS/Source/TRS_CrystalXI/SUB670/Classes/clsSUB670.vb

81
7.7.0 RELEASE NOTES
clsSub671.vb /TRS/Source/TRS_CrystalXI/SUB671/Classes/clsSub671.vb
modCUS595.vb /TRS/Source/TRS_CrystalXI/CUS595/Modules/modCUS595.vb
modMain.vb /TRS/Source/TRS_CrystalXI/EFT680/Modules/modMain.vb
modMain.vb /TRS/Source/TRS_CrystalXI/FAR681/Modules/modMain.vb
modMain.vb /TRS/Source/TRS_CrystalXI/FND681/Modules/modMain.vb
modMain.vb /TRS/Source/TRS_CrystalXI/INV620/Modules/modMain.vb
modMain.vb /TRS/Source/TRS_CrystalXI/LCK100/Modules/modMain.vb
modMain.vb /TRS/Source/TRS_CrystalXI/PGR100/Modules/modMain.vb
modMain.vb /TRS/Source/TRS_CrystalXI/ZIP100/Modules/modMain.vb
modORD650Main.vb /TRS/Source/TRS_CrystalXI/ORD650/Modules/modORD650Mai
n.vb
clsCUS595.vb /TRS/Source/TRS_CrystalXI/CUS595/Classes/clsCUS595.vb
clsMKT800_V2.vb /TRS/Source/TRS_CrystalXI/MKT800/Classes/clsMKT800_V2.vb
modCUS595.vb /TRS/Source/TRS_CrystalXI/CUS595/Modules/modCUS595.vb
modMain.vb /TRS/Source/TRS_CrystalXI/LCK100/Modules/modMain.vb
modMain.vb /TRS/Source/TRS_CrystalXI/MTG510/Modules/modMain.vb
TRS Report Changes
File Location
ADV620_Invoice.rpt /TRS/Source/TRS_CrystalXI/ADV620/Reports/ADV620_Invo
ice.rpt
COM1200CE.rpt /TRS/Source/OLR_CrystalXI/COM/COM1200CE.rpt

82
7.7.0 RELEASE NOTES
COM1200CI.rpt /TRS/Source/OLR_CrystalXI/COM/COM1200CI.rpt
COM1200PE.rpt /TRS/Source/OLR_CrystalXI/COM/COM1200PE.rpt
COM1200PI.rpt /TRS/Source/OLR_CrystalXI/COM/COM1200PI.rpt
COM1201CI.rpt /TRS/Source/OLR_CrystalXI/COM/COM1201CI.rpt
COM1201PI.rpt /TRS/Source/OLR_CrystalXI/COM/COM1201PI.rpt
COM1203PE.rpt /TRS/Source/OLR_CrystalXI/COM/COM1203PE.rpt
CRM1000.rpt /TRS/Source/OLR_CrystalXI/CRM/CRM1000.rpt
CUS_GDPR_Data_Inquiry.r /TRS/Source/OLR_CrystalXI/CUS/CUS_GDPR_Data_Inquir
pt y.rpt
CUS_GDPR_Request_Rec /TRS/Source/OLR_CrystalXI/CUS/CUS_GDPR_Request_R
eived_List.rpt eceived_List.rpt
CUS_NCOA_JOB_PROCE /TRS/Source/OLR_CrystalXI/CUS/CUS_NCOA_JOB_PROC
SS.rpt ESS.rpt
CUS_NCOA_JOB_STATUS /TRS/Source/OLR_CrystalXI/CUS/CUS_NCOA_JOB_STAT
.rpt US.rpt
FND1210.rpt /TRS/Source/OLR_CrystalXI/FND/FND1210.rpt
FND1211.rpt /TRS/Source/OLR_CrystalXI/FND/FND1211.rpt
FND630_Letter.rpt /TRS/Source/TRS_CrystalXI/FND630/Reports/FND630_Lett
er.rpt
FND630_LISTING.rpt /TRS/Source/TRS_CrystalXI/FND630/Reports/FND630_LIS
TING.rpt
FND660_Letter.rpt /TRS/Source/TRS_CrystalXI/FND660/Reports/FND660_Lett
er.rpt
FND660_Listing.rpt /TRS/Source/TRS_CrystalXI/FND660/Reports/FND660_Listi
ng.rpt

83
7.7.0 RELEASE NOTES
INV2006.rpt /TRS/Source/OLR_CrystalXI/INV/INV2006.rpt
MTG1200CE.rpt /TRS/Source/OLR_CrystalXI/MTG/MTG1200CE.rpt
MTG1200CI.rpt /TRS/Source/OLR_CrystalXI/MTG/MTG1200CI.rpt
MTG1200PE.rpt /TRS/Source/OLR_CrystalXI/MTG/MTG1200PE.rpt
MTG1200PI.rpt /TRS/Source/OLR_CrystalXI/MTG/MTG1200PI.rpt
MTG1201C.rpt /TRS/Source/OLR_CrystalXI/MTG/MTG1201C.rpt
MTG1201P.rpt /TRS/Source/OLR_CrystalXI/MTG/MTG1201P.rpt
MTG1204PE.rpt /TRS/Source/OLR_CrystalXI/MTG/MTG1204PE.rpt
MTG1204PI.rpt /TRS/Source/OLR_CrystalXI/MTG/MTG1204PI.rpt
ORD660.rpt /TRS/Source/TRS_CrystalXI/ORD660/Reports/ORD660.rpt
ORD660_BadAdd.rpt /TRS/Source/TRS_CrystalXI/ORD660/Reports/ORD660_Ba
dAdd.rpt

84
7.7.0 RELEASE NOTES
ORD660_BadAddress.rpt /TRS/Source/TRS_CrystalXI/ORD660/Reports/ORD660_Ba
dAddress.rpt
ORD660_BadEmailAddress /TRS/Source/TRS_CrystalXI/ORD660/Reports/ORD660_Ba
.rpt dEmailAddress.rpt
ORD660_Confirmation.rpt /TRS/Source/TRS_CrystalXI/ORD660/DBScripts/92a/ORD6
60_Confirmation.rpt
ORD660_notify.rpt /TRS/Source/TRS_CrystalXI/ORD660/Reports/ORD660_noti
fy.rpt
PGR100_EXCEPTION.rpt /TRS/Source/TRS_CrystalXI/PGR100/Reports/PGR100_EX
CEPTION.rpt
PGR100_PROCESSED.rpt /TRS/Source/TRS_CrystalXI/PGR100/Reports/PGR100_PR
OCESSED.rpt
PGR100_PROCESSED_SU /TRS/Source/TRS_CrystalXI/PGR100/Reports/PGR100_PR
MMARY.rpt OCESSED_SUMMARY.rpt
Universe Changes
The following universe was modified in this release:
 Customers.unv
Web Changes
The following web files were added or modified in this release:
Web Library Changes
File Location
SSOAuthentication. /Library/Components/Personify.SSOAuthentication/SSOAuthenticati
vb on.vb

85
7.7.0 RELEASE NOTES
Web Part Changes
File Location
Login.ascx.vb /WebParts/Login/Login.ascx.vb
SubmissionEntryContent. /WebParts/Abstract/Abstract/Screens/Author/SubmissionEntry
ascx.vb Content.ascx.vb

86

Personify360 7.7.0 Release Notes

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Personify360 7.7.0 Release Notes

Caricato da

Copyright:

Formati disponibili

Personify360 Release Notes

Resolved Issues .................................................................... 16

PROPRIETARY AND CONFIDENTIAL

Upgrading to 7.7.0 ................................................................. 33

Technical Changes ................................................................ 66

PROPRIETARY AND CONFIDENTIAL

National Change of Address

National Change of Address (NCOA) is a secure dataset of approximately 160 million

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

Payment Schedules Online

PROPRIETARY AND CONFIDENTIAL

Pricing By World Bank Region

PROPRIETARY AND CONFIDENTIAL

Populate Purchasing Groups

PROPRIETARY AND CONFIDENTIAL

Membership Join/Renew Enhancements

PROPRIETARY AND CONFIDENTIAL

ZIP100 & ORD650 Enhancements

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

Launch Screen Redesigns

PROPRIETARY AND CONFIDENTIAL

Customer-Facing Report Redesigns

PROPRIETARY AND CONFIDENTIAL

eBusiness Configuration File

PROPRIETARY AND CONFIDENTIAL

Architecture and Third-Party Support Upgrades

PBBI/Spectrum 12.2 Upgrade

Spectrum™ Technology Platform is a system that improves the completeness, validity,

As of Personify360 version 7.7.0, Thycotic DLL has been removed.

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

Credit Card Processing

PROPRIETARY AND CONFIDENTIAL

 When the user attempted to add contact information on a customer record in

PROPRIETARY AND CONFIDENTIAL

Digital Content Delivery

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

 When a membership order had a digital subscription as a member benefit, the

PROPRIETARY AND CONFIDENTIAL

 When the user attempted to give access to the

PROPRIETARY AND CONFIDENTIAL

PROPRIETARY AND CONFIDENTIAL

 Database servers – Windows Server 20012 R2 Standard or above and SQL

Before You Begin

Before you begin the upgrade, please perform the following:

PROPRIETARY AND CONFIDENTIAL

You must log on as "Administrator" or a similar privilege to perform the upgrade.

The upgrade process should be performed locally.

Upgrading from 7.6.2

PROPRIETARY AND CONFIDENTIAL

1. Restore the backup of the Personify360 database.

PROPRIETARY AND CONFIDENTIAL