Flow Engine Context Error

Neil Paterson
Tera Contributor

Since upgrading to Washington patch 6 we've noticed a flow engine context error whenever a new catalog request is made via EC.  The REQ, RITM and SCTASK records are generated correctly but the an error appears in the flow engine contexts table and system log.

The calling source is CRUD_TRIGGER and the error message begins "attempting to use undefined input = 'permission_type' from <sysid>

com.snc.process_flow.exception.ProcessAutomationException: attempting to use undefined input = 'permission_type' from <sysid>...".

 

The error is happening on all request types regardless of whether they call subflows or not.

Does anyone know what might be causing the error?

0 REPLIES 0