Perhaps this story should be titled "BDD definitions for agile service stories"...
For our .NET-based stories (always vertical slices) we use definitions matching the well known BDD format.
Sometimes the story involves work explicitly in a dependent system (here this is SAP). When this happens it does not touch the user interface at all and often doesn't involve .NET in any way.
So far we have not been able to define these stories in BDD (gherkin format) and this makes it difficult for the stories to be broadly understood.
While many stories will have a technical detail section fleshed out with items referred to by the scenarios, how should a story which is essentially only technical bullet points be defined? Is there a gherkin syntax for defining service behaviour?