OC_GetTrackingData

This function does not return the same TDR more than once, even when called simultaneously from multiple threads. A given TDR will only be returned from one of the potential multiple calls to this function.

The only exception is if OC_InitializeTrackingData is called. If there are any TDRs that have been delivered to the caller but not acknowledged then they will be re-sent. Any re-sent TDRs will have its reset-field set to 1.

If the specified username does not exist in the content publisher system, then this function will respond in the same manner as if there were no TDRs available for an existing user.

Note: If you are using OLSA with Privacy Support enabled, when invoking this web service, you must specify the login name of a user created using the UM_CreateUser web service, not the login name of a user created in SkillPort. This is because a hashed login name is required by this web service, and only OLSA (not SkillPort) creates this type of login name.

Inputs

• customerId - String identifies the customer of OLSA environment.
• TdrType - all (default), direct, indirect
• userName - Login name of the user. This is optional.

Outputs

• Handle
• MoreFlag - true means there may be more TDRs to retrieve that match the specified criteria so the caller may choose to call this function again after processing the current array of TrackingDataRecords, otherwise false
• tDataRecords - Array of TrackingDataRecords matching the specified criteria
  • If array is non-empty, then Handle must be non-null. MoreFlag may be true or false.
  • If array is empty, then NoResultsAvailableFault will be thrown.

Additional Faults

The following table lists additional faults this service may produce, along with the error condition that causes the fault.