KONTAKTE | Installation Requirements
Installation Prerequisites for Kaleido KONTAKTE NPC
This document outlines the requirements for installing the Kaleido KONTAKTE NPC managed package in a Salesforce org.
Salesforce Edition
Enterprise Edition or higher recommended
Developer Edition supported for testing/development
Nonprofit Cloud
Nonprofit Cloud is a comprehensive product built on the core platform that allows nonprofits to fund, deliver, and measure impact with one integrated platform. (Source)
This is included:
Full Sales & Services Cloud
Program & Case Management
Fundraising
Accounting Subledger Growth
Outcome Management
Nonprofit Toolkit
Pre Installation
Required Org Features
The target org must have the following features enabled before installation:
Platform Features
Feature | Notes | Dev Scratch Org | Production Org / Sandbox Org |
|---|---|---|---|
Person Accounts | Critical – Cannot be disabled once enabled. Plan ahead. Go to Setup / Feature Settings
| - | |
Contacts to Multiple Accounts | Allows contacts to be related to multiple accounts. Go to Setup / Sales /Account Settings and enable the checkbox | - | |
State and Country Picklists | Standardised address picklists. Go to Setup / Data / State and Country / Territory Picklists. These steps have to be completed before you can enable the feature:
Follow this instruction for the configuration: | Enabled, but not configured. Follow the configuration instructions if you need the values. | |
Fundraising | Enable Fundraising. Go to Setup / Feature Settings / Fundraising / Fundraising Settings Turn On Leave further settings as they are for the moment. | - | |
Interest Tags | Enable Interest Tags. Go to Setup / Feature Settings / Financial Services / Guided Setup Interest Tags
| - | |
Translation Workbench | Required for multi-language deployments. Go to Setup / User Interface / Translation Workbench / Translation Languge Settings Click “Edit” and activate German (mandatory) and other languages if needed. | - |
Optional Features
The following features may be required depending on your implementation:
Feature | Notes |
|---|---|
OmniStudio Designer | Required if customising FlexCards, OmniScripts, or DataRaptors |
OmniStudio Runtime | Required if running OmniStudio components |
Package Installation
Install the following packages in order:
Kaleido.Common – Base package (must be installed first) https://github.com/ANT-Informatik/Kaleido.Common/releases/latest
Kaleido.Kontakte NPC - Main package https://github.com/ANT-Informatik/Kaleido.Kontakte.NPC/releases/latest
Post Installation
Step | Dev Scratch Org | QA Scratch Org | Production Org |
|---|---|---|---|
Add values for Salutation Field in PersonAccount Record Type
| |||
Add List View Filter for “Alle aktiven Personenaccounts”
| - | ||
Deploy unpackaged Metadata Unpackaged Metadata is metadata that cannot be a part of the Kontakte package and needs to be deployed manually. It consists mainly of changes to Standard Objects and Standard Picklists. Please check the metadata beforehand to ensure it is relevant to the project. Installation Guidelines (via CumulusCI):
Post deployment steps are now grouped in a flow | - | - | |
Import default configuration of the Label Service The default configuration of the Label Service will populate the following Account fields:
You can also start from scratch and not import anything. However, it is recommended that you use the default configuration as a starting point at least.
| - | - | |
Assign Permission Sets Assign the following Permission Sets to the appropriate Users:
| - | - |
References
Nonprofit Partner Pocket Guide
Industry Demo Orgs (Search for “Nonprofit”)
@Wolfgang Trog
This page is called “KONTAKTE | Installation Requirements”, but you added pre-install steps, installation instructions and the post installation steps.
This was probably copied from https://gutesbessertun.atlassian.net/wiki/spaces/KALEIDO/pages/1296007169 (I guess).
Multiple things are not correct or missing in the current page. One of the most important things: there is no mention in here that the packages should be installed for admins only. Or else anyone has access to anything.
We now also have duplicated documentation (again), which is something we wanted to prevent. I don’t know which documentation is correct or the most up to date and people will make edits to both versions independently, which will increase the chaos even more.
Can we please consolidate this, so we only have one page with installation instructions as the single source of truth? This is also helpful for the project team.