Validate Lifecycle combination Business Rule error in Flow Designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
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.
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:
Life cycle Control table:
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Lucky1 ,
It's strange; this issue shouldn't occur unless someone has customized either the "Validate lifecycle combination" (table = Configuration Item [cmdb_ci]) Business Rule or the "LifeCycleUtil" Script Include. Please check if anything differs from the OOTB version.
If this solution helps you then, mark it as accepted solution ✔️ and give thumbs up👍!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Debundudas,
Thanks for your reply.
This I am doing in my PDI.
Also, I see there are no previous versions for either Business rule or even the script include.
Regards,
Lucky
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Okay, can you share a screenshot of the update record flow action ? Just wanted to see the field value mapping. I will replicate this in my pdi and check if it's working or not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi debendudas,
Here is the screenshot.
Also note one more point, this error is coming up in my friend's PDI as well once he tried.
Regards,
Lucky