I think it is possible with a validation rule. I don't have a specific example but It would need a lookup to the CI object where it cannot be blank or null value. Hope that helps you.
Hi Brandon Smith,
You can consider a new lookup to Base Element on change. Add here a validation rule NOT(ISBLANK(xxxx))
On top, make sure you add a process builder to create the "CI Change link" with the CI from your custom lookup. That way your info is also displayed in the CI explorer, Collision etc.
On top; Less clicks to go to the details page and in most scenario's just 1 CI is impacted,
Thanks Paul. We have instances where there are multiple CIs that need to be linked. Is there a way have the validation rule check to see if CIs have been linked on the 'Details' tab of the ticket? This would fulfill the necessary requirements that we are looking for.
There are some options, but the link is set on "Change CI link". While you save your actions on Change.
So on change you need a validation to fire on a checkbox or so. Set this checkbox to True when a CI Change link is inserted.
Hope this helps.
Thanks again Paul for providing us these options!
We do something similar here for Incidents with linked Problems. If we have incidents that we are closing with a work around we populate the work around in the resolution and we choose a value called, "Refer to Problem Link" for our Cause. To make sure that there really is a Problem linked to the incident we created the following validation rule (see below). "Number_of_linked_problems" is a custom roll-up summary field off of the Incident Problem Link.
Maybe this will give you some ideas on how to come up with a solution that works for your use case using the Change CI Link.
text(Cause_pl__c) = 'Refer to Problem Link' && text(Number_of_linked_Problems__c) = '0'
Hi Paul -
Thanks for the explanation. Can you clarify, are you saying that a field to input the CI details needs to be created in order for this to work? I'm trying to create a workflow rule that will check to see if there are any CI links in the related list, but it does not give me this option to refer to Base Elements when creating the workflow rule. The CI link should be attached to the change and if it is, the checkbox does not get checked. If the CI link is not there, the checkbox is checked and a validation rule is triggered. Without using a custom CI field, how do I get the workflow rule to check against the related list to determine if a CI is linked?
Just saw this post....I am going to investigate this roll up summary a little more. This may give us the functionality we need! Thanks for the input John!
What you can do;
Create a checkbox on change, don’t add it to the layout.
Create a workflowrule (or roll up, as suggested by Dan, to fire on create of Ci change link.
Criteria; when name is Null and checkbox is false
Add a fieldupdate to change as formula to set the checkbox true.
Now create a validation that you cannot change the status, or close the change, when the checkbox is true.
Hope this helps?
Ps just checks for 1 linked ci