- open the Global Process app in Composer - use the Find operation and search for " Event " - in the result list right click on "Event without reply" and click on "Go to Reference Location"
When running an orchestration workflow you may see the following errors in the Event Viewer or the user workspace for all instances of the workflow or just random ones. Error occurred in file:
To work around this issue, uncheck the "Lock definition" checkbox on the Event without Reply event definition in Composer and deploy the process app again. This will cause the event to be sent successfully from the transition.
Workaround: In Composer, under Orchestrations Links > Event without Reply , one of these fields are causing the problem. The problem does not occur if a Multi-types field is not the first element in the event definition extension structure.
Steps To Reproduce Configure ALF environment Build Revised Baseline Expected Result Build Baseline submitted/completed ALF events should be fired Actual Result There are no Build Baseline submitted/completed ALF events Additional Info This is because code doesn't handle "In Response To(revised)" (and "Affected(revised)") Request relationship type.
There are no Build Baseline submitted/completed ALF events Additional Info This is because code doesn't handle "In Response To(revised)" (and "Affected(revised)") Request relationship type.