Updated release notes with limitation related to cps path

Issue-ID: CPS-1179
Signed-off-by: puthuparambil.aditya <aditya.puthuparambil@bell.ca>
Change-Id: I9fa7799e5a54b82b280606a14d09ce2256b844f2

1 files changed, 2 insertions, 0 deletions

diff --git a/docs/cps-path.rst b/docs/cps-path.rst
index 44662d893c..f321adfa99 100644
--- a/docs/cps-path.rst
+++ b/docs/cps-path.rst
@@ -241,6 +241,7 @@ leaf-conditions
   - The key should be supplied with correct data type for it to be queried from DB. In the last example above the attribute code is of type
     Integer so the cps query will not work if the value is passed as string.
     eg: ``//categories[@code="1"]`` or ``//categories[@code='1']`` will not work because the key attribute code is treated a string.
+  - Having '[' token in any index in any list will have a negative impact on this function.
 
 **Notes**
   - For performance reasons it does not make sense to query using key leaf as attribute. If the key value is known it is better to execute a get request with the complete xpath.
@@ -265,6 +266,7 @@ The text()-condition  can be added to any CPS path query.
   - Only string and integer values are supported, boolean and float values are not supported.
   - Since CPS cannot return individual leaves it will always return the container with all its leaves. Ancestor-axis can be used to specify a parent higher up the tree.
   - When querying a leaf value (instead of leaf-list) it is better, more performant to use a text value condition use @<leaf-name> as described above.
+  - Having '[' token in any index in any list will have a negative impact on this function.
 
 ancestor-axis
 -------------