diff --git a/jcore-gnormplus-ae/README.md b/jcore-gnormplus-ae/README.md
index 7e875217..48b548e1 100644
--- a/jcore-gnormplus-ae/README.md
+++ b/jcore-gnormplus-ae/README.md
@@ -11,10 +11,14 @@ Wrapper for the JULIE Lab variant of the GNormPlus gene ID mapper.
 
 **1. Parameters**
 
+Note that these are not all parameters but just those that are the least self-explanatory.
+
 | Parameter Name | Parameter Type | Mandatory | Multivalued | Description |
 |----------------|----------------|-----------|-------------|-------------|
-| param1 | UIMA-Type | Boolean | Boolean | Description |
-| param2 | UIMA-Type | Boolean | Boolean | Description |
+| SkipUnchangedDocuments | Boolean | false | false | Whether GNormPlus should run on documents that exist in the database and have unchanged text contents. |
+| AddToVisitKeys | Boolean | false | false | Whether to add the value of the `ToVisitKeys` parameter to the CAS. See description of `ToVisitKeys` for more details. |
+| AddUnchangedDocumentTextFlag | Boolean | false | false | Whether to set a flag in the CAS that stores the information if the document text has changed in comparison to a potentially existing document in the database with the same document ID. Used by downstream components like the XMI DB Writer to manage actions depending on (un)changed text contents. |
+| ToVisitKeys | String[] | false | true | The UIMA-aggregate-keys of the pipeline components that should still be visited if the document text is unchanged in comparison to a potentially existing document in the database with the same ID. In CoStoSys pipelines we want to run the DB Checkpoint AE in any way, unchanged document text or not, because we want to keep track of all documents if they have already been processed by the pipeline. |
 
 **2. Predefined Settings**
 
diff --git a/jcore-gnormplus-ae/pom.xml b/jcore-gnormplus-ae/pom.xml
index e503c046..162af331 100644
--- a/jcore-gnormplus-ae/pom.xml
+++ b/jcore-gnormplus-ae/pom.xml
@@ -13,7 +13,7 @@
         <version>2.6.1</version>
     </parent>
     
-    <version>2.6.8</version>
+    <version>2.6.9</version>
 
     <dependencies>
         <dependency>
@@ -34,17 +34,17 @@
         <dependency>
             <groupId>de.julielab</groupId>
             <artifactId>jcore-xmi-db-reader</artifactId>
-            <version>2.6.2</version>
+            <version>[2.6.2,2.7)</version>
         </dependency>
         <dependency>
             <groupId>de.julielab</groupId>
             <artifactId>jcore-xml-db-reader</artifactId>
-            <version>2.6.2</version>
+            <version>[2.6.2,2.7)</version>
         </dependency>
         <dependency>
             <groupId>de.julielab</groupId>
             <artifactId>jcore-pmc-db-reader</artifactId>
-            <version>2.6.2</version>
+            <version>[2.6.2,2.7)</version>
         </dependency>
         <dependency>
             <groupId>ch.qos.logback</groupId>
diff --git a/jcore-gnormplus-ae/src/main/resources/de/julielab/jcore/multiplier/gnp/desc/jcore-gnormplus-xml-db-multiplier.xml b/jcore-gnormplus-ae/src/main/resources/de/julielab/jcore/multiplier/gnp/desc/jcore-gnormplus-xml-db-multiplier.xml
index 988f409b..46c3e13a 100644
--- a/jcore-gnormplus-ae/src/main/resources/de/julielab/jcore/multiplier/gnp/desc/jcore-gnormplus-xml-db-multiplier.xml
+++ b/jcore-gnormplus-ae/src/main/resources/de/julielab/jcore/multiplier/gnp/desc/jcore-gnormplus-xml-db-multiplier.xml
@@ -95,7 +95,7 @@
             </configurationParameter>
             <configurationParameter>
                 <name>ToVisitKeys</name>
-                <description>For use with AnnotationDefinedFlowController. Specifies the delegate AE keys of the AEs this CAS should still applied on although the hash has not changed. Can be null or empty indicating that no component should be applied to the CAS. The task of the AnnotationDefinedFlowController is then to read those annotations and route the CAS accordingly.</description>
+                <description>For use with AnnotationDefinedFlowController. Specifies the delegate AE keys of the AEs this CAS should still applied on although the hash has not changed. Can be null or empty indicating that no component should be applied to the CAS. The task of the AnnotationDefinedFlowController is then to read those annotations and route the CAS accordingly. The parameter values will only be added to the CAS if AddToVisitKeys is set to true, the document text hash is available in the database (see the AddShaHash parameter) and the hash in the database equals to the hash of the current document in the pipeline.</description>
                 <type>String</type>
                 <multiValued>true</multiValued>
                 <mandatory>false</mandatory>