Closed
Dynamically use parse rule in soap response
We have a requirement that with the value in soap header field we have to chose the Parse Rule to parse the response. How can this be achived?
This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.
We have a requirement that with the value in soap header field we have to chose the Parse Rule to parse the response. How can this be achived?
STEPS:-
1. Map the response XML to a text property [say MessageResponse]
2. Parse the SOAP Message Header and get the required header field (say Message ID)
3. Maintain a decision table as shown below and set the desired Response Parse Rule (depending on Message ID)
|
Message ID |
Response Parse Rule |
Response Data transform |
if |
100 |
Parse-Rule1 |
Data-Transform1 |
Else if |
200 |
Parse-Rule2 |
Data-Transform2 |
Else if |
300 |
STEPS:-
1. Map the response XML to a text property [say MessageResponse]
2. Parse the SOAP Message Header and get the required header field (say Message ID)
3. Maintain a decision table as shown below and set the desired Response Parse Rule (depending on Message ID)
|
Message ID |
Response Parse Rule |
Response Data transform |
if |
100 |
Parse-Rule1 |
Data-Transform1 |
Else if |
200 |
Parse-Rule2 |
Data-Transform2 |
Else if |
300 |
Parse-Rule3 |
Data-Transform3 |
Else if |
400 |
Parse-Rule4 |
Data-Transform4 |
|
|
|
|
4. Call the decision table and set the parse rule
5. Now use the above parse rule to parse the response.
I am using this approach in my current application.
Thanks Kiran. I too eneded up doing the same thing.
Question Solved
Question
Question Solved
Question
Question
Question
Question
Question
Discussion
Question
Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.