Dashboard > Tempo > ... > FAQ > Designer > View
Tempo Log In   View a printable version of the current page.
Designer
Added by Nicolas Modrzyk, last edited by Nicolas Modrzyk on Sep 11, 2008

Deploy AbsenceRequest without Intalio|Designer

A workflow process mostly needs two set of deployment.

  • Deploy process on Ode: deploy a BPEL process on Ode, by just copying the process files in the Ode deployment folder.
  • Deploy forms and pipa on Tempo: deploys the workflow forms, and the workflow PIPA tasks on tempo, by copying the files in tempo deployment folder.

Most of it has been described in previous FAQs, let's just review the PIPA descriptor:

# AbsenceRequest PIPA Task Descriptor
task-description=Examples - Absence Request
task-role-owners=examples\\employee
formURI=/AbsenceRequest/AbsenceRequest.xform
formNamespace=http://www.intalio.com/workflow/forms/AbsenceRequest/AbsenceRequest
processEndpoint=http://localhost:8080/ode/processes/AbsenceRequest/Employee_To_AbsenceRequest
userProcessInitSOAPAction=http://www.example.com/AbsenceRequest/Employee_To_AbsenceRequest/Employee_To_AbsenceRequest_PortType/Receive_Absence_Request

The most important attribute are:

  • task-description: is the title the PIPA will be used to show itself in, for example, the UI-FW processes list
  • task-role-owners: along with its sibling user-owners, is a comma-separated list of owners for the task. The task will be shown in the related people list.
  • formURI: is the full, or relative URL where the form can be found. This goes along the form manager configuration.
  • processEndpoing: is the axis service that will be called to start the process
Site powered by a free Open Source Project / Non-profit License (more) of Confluence - the Enterprise wiki.
Learn more or evaluate Confluence for your organisation.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 1.4.1 Build:#212 Jun 02, 2005) - Bug/feature request - Contact Administrators