This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Sample Business Scenario for Producteev

Owned by Former user (Deleted)
Last updated: Aug 31, 2015
2 min read

You can use the Producteev connector to manage the following key use cases in a business scenario:

The following diagram illustrates the steps you need to follow in each of these use cases and the external applications (Zoho CRM, JotForm, BugHerd, Mandrill and PagerDuty) you could integrate with along the way using the relevant ESB connectors.

Assumptions

  • All the projects are assumed to be created under the same workspace.
  • Labels such as ‘Production Issue’, ‘Bug’ should be created in the Producteev API.
  • All the won potentials in Zoho CRM, Producteev, BugHerd and PagerDuty are available in Producteev as projects (this can be done offline).
  • Only the cases in status 'new' will be considered for the scenario. Cases which are in status 'Escalated', 'On hold' or 'Closed' will be skipped.
  • At the point of resolving a bug in BugHerd or resolving an incident in PagerDuty the resolution will be added as a comment and this will be updated in Producteev task as a note.

  • All the assignees (employees) are assumed to be existing in all the accounts (Zoho CRM,Producteev,BugHerd and PagerDuty)

  • All the projects in the Producteev account belongs to one single network.

  • All the incidents in the PagerDuty account belongs to one single service.

Prerequisites

  1. The following custom fields should be available in Zoho CRM:

    1.  For Cases: 

      1. Customized drop down list (Pick List) named as 'Task Label' having two values as 'Bug' and 'Production-Issue' to select the type of issue. 
      2. A text field named as 'Producteev Task ID'.
    2. For Potentials:
      1. A text field named as 'Producteev Project ID'.
  2.  Two labels named as ‘Production-Issue' and ‘Bug’ needs to be created in the Producteev account.
  3. Create a network in Producteev and note its network ID for further reference.
  4. Create a service in PagerDuty and note its service key and service ID for further reference.

Environment Setup to Run the Producteev Scenarios

  • Download and initialize ESB 4.9.0-BETA-SNAPSHOT with patches.
  • Follow the instructions given in the developer guide of the above connectors, and enable the ESB axis configurations accordingly.
  • If required, add the corresponding website security certificates to the ESB for these connectors. 
  • Add the following sequences and templates in the common directory (<PRODUCTEEV_CONNECTOR_HOME>/producteev-integrated-scenarios/src/common), to the ESB that are listed below:

    • sequences - faultHandlerSeq.xml
      removeResponseHeaders.xml 

    • templates - responseHandlerTemplate.xml
       retrieveTaskDetailsFromNotes.xml 

  • Each scenario folder consists of sub-folders named "Case-xxx". Before executing each case, be sure to read the corresponding use case for that using the links at the top of this page.