TimeClockSync
The following operations are supported. For a formal definition, please review the Service Description.
- Add_TimeClock_CO_Sync_Data
-
Add_TimeClock_EE_Data
Accepts TimeClock Employee Data From Tablet -
Get_CWSecCoConfig_Sync_Data
Retrieve CWSecCoConfig Data for Tablet -
Get_CWSecUsers_Sync_Data
Retrieve CWSecUSers Data for Tablet -
Get_TimeClock_CC1_Sync_Data
Retrieve TimeClock CC1 Data for Tablet -
Get_TimeClock_CC2_Sync_Data
Retrieve TimeClock CC2 Data for Tablet -
Get_TimeClock_CC3_Sync_Data
Retrieve TimeClock CC3 Data for Tablet -
Get_TimeClock_CC4_Sync_Data
Retrieve TimeClock CC4 Data for Tablet -
Get_TimeClock_CC5_Sync_Data
Retrieve TimeClock CC5 Data for Tablet -
Get_TimeClock_CO_MAC_Sync_Data
Retrieve TimeClock CO MAC Data for Tablet -
Get_TimeClock_CO_Users_Sync_Data
Retrieve TimeClock Co Users Data for Tablet -
Get_TimeClock_Co_CodeDesc_Sync_Data
Retrieve TimeClock CO CodeDesc Data for Tablet -
Get_TimeClock_Co_TimeCodes_Sync_Data
Retrieve TimeClock CO TimeCode Data for Tablet -
Get_TimeClock_JobCode_Sync_Data
Retrieve TimeClock JobCode Data for Tablet -
Get_TimeClock_Local_Cinfo_Sync_Data
Retrieve Local Cinfo Data for Tablet -
Get_TimeClock_Local_ERates_Sync_Data
Retrieve Local ERates Data for Tablet -
Get_TimeClock_Local_Einfo_Sync_Data
Retrieve Local Einfo Data for Tablet -
Get_TimeClock_ShiftCodes_Sync_Data
Retrieve ShiftCode Data for Tablet -
Get_TimeClock_TimeAttend_TimeCode_Type_Sync_Data
Retrieve TimeAttend TimeCode Type Data for Tablet -
Get_TimeClock_TimeCode_CO_Users_Sync_Data
Retrieve TimeCode Co Users Data for Tablet -
Get_Timeclock_Co_Map_Sync_Data
Retrieve TimeClock Co Map Data for Tablet -
Update_Sync_Complete
Updated all data that has been synced
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.