2017-10-18_19-06-07_Fixes and Improvements - Summer '17

To empower our customers, we offer the opportunity to be involved in the Preview Channel.  This gives our customers, implementations, and partners the opportunity to put new features through their paces and provide feedback before they are generally available.  We are excited to share the Summer '17 Preview version of Nimble AMS with our users.  There are many features and improvements you have been asking for that we are excited to roll out and get feedback on.For a deeper dive into the new features, check out Delivered!.  Here are the highlights! 

Fixes and Improvements

Event Question Status and Community Hub Enablement Event questions have been improved with new fields staff can use to control:

  • Whether a question should display in Community Hub, or just Staff View.
  • Whether the question should be active to be filled out in the registration process in Community Hub or Staff View or inactive if it is no longer needed. If you make an event question inactive, any answers to that questions are still available within the event for your analytics.
  Learn more...

Here are the improvements:

  • The StatusStatus Flag, and Self Service Enabled fields have been added to the Event Question object.
  • The Add Registration Page in Staff View has been updated to only display event questions where Status is blank or Active.
  • The Event Questions card on the Customize the Experience Page has been improved to only display event questions where Status is blank or Active and Self Service Enabled is selected.
  • The EditEventQuestionAnswers Data Source has been updated to supply the event questions where Status is blank or Active and Self Service Enabled is selected along with their related event answers to the Event Questions card.

To take advantage of this improvement, we recommend you add these new fields in the following places and make the following changes:

  • On the Event Question object, on the Question Layout page layout:
    • Add the StatusStatus Flag, and Self Service Enabled fields
    • Update the mini page layout
  • On the Product object:
    • On the Registration page layout, update the Event Questions related list
    • Update the Search Layouts:
      • Search Results
      • Lookup Dialog
      • Lookup Phone Dialog
      • Events Tab
    • Update the All Event Questions list view
    • Consider creating new list views:
      • All Event Questions - Active
      • All Event Questions - Inactive
      • Community Hub Enabled - Event Questions
  • On the Event object, on the Event Layout page layout, update the Event Questions related list

For all new events, be sure to set Status for questions to be displayed in Community Hub and Self Service Enabled to active for all questions that should be display in Community Hub and Staff View for all event questions.

Take a look at the Event Session Questions in Community Hub improvement below for even more control over event questions.

Appeal Status and Tracking Appeals have been improved with new fields so staff can control whether an appeal is displayed in the order process.

Additional fields have been added to help staff include a description of the appeal, a beginning and end date of the appeal, and what type of appeal it is—like email or membership—in your analytics.

  Learn more...

Here are the improvements:

  • The StatusStatus FlagDescriptionStart DateEnd Date, and Type fields and have been added to the Appeal object.
  • The Donate Now Page in Community Hub has been updated so only orders submitted with an active appeal link the appeal record to the donation record. Donations made toward an inactive appeal are not linked.
  • The Add Donation Page and Add Membership Page in Staff View have been updated to only display appeals for donations where the appeal Status is Active.

To take advantage of this improvement, we recommend you add these new fields in the following places and make the following changes:

  • On the Appeal object:
    • On the Appeal Layout page layout:
      • Add the StatusStatus FlagDescriptionStart DateEnd Date, and Type fields
      • Update the mini page layout
      • Remove the DeleteChange OwnerChange Record Type, and Sharing buttons
      • Add a System Information section at the bottom of the page layout which includes Created ByLast Modified By, and Owner
    • Update the Search Layouts:
      • Search Results
      • Lookup Dialog
      • Lookup Phone Dialog
      • Events Tab
    • Update the All list view—also, rename to All Appeals

    • Consider creating new list views:

      • All Appeals - Active
      • All Appeals - Inactive

For any existing and still active appeals, be sure to set Status to Active and feel free to populate DescriptionStart DateEnd Date, and Type to suit your needs.

Support for Mastercard 2-Series Staff View and Community Hub have been updated to support 2-series Bank Identification Numbers (BINs). Learn more (external).

Architectural Improvements

Transition to Custom Metadata Types With Summer '17 Community Hub Setup is transitioning from Custom Settings to Custom Metadata Types 

  Learn More...

Custom Metadata Types (CMTs) are another way to define customizations and configuration of Community Hub. Today, Nimble AMS uses Custom Settings to define Community Hub. With Summer '17, we are transitioning to Custom Metadata Types. To learn more about CMTs, check out this article from Salesforce: Custom Metadata Types (external).

Here are the benefits:

  • Custom Metadata Types better support future Community Hub improvements
  • They can be moved between orgs via changeset
  • They provide better stability for our seasonal upgrades
  • Nimble AMS is now better aligned with Salesforce's recommended best practices

Here is what you need to do:

  • To take advantage of Summer '17 features and all future features, that are built using CMTs, you will need to transition from Custom Settings to Custom Metadata Types
  • Simply open a case with support and we will enable CMTs, transition your existing custom settings to CMTs, and test to ensure your existing customizations continue to work as expected

Add Additional Items The Order API (specifically the OrderProcessor) has been updated to allow for editing of Orders and adding additional items/lines to pre-existing orders. (AMS-8506) 

Cancel! The Order/OrderItem/OrderLine classes now have a cancel() method that cancels the corresponding record. (AMS-8520)

Add Value to Field The Payment.addValueToField method has been globalized in order to be able to use it to add additional values to fields in Payment__c records. (AMS-8453)

Specify the Batch Id Consumers of the Order API now have the ability to optionally specify the Id of a batch to process payment transactions in during order payment submission. (AMS-8472)

Community Hub Improvements

Event Session Questions in Community Hub The Community Hub registration process has been improved to display not only questions related to the event but also those questions related to specific event sessions.

  Learn more...

Here are the improvements:

To take advantage of this improvement, we recommend you add these new fields in the following places and make the following changes:

  • On the Event Question object, on the Question Layout page layout:
    • Add the Session field
    • Update the mini page layout
  • On the Product object:
    • On the Registration page layout, update the Event Questions related list
    • Update the Search Layouts:
      • Search Results
      • Lookup Dialog
      • Lookup Phone Dialog
      • Events Tab
    • Update the All Event Questions list view
    • Consider creating new list views:
      • All Event Session Questions
  • On the Event object, on the Event Layout page layout, update the Event Questions related list
  • When you Create an Event Question, enter the specific Session to which the event questions relates and be sure to select Self Service Enabled to display the question in the Community Hub registration process.

Take a look at the Event Question Status and Community Hub Enablement improvement above for even more control over event questions.

Photo Card Type There is a new card type called Photo Card Type that can be used for uploading photos and other types of files. Learn More

Terms and Conditions Card Type There is a new card type called Terms and Conditions Card type that allow admins to specify terms and conditions and can be customized to require constituents to check a box or acknowledge the terms. Learn More

Where's the button? On the Add Individual page, when the Add Individual button is not displayed due to the user's email not being part of the valid email domains, a message is now displayed to indicate why the affiliation can't be created. (NC-3955)

Button Menu Items Button Menu configuration can now be accomplished in Community Hub Setup. (NC-3452) Learn More

Query Limit for Dupe Checking A query limit has been added to dupe checking to prevent list size errors and CPU timeout errors. During dupe checking, only the first 1,000 records will be displayed. (NC-3831)

Donate with Stored Payment The Donations page now supports paying through a stored payment method for logged in users. (NC-3722) Learn More

Cookie Message Service Made Global TrafficService has been created and contains global methods to transfer information between pages. (NC-3747) 

Form Validation A new ButtonRow2 Card has been created! This allows developers to make use of HTML5 client side validation in their forms rather than relying solely on server side validation. (NC-3832)  Learn More

Credit Card Payment Component Methods in the CreditCardPaymentComponentController where globalized to allow for customizations to decide when the card should render. (NC-3927) 

Don't create it anyway Additional validation has been added prevent a scenario where CH can get stuck between creating an account and a user. Now, additional password validation is done before fully committing the account. (NC-3928) 

On This Page

In This Section

Error rendering macro 'sv-pagetree' : com.atlassian.renderer.v2.macro.MacroException: Could not find page for specified rootPage: 2017-10-18_19-06-09_Release Information - Summer '17