In IDE3 working but not working in UAT

saic63255649417
Tera Contributor

5 hours ago

The functionality is working as expected in IDE3. The update set has been committed successfully in UAT, and there were no errors during deployment. However, the functionality is still not working in UAT environment.

 

could u please help me identify the reason or let me know if there are any additional steps or configurations required in UAT?

 

0 Helpfuls
  • 131 Views
2 REPLIES 2

Tanushree Maiti
Tera Patron

4 hours ago

Hi @saic63255649417 

 

Explain what functionality is working IDE3 and not working in UAT.

 

If it is failing due data related , that also check . e.g if you have any custom table ->added record in lower instance, that is not automatically added to update set. You have to use related link:  Forced to update set  to capture in update set..

There could other possibilities as well.

Explain what discrepancy you are getting in functionality.

 

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
0 Helpfuls

saic63255649417
Tera Contributor
In response to Tanushree Maiti

59m ago

Thank you for your update 

 

The functionality I modified is the Aprroval workflow for the external DNS request.

In IDE3, the workflow resolves the approval correctly based on the approvedBy value return  by API. if approvedBy is null, inactive, or the same as the application owner, the workflow correctly routes the approval to the application owner as per the implementation logic. 

But In UAT, after the update set was committed successfully with  no commit errors, the approval routing is incorrect.

0 Helpfuls