is there a solution to this problem?
When creating a rule in the config API application and choosing the start event, a user-defined event or a generic event gets stuck here and we can’t proceed.
This is a known limitation of the Config API Client sample.
The extra information needed, is found in the “Introduction to Configuration API” → “Rules configuration” → “External Events sources” - For External Events; you must use the ItemType “External” with the special GUID string “e8bd6cee-1119-4296-ba91-e3803e2c591e” i.e., “External[e8bd6cee-1119-4296-ba91-e3803e2c591e]”.
This special handling is not used of the Config API Sample which to a large extend is a tool for general handling but lacks some special handling. I will update the sample description special note as it wasn’t mentioned.
