adding error codes for ABAC metadata function

modules/ROOT/content-nav.adoc

@@ -280,6 +280,9 @@
 **** xref:errors/gql-errors/42N09.adoc[]
 **** xref:errors/gql-errors/42N0A.adoc[]
 **** xref:errors/gql-errors/42N0B.adoc[]
+**** xref:errors/gql-errors/42N0D.adoc[]
+**** xref:errors/gql-errors/42N0E.adoc[]
+**** xref:errors/gql-errors/42N0F.adoc[]
 **** xref:errors/gql-errors/42N10.adoc[]
 **** xref:errors/gql-errors/42N11.adoc[]
 **** xref:errors/gql-errors/42N12.adoc[]

modules/ROOT/pages/errors/gql-errors/42N0D.adoc

@@ -0,0 +1,22 @@
+= 42N0D
+
+
+== Status description
+
+error: syntax error or access rule violation - cannot call function from this context. The function `{ <<fun>> }` cannot be called from the current context. It can only be used `{ <<context>> }`.
+
+== Explanation
+This error is thrown when a function is called from a context that is not allowed for that function.
+
+== Example scenario
+
+Try to call an internal security function like `abac.oidc.user_attribute()` from a regular Cypher query.
+You will get this error because it is not supported in user Cypher queries and can only be called from within `AUTH RULE` creation or alteration commands.
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/42N0E.adoc

@@ -0,0 +1,19 @@
+= 42N0E
+
+
+== Status description
+
+error: syntax error or access rule violation - cannot call function without metadata. The function  `{ <<fun>> }` cannot be called without metadata.
+
+== Explanation
+This error occurs when the metadata required by the function is missing from the context supplied. This is an internal error which would only ever appear in the logs.
+
+== Example scenario
+A function is called without the required metadata.
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/42N0F.adoc

@@ -0,0 +1,19 @@
+= 42N0F
+
+
+== Status description
+
+error: syntax error or access rule violation - cannot call function without metadata for realm. The function  `{ <<fun>> }` cannot be called without metadata for realm: `{ <<auth>> }`.
+
+== Explanation
+This error occurs when the metadata for a specific security realm is missing from the context supplied. This is an internal error which would only ever appear in the logs.
+
+== Example scenario
+A function is called with a metadata dictionary, but there is no entry for the required realm.
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/index.adoc

@@ -1133,6 +1133,18 @@ Status description:: error: syntax error or access rule violation - invalid shar
 
 Status description:: error: syntax error or access rule violation - cannot replace sharded database. The database identified by `{ <<db>>1 }` is sharded. Drop the database `{ <<db>>2 }` before recreating.
 
+=== xref:errors/gql-errors/42N0D.adoc[42N0D]
+
+Status description:: error: syntax error or access rule violation - cannot call function from this context. The function `{ <<fun>> }` cannot be called from the current context. It can only be used `{ <<context>> }`.
+
+=== xref:errors/gql-errors/42N0E.adoc[42N0E]
+
+Status description:: error: syntax error or access rule violation - cannot call function without metadata. The function  `{ <<fun>> }` cannot be called without metadata.
+
+=== xref:errors/gql-errors/42N0F.adoc[42N0F]
+
+Status description:: error: syntax error or access rule violation - cannot call function without metadata for realm. The function  `{ <<fun>> }` cannot be called without metadata for realm: `{ <<auth>> }`.
+
 === xref:errors/gql-errors/42N10.adoc[42N10]
 
 Status description:: error: syntax error or access rule violation - no such role. A role with the name `{ <<role>> }` was not found. Verify that the spelling is correct.