state not update

[Vaibhav Ramteke]

Hello,

Im creating ebonding of problem in servicenow instance both side problem create and update all fields update but the only is State(life cycle) is not change.

Ex. In A create/update to B create/update in this process all work short description, description work note, all 
just only state New-> Assess work but remain state not work as usually in A side state as normally work but my issue is when in A  New->Assess->Root cause->Fix in progress->Resolved->closed 
this all not update only new->assess work 

this is regarding problem ebonding issue 

im stuck here
 

[Me Being Mustaq]

Hi @Vaibhav Ramteke ,

It sounds like your Problem eBonding is working for all fields except the State (Lifecycle State) after New → Assess.

 As per issue mentioned above in question most likely 

State changes Assess → Root Cause → Fix in Progress → Resolved → Closed do not sync

1. State Mapping is Missing:- In many eBonding integrations, the state values must be explicitly       

     mapped.

2. Different State Values Between Instances Even if labels look the same, the backend values may

     differ.

A Instance:

Assess = 102

Root Cause = 103

Resolved = 104

B Instance:

Assess = 2

Root Cause = 3

Resolved = 4

If the integration sends 103 but B expects 3, the update will fail. Check sys_choice for the Problem table state field in both instances.

Most Likely Issue

Since New → Assess works but all later states do not, the most common cause is state mapping or lifecycle transition restrictions in the target instance. The integration is probably sending the update, but Instance B does not recognize or allow the subsequent state values.

Warm Regards,

Shaik Mustaq.

[Vaibhav Ramteke]

in both instance backend value same 

[Me Being Mustaq]

Hi @Vaibhav Ramteke ,

In the target instance, run a Background Script:

var prb = new GlideRecord('problem');
prb.get('YOUR_SYS_ID');
prb.state = 'Root Cause value';
prb.update();

If this update fails or reverts, the issue is not eBonding. It's a Business Rule, Flow, Data Policy, or lifecycle validation on the target instance.

Since New → Assess works, my strongest suspicion is that the outbound or inbound Business Rule contains logic specifically for the Assess state, or another Business Rule on the target instance prevents transitions beyond Assess.

Share the outbound and inbound Business Rule scripts, and I can pinpoint the exact line causing the state synchronization issue.

Warm Regards,

Shaik Mustaq

[gaurrohi]

Few additional questions:

• What approach or method did you use for the eBonding integration? (Business Rule/Flow Designer)
• Have you checked the return status and the response?
• Have you reviewed the state mapping logic implemented in the solution?