ISSUE/QUESTION: Unlike from usual debugging flow, there are several differences need to consider when performing WaDaCo debugging. Therefore, it is necessary to have the basic understanding when performing a wadaco related investigation.
ENVIRONMENT: Wadaco Client
AUDIENCE: Internal, Partner
RESOLUTION/ANSWER:
High level differences are as below:
- WaDaCo flows session always starts from Data_Capture_Session.api methods and Data_Capture_Session_Line.api methods.
- Flow always initiates with a new session ID.
- Basic WaDaCo method calls are as below.
- Depending on the functionality, corresponding product code is later called once Data_Capture_Session methods are called.
- Every process has its own package.
- WaDaCo processes are included from a postscript as below. In-case if a customer is information the processes are missing, check whether below script is correctly deployed in the environments.
- POST scripts are harvested under corresponding component. (Examples as below)
- As per to configuration items, WaDaCo flow request data for each configuration items.
- Relevant passed information can be viewed from Data_Capture_Session_Tab and Data_Capture_Session_Line_Tab. (Corresponding client forms are existing in client)
- Data_Capture_Session_Tab
-
Data_Capture_Session_Line_Tab
- Data Capture Session Client View
- Data_Capture_Session_Tab
