Changing condition in Workflow properties is auto saved as NoneIssue Adding condition to the RITM related workflow properties and saving the conditions. After saving the condition, it is auto saved as None. Steps to reproduce: Open the Workflow Editor.Open an RITM related workflow.Open workflow properties.Notice conditions tab is visible.Try to change condition value from none to something different.Save.Notice after saving the condition, value is reverted back to none.ReleaseAnyCauseThis expected behaviour due to OOTB Business Rule "Request item handling" and deactivated OOTB UI Policy "Hide conditions for Request Item workflows or Private application scope". On OOTB instances, conditions are hidden for Requested Item (sc_req_item) Workflows, but conditions tab is visible on customer instance. This is because the OOTB UI Policy "Hide conditions for Request Item workflows or Private application scope" has been deactivated on customer instance. Now users on customer instance are able to view / attempt to change conditions for Requested Item workflows. When a user attempts to change the (now visible) conditions in workflow properties for Requested Item workflows, any changes are reverted by OOTB BR "Request item handling". ResolutionAs per OOTB functionality, conditions in the properties of RITM workflows are not able to be changed. Any changes to OOTB UI Policies or Business Rules should be done with care. Review the reasons for deactivating OOTB UI Policy "Hide conditions for Request Item workflows or Private application scope" and reactivate this UI Policy to prevent users from being able to view the conditions tab for RITM workflows.