Servicenow_create_change_request_from_problem

[HarithaV-1908]

No description provided.

[ghost]

🎉 Snyk checks have passed. No issues have been found so far.

✅ code/snyk check is complete. No issues have been found. (View Details)

[github-actions]

Changes to plugins/servicenow-change-request-from-problem/README.md can be viewed at https://developer.moveworks.com/creator-studio/resources/plugin?id=servicenow-change-request-from-problem&commit_id=6cb0dd5bd234765d3efd801d65dfc9cfe13d7e9c;

[github-actions]

Changes to plugins/servicenow-change-request-from-problem/README.md can be viewed at https://developer.moveworks.com/creator-studio/resources/plugin?id=servicenow-change-request-from-problem&commit_id=ad595c659202fd8b184e6da34bbde0639f5f875c;

[Sudheer2137]

@HarithaV-1908 In the conversational flow, I see that we are dot-walking the response from the first API to fetch the number, description. However it should be dynamic based on the exact problem selected by the user, right?

[HarithaV-1908]

Yes @Sudheer2137 we are only retrieving the u_problem field from this to pass it to the second action

[HarithaV-1908]

@Sudheer2137

I’ve updated the output mapper with map function — it will fetch the problem based on that user selection

[HarithaV-1908]

Yes, that’s why I’ve updated it to use it by map function, so it dynamically fetches the correct item based on the selected problem

[Sudheer2137]

LGM - Approved