diff --git a/spring-boot/README.md b/spring-boot/README.md
index 8034c52..c05870e 100644
--- a/spring-boot/README.md
+++ b/spring-boot/README.md
@@ -12,6 +12,7 @@ This adapter is aware of all the details needed to keep in mind on using Camunda
     1. [Worker ID](#worker-id)
     1. [Module aware deployment](#module-aware-deployment)
     1. [SPI Binding validation](#spi-binding-validation)
+1. [Call-Activity](#call-activity)
 1. [Multi-instance](#multi-instance)
 1. [Message correlation IDs](#message-correlation-ids)
 1. [Transaction behavior](#transaction-behavior)
@@ -93,6 +94,15 @@ On starting the application BPMNs of all workflow modules will be wired to the S
    
 This ensures that correct wiring of all process definitions according to the SPI is done.
 
+## Call-activity
+
+The adapter uses Camunda 7's business key to associate the workflow aggregate
+to the process instance. Therefor, on defining a call-activity in Camunda Modeler
+it is mandatory in the property panel to tick the checkbox
+`Business Key` and keep the default `Business key expression`:
+
+![Business Key for call-activity](./readme/call-activity_business-key.png)
+
 ## Multi-instance
 
 For Camunda 7 all the handling of multi-instance is done under the hood.
diff --git a/spring-boot/readme/call-activity_business-key.png b/spring-boot/readme/call-activity_business-key.png
new file mode 100644
index 0000000..333f85c
Binary files /dev/null and b/spring-boot/readme/call-activity_business-key.png differ