or use a UI rule to set a field as required based on conditions. The action to take in the rule is to use a stop notification pop up which will stop the user from saving the item until the meet the condition in the rule
Hi, If we set the mandatory field for a particular item(say service call) from Admin -> Security->Prevention, that field will be set as mandatory for all the forms/templates for that item. Is there any way we can set mandatory fields for a particular form/template of that object only? For example, for service call form named abc i want caller to be mandatory field but for other forms of service call caller field is not mandatory.
you use a UI rule to set the condition. The action the Ui rule does is a "User Notification" as an Error. The Error notification will keep popping up an user notifiction prompt until the user satisfies the condition and then it will stop popping
you use a UI rule to set the condition. The action the Ui rule does is a "User Notification" as an Error. The Error notification will keep popping up an user notifiction prompt until the user satisfies the condition and then it will stop popping up
Please note if you are on SP 18 (i think) or above you loose the functionality to fire a user notification "when a value has changed". If you set the rule to be fired "before the item is saved" it will allow you to use a popup notification.
The attachment shows setting a template in the rule
Hi Peter, Thanks for the solution. Is there any way we can get the name of the form (eg. Service call all fields) automatically filled in the new custom field "Form field", instead of typing in the same or in other words how can we access the name of the form?
You can't access the name of the form, that's the problem.
As I said you can use a template for creating new ones and have that field filled in in the template and therefore any forms created by the template will have it completed.
You can also select existing forms using Advanced find or a view etc. Then right click on the selected records and choose "Update All". You can then eneter the name of the form into the field. This will allow you to do a mass update rather than one record at a time.
Hi Peter, Thanks for the valuable inputs. Your solution makes sense but the only drawback is that we need to manually fill in the FormName in the CustomField. If we want to avoid typing in the form name, we need to create a template for setting the CustomField to FormName and for templates we don't require the CustomField as suggested by Mark.