Experts can suggest you better approach, here is my understanding you can achieve this.
The following Filter INT:CHGSRM:CRQ:CreateRequest_650_Submit on CHG:Infrastructure Change form create the SRM request.
You can achieve this by adding custom field on CHG:Infrastructure Change form and create overlay on the above mentioned filter and add additional check of custom field value to prevent or create the SRM Request.
OR make create overlay on this filter CHG:CRQ:GetCreateReqFlag_025 which gets the create request flag to not get the flag based on your custom value.
Please make sure to test it well before promoting the changes.
Why not try to disable the Create Service Request on Submit from the Application Admin Console -> change Management -> Advanced Options -> Rules to stop creating SRs when change is created?
The reason that I can't use the configuring rules is stated in my second sentence.
"The challenge is that I need to be able to turn it off on a request by request function."
3 of 3 people found this helpful
Here is the issue. When submitting a single ticket we need to be able to bypass the SRM creation process. There is a field on CHG:ChangeInterface_Create called Flag_Create_Request. This field is the field that tells the system to create the SRM request. The root of the issue is that CHG:CRQ:Get_RulesValue overwrites the value entered into the field when the Change ticket is actually created.
The resolution to the issue is to disable CHG:CRQ:Get_RulesValue and create two new filters. The first still pulls back the value if Flag_Create_Request is null. The other pulls back all the values except Flag_Crate_Request if it is populated. Thereby allowing an individual to manually choose to create a SRM Request or not, as needed.
I hope this helps.
Why did you customize it when OOTB options are available?
Create Service Request on Submit
Select which action occurs when a change request is submitted.
If set to Yes, when a user submits a change request, a corresponding request is created. The customer can view this request, which indicates the change status, through the Requester Console
I think I missed your earlier comments