REQ still active when state is closed skipped

[JordyZ]

Hi,

I have some requests that are active while in closed skipped state, isn't it supposed to turn inactive? The RITM under the REQ is also closed skipped but is not active.

Is this supposed to be like this OOB? If not, which BR do I change?

Thanks in advance.

[Manmohan K]

Hi @JordyZ ,

I have checked in an OOB instance and  REQ if closed skipped remains Active = True OOB.

But in other states like Closed Complete, Closed Incomplete, Closed Cancelled or Closed Rejected , the REQ becomes Active = False

The behavior is governed by OOB Business rules - "Request reopened" (it sets the request from false to active when conditions are met) and "Mark Request Closed" - This sets the request to active false when the conditions are met in the script tab of BR

[JordyZ]

Hi @Manmohan K , thanks for replying!

If I want to have REQ inactive when state is closed skipped, how do I change this?

[Manmohan K]

In the Business rule  - "Mark Request Closed", You can add another or condition after line 4 which says current.request_state=="closed_skipped" to turn REQ inactive when state is closed skipped

[Bert_c1]

Hi,

I see a Business rule name "Mark Request Closed" defined on the sc_request table, that sets the Active field based on the stage field value. There is logic included there for the 'request_state' field value.  there is the business rule named "Set Active Flag" defined on the sc_req_item table, that has very similar logic. Workflows are in play here.