What it does
The rejection branch checks only two of the four security questions. Bedrock models handle the agent and report summary; missing lookup workers and untested gates make this an example, not a security guarantee.
Integrations
Camunda + Jev Integration Examples
Add Jev questions to a Camunda customer-service workflow, with examples for screening requests, assessing customers and reviewing an agent's work.
Bookmark: Camunda + Jev Integration Examples
Keep this in your collection.
Leave a noteWhat would you try with this?
: Camunda + Jev Integration Examples
Only you can see your notes.
Screenshot unavailable. Open the experiment ↗
How you can use it
Ask a developer to begin with the supplied process diagram and connection settings. They show where AI questions could join your customer-service process. A working version needs the Camunda workflow system, service access keys and code to retrieve customer records. That record-retrieval code is not supplied here.
Keep access rules outside the model. This example rejects some requests marked as attempts to manipulate the assistant, but leaves other requested checks out of that decision. Customer and tool information goes to TypeSafe, an outside AI service. Separate Bedrock models write the replies and summaries. Test the branches yourself.