The following operations are supported. For a formal definition, please review the Service Description.

• AddFollowup
  Add Followup data to specefic lead
• AddmanulLead
  Add Lead To Database
• Addmanulvisitor
  Add Visitor Data
• Draftdata
  Draft Data Number
• Draftdata1
  Draft Data1
• EmployeeName
  Fetch Employee Name Before Login
• Employee_Login
  Employee Login empid , empname,password
• FetchCategory
  Fetch Category for visitor screen
• FetchCustomer
  Fetch Customer salesperson wise
• FetchCustomerOutstanding
  Customer Outstanding report
• FetchInvoiceoutstandingcust
  Invoice Outstadning report Customer Wise
• FetchLeadDetails
  Search Lead Data according to lead No
• FetchLeadReport
  Search lead report base on from date and to date
• FetchProduct
  Fetch Product for Visitro Screen
• FetchSubCategory
  fetch Subcategory for visitor
• Fetchpendingorder
  Customer pedning order report
• HDPAYREQUEST
  HDFC REQUEST
• HelloWorld
• TravelDetails
  Add Travel Expenses Details
• Traveldetailsfetch
  Search Travel Expenses base on travel Exp ID
• UpdateBatch
• adddailyexp
  Add Daily Expensess
• barclogin
  Employee login
• dailyexpreportfetch
  Search Daily Expensess Report Base on From date and to date
• fetchconvs
  Conveyance type fetch for daily expensess Form
• fetchdb
  DB Data
• fetchfollowupdetails
  Search Followup Data base on lead No
• travelreportfetch
  Search Travel Report Base on From date and to date
• updatefollowupdetail
  Update followup data base on followup line no
• visitorreports
  Search visitor report base on from date and to date

This web service is using http://tempuri.org/ as its default namespace.

Recommendation: Change the default namespace before the XML Web service is made public.

Each XML Web service needs a unique namespace in order for client applications to distinguish it from other services on the Web. http://tempuri.org/ is available for XML Web services that are under development, but published XML Web services should use a more permanent namespace.

Your XML Web service should be identified by a namespace that you control. For example, you can use your company's Internet domain name as part of the namespace. Although many XML Web service namespaces look like URLs, they need not point to actual resources on the Web. (XML Web service namespaces are URIs.)

For XML Web services creating using ASP.NET, the default namespace can be changed using the WebService attribute's Namespace property. The WebService attribute is an attribute applied to the class that contains the XML Web service methods. Below is a code example that sets the namespace to "http://microsoft.com/webservices/":

C#

[WebService(Namespace="http://microsoft.com/webservices/")]
public class MyWebService {
    // implementation
}

Visual Basic

<WebService(Namespace:="http://microsoft.com/webservices/")> Public Class MyWebService
    ' implementation
End Class

C++

[WebService(Namespace="http://microsoft.com/webservices/")]
public ref class MyWebService {
    // implementation
};

For more details on XML namespaces, see the W3C recommendation on Namespaces in XML.

For more details on WSDL, see the WSDL Specification.

For more details on URIs, see RFC 2396.