Hello Colin
We had the same issue. If you want to use a router:
- You have to set the Response From property on the router with name of the operation.
- Make sure to set Forward Generated Response To Target(s) to true
- The Response timeout. Do not set the Respone timeout on -1 because the system could hang if you have an error on the router.
- Make sure that all the reply action codes (router and operation) are set in a way the system does not retry.
This way you can also use a router.
Kind regards
Benny Verhamme
Hello Julian
Thanks for your clear answer, I will discuss your answer with my team. The proposal to filter in advance on trigger event in the main router is very interesting and is a good middle way. It's a way to keep the complexity in the systemrouter, but to do an easy filter in the main router. And it is still very maintainable.
Kind regards
Benny Verhamme
I have a few questions.
- We have created some custom services and operations with extra settings. These settings are not visible anymore. Is this going to be implemented? Or do we need to do something extra?
- I have also overwritten a property of operation with another description. Our description is not showing, it shows the description of the class we extended from? Also here what am I missing?
- Another thing, is this still using Zen pages? At first sight and don't think so?
- Is there maybe a tutorial on creating your own custom selector for settings on a operation or service? Because I have created a custom selector in a zen page dialog. But if zen is no longer supported guess I have to rebuild this.
- It is not very clear how everything is implemented and how we can customize things as we like.