Validate Lifecycle combination Business Rule error in Flow Designer

Lucky1
Tera Guru

Hello all,

 

When I am trying to update a Business Application record from flow designer,

I am updating with Status --- Retired, Life Cycle Stage ---- End of Life, Life Cycle stage status --- Retired.

the record is not getting updated with the values, instead it is giving error in the flow executions.

Lucky1_0-1755715292774.png

 

I have checked the business rule, and also checked the entries in Life cycle control table and Life cycle mappings table, but not understanding clearly how it works and why I got that error.

 

I see the Life cycle Mappings table record like this:

Lucky1_0-1755715767519.png

 

 

Life cycle Control table:

Lucky1_0-1755716043314.png

 

 

So, in the workflow I am doing the right thing only, then why it is throwing an errror?

 

 

Can someone help me how to update the record with these values without error.

Please I cannot use custom action and write gr.setWorkflow(false).

 

 

Thanks in advance.

Regards,

Lucky

 

9 REPLIES 9

It is very strange; it is not working in my PDI as well. 

 

However, I found a workaround, I used flow script to return the values, and it worked.

Please find the screenshots in the below:

debendudas_0-1755755693980.pngdebendudas_1-1755755719919.png

 

If this solution helps you then, mark it as accepted solution ‌‌✔️ and give thumbs up 👍

Yes,

Actually I too done the same, but my lead is asking why that error and why can't we update simply.

Hence put those logs.

 

 

Regards,

Lucky

Lucky1
Tera Guru

Also, I have put some logs into the Business rule and Script include.

In the Script include, life cycle stage value is coming as undefined.

Can some one tell me why?

My Business Rule Screenshot:

Lucky1_0-1755754375337.png

Lucky1_1-1755754474009.png

 

 

Script Include Screen shot:

Lucky1_2-1755754518866.png

 

Note: It is not going inside While loop as the value is getting undefined.

 

 

Please help.

 

 

Regards,

Lucky

 

 

Ankur Bawiskar
Tera Patron
Tera Patron

@Lucky1 

the error clearly tells some before update business rule stopped/aborted the update.

Did you check if that BR condition and script is actually blocking?

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Hello Ankur,

 

It is oob BR and oob read-only script include.

Hence I copied the Script include code and created a new Script include to put logs.

and in the BR, i commented the original one, and triggered my Script include.

 

 

Regards,

Lucky