Team - I’m genuinely perplexed by the unconnected threads of new developer functionality and see the landscape a respresenting a huge missed opportunity for consolidation.
I’ve almost stumbled over new developer ‘Action’ developer functionality while working on Customer Agent setup - and it seems that there is a lot of parallel thoughts in play that have not quite cohered into a complete picture for us on the outside. For example (this is my scanning of the documentation:
- Custom Workflow Actions very nearly make a very sophisticated enhancment to Custom Code Workflow steps - an enhancement that would enable us developers to store code and maintain on the server side and prevent duplication of the same code fragment within worflows or across workflows. All you need is to be able to do is add a ‘code’ section in the Action definition!
- Agent Tools are so close to Custom Workflow steps that you can hardly see the light between the definitions. Why not define and support them in the same way?
- Customer Agent Action defintions are almost exactly what’s described in Agent Tools - but have a completely different implementation model. Whay can’t they be one and the same thing?
I’m hoping that others in a similar position to me can see some of the weirdness in all this and can help pull the threads together.
Steve