Hello,

It is my understanding that both the Extraction and Transformation skills are agnostic of what the Ticket is classified as.  Both Returns and Sales have a product number and order number; both returns and sales have an Address that needs to be transformed.  So why is Classification presented first in the Deterministic example?  I also don’t understand why the “if classification=returns” is so high up the chain.  Together these feel inefficient and force the developer to drag/drop/map the same API Tasks calls twice in the Process.  Couldn’t it instead be as simple as this?

1. Extraction
2. Transformation
3. Classification
4. Content Generation
5. If classification=return, then CreateReturn, else if classification=sales, then CreateSales
6. Approval
7. If approved, send email, else allow for edit and then send email

Obviously this still doesn’t allow for repeated or extra steps like APA, but it just felt like the example given was more complicated than it needed to be.

Thanks.