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 Sirportly

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

You can use the Sirportly 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 (Formstack, Mandrill and CashBoard) you could integrate with along the way using the relevant ESB connectors.

Environment Setup to Run the Sirportly Scenarios

  • 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 (inside <SIRPORTLY_CONNECTOR_HOME>/Sirportly-integrated-scenarios/src/common), to the ESB that are listed below:

    • sequences - faultHandlerSeq.xml
      removeResponseHeaders.xml 

    • templates - responseHandlerTemplate.xml
        base64Decoder.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.

Prerequisites

  • There must be a department named 'Helpdesk Support' for the brand of the company (there will be a default brand created for the company on creation of the Sirportly account).

  • Create a project in Cashboard named as 'Helpdesk Support' and keep the project ID for further reference.
  • These custom fields are required in Sirportly (Custom fields can be created by following 'Admin'-->'Work Flow'-->'Custom Fields') :
    • projectId: The Cashboard project ID to which the ticket belongs to.
    • IsBIllable : Indicates whether the ticket is billable or not.
    • totalEstimation: Holds the total estimation amount of this ticket.

Assumptions

  • All the client companies in Sirportly are available in Cashboard.

  • Only the Sirportly tickets that are created through the scenario execution will be considered for this automation and the tickets that are created in Sirportly (offline) will be skipped.
  • All the Sirportly tickets which are reported by the clients will be added to the default brand of the Sirportly account and to the 'Helpdesk Support' department that is created in the Prerequisites section.
  • All the project lists that are created from this automation will hold only one task call 'Workshop Operations' .
  • A ticket in Sirportly is equivalent to a project-list in Cashboard.

Note

Please note that the cases need to be executed in the same order as they appear in this document as they are inter-related and cannot be executed independently.