RITM Approval Field set as 'Requested' by OOTB BR even tough there is no approval attached

[juanmalfonso22]

Hello, 

I discovered the following behavior in the RITMs which is OOTB and I am trying to understand why it is like that? For me it makes no sense.

The 'Approval' field in the 'sc_req_item' table has 'Not Yet Requested' as default value, which is totally fine.

But there is an OOTB BR 'Cascade Request Approval to Request Item' in the sc_request table which is triggered once the REQ gets approved, and it is changing the state of the 'Approval' field in the child RITMs to 'Requested' automatically.

So, once the Flow starts running in the RITM, this field is showing 'Requested' when in fact there was no approval triggered yet or there is no approval at all, so when closing the RITM it contains the wrong value.

This is the OOTB behavior, do you know why it is like this? Reports are showing invalid data and users are complaining this is not working well, when in fact it is baseline.

Thank you!

[Eitan_B]

@juanmalfonso22 
when you say this is an OOB behavior, what exactly are you referring to? an OOB flow that you are leveraging?

Or is this a custom-built flow? If so, you might want to add STAGES for each main step in your flow: before approval, after approval, and when the RITM is closed completely. 

please provide more details. 

[juanmalfonso22]

Hi @Eitan_B 

By OOTB behavior I mean it comes baseline with the system. 

Please check in any fresh PDI, when creating a new RITM the approval field is set as 'Requested' as you can see in the attached screenshot.

[psjajda]

 Hi Juanmalfonso22, 

I am also facing similar issue. Did you able to find the fix or reason for it? How it should be resolved?

Please respond.

Thank you.

[juanmalfonso22]

Hi @psjajda ! No, actually I decided to just hide this field from the form and the activities since it was confusing all itil users.

It works like that baseline, which for me makes no sense.