For these specific areas and situations, we need humans participating in the processing of composite application instances. And just like all other service engines, for the sake of the SCA engine, humans in a composite should come with a WSDL interface and communication specified in XSD too. And that is what the SOA Suite’s Human Task Service provides: the interface between the services world of the composite application and the people performing activities in the context of the application.
Human tasks typically implement stand-alone tasks around a set of data—potentially with complex escalation, voting, and routing logic. In this chapter, we will focus on defining individual human tasks.We will look at relatively simple decision tasks, at tasks that have custom user interfaces that support manipulation of task payload data, at tasks that can be dealt with by sending an email and at tasks with a complex workflow.
Sections in this chapter:
- Simple Task Seeking Human Approval for Aircraft Service Proposal
- Custom Task UI to Handcraft Proposal when rejecting the generated proposal
- Complex Workflow in Human Task
These figures illustrate the components to be developed in this chapter.
Sources for this chapter can be found on Github: Chapter 17 sources.
Blog article about configuring GMail account for Outbound Email in SOA Suite 12c:http://technology.amis.nl/2014/08/05/setup-gmail-as-mail-provider-for-soa-suite-12c-configure-smtp-certificate-in-trust-store/
Blog article about configuring GMail account for Inbound Email in SOA Suite 12c: http://technology.amis.nl/2014/08/17/soa-suite-12c-configuring-gmail-as-the-inbound-email-provider-for-ums-imap-ssl/
Blog article about configuring actionable email for human tasks in SOA Suite 12c: http://technology.amis.nl/2014/10/17/soa-suite-12c-actionable-emails-with-human-task-service/
Blog article on how to create a user hierarchy in the Embedded LDAP Server in WebLogic (using JXPlorer)