Multiple Community Hubs - Winter '18

PilotPilot — New feature available to a limited set of customers who are closely monitored. Potential Pilot customers are identified early in the process. The purpose of a pilot feature is to gather feedback and data on product functionality, scalability, performance, and usability, which influences the direction, continued development, or roll out of the feature.

Multiple Community Hubs is the latest advancement to the Nimble AMS Community Hub experience. This new functionality provides administrators the necessary building blocks to manage the setup and maintenance of additional Community Hubs. As before, the primary association can fully manage their ecommerce needs in their existing Community Hub. Now, any additional entities or affiliated associations, also managed in Nimble AMS, can have their own entity based Community Hub. Administrators have the tools to define each Community Hub's look and feel as well as the unique Community Hub experience for that entity or association.

What's New?

  • Administrators can now create Community Hub components, like menu items, pages, cards, and buttons, for each Community Hub. Learn more.
  • The Entity on constituent's cart is now updated with the entity of the Community Hub they are using. This ensures all transactions are made to the correct entity.
  • The value in Identifier on existing Community Hub carts has been updated so they display in the proper Community Hub(s).
  • URL fields have been replaced and improved so you can set up and use Community Hub event registration, downloadable merchandise, donations, and express payment for each entity.

      Learn More...
    • Community Hub URL on the Entity object has been removed from the Community Hub package has been replaced by Community Hub URL in the Nimble AMS package.
      • Community Hub Event URL on the Event has been updated to use the new Community Hub URL field when sharing the Community Hub event registration URL.
    • Download Proxy Page in Nimble AMS configuration has been replaced by Download Proxy Page on the Entity object.
      • Download Proxy Page now only needs to be populated with the relative page path, rather than the full URL, and does not need to be updated when Community Hub URL changes.
      • Download URLon the Order Item Line object has been improved to use the new Download Proxy Page field in conjunction with the new Checkout Page field when using downloadable merchandise.
    • Checkout Page in Nimble AMS configuration has been replaced by Checkout Page on the Entity object.
      • Checkout Page now only needs to be populated with the relative page path, rather than the full URL, and does not need to be updated when Community Hub URL changes.
      • Checkout URL on the Product and Appeal objects has been improved to use the new Community Hub URL field in conjunction with the new Checkout Page field when using Community Hub donations.
    • So the change is no trouble for you, the new fields have been populated on all your entities with the values of the fields they replace.
  • Data sources included in Community Hub have been updated to retrieve data for the Community Hub in which they are used.

      Learn More...

    For example: if you have a Community Hub for your association entity, with no entity crossovers, only products and events for the association entity are returned by data sources.

    If you have a Community Hub for your association entity, with entity crossovers set up you your foundation entityproducts and events for the association entity and foundation entity are returned by data sources.

  • Community Hub menu items have been updated so you can display and order menus differently in each Community Hub.
  • Community Hub themes have been updated so you can create a custom theme for each Community Hub.
  • Community Hub customization settings have been updated so you can customize each Community Hub differently.
  • Stored payment methods have been improved so constituents can view and pay with only valid stored payment methods in Community Hub. Learn more.

How Do I Enable It?

  • Prerequisite: this feature uses Custom Metadata types, which NimbleUser Support can enable in your org.
  • Contact your NimbleUser customer success manager to find out how you can enroll in this pilot feature.

Things to Keep In Mind

  • Because individuals and companies each have a single account in Nimble AMS, their profile photo and company logo displays throughout all Community Hubs.
  • When creating new data sources, you will need to filter for the appropriate entity(s) of the Community Hub. For data sources based on a query record, include Id = {!CurrentEntityId} in the WHERE to return only records for the entity(s) of the Community Hub. Contact support for assistance updating Apex based data sources.
  • When cloning an existing Community Hub, you will need to update any custom data sources to filter for the appropriate entity(s) of the Community Hub.
  • Payment URL (Order) and Payment URL (Cart) on the Entity—used for express payments—must be populated with a full URL, as opposed to a relative page path, and must be updated when Community Hub URL changes.

On This Page

In This Section