Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cookie-law-info domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/necessid/necessidad.uk/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the insert-headers-and-footers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/necessid/necessidad.uk/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/necessid/necessidad.uk/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/necessid/necessidad.uk/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/necessid/necessidad.uk/wp-includes/functions.php on line 6114
Considerations When Using Resco OnLoad Rules - Necessidad

Considerations When Using Resco OnLoad Rules

Resco OnLoad Rules

Resco OnLoad rules are a feature of Resco Mobile CRM, a customer relationship management platform for businesses.

OnLoad rules are used to automate various tasks and actions within the Resco platform. They allow you to define conditions and actions that are triggered when a form or record is loaded within the platform.

Some common uses for OnLoad rules include automatically populating fields, calculating values, and changing the appearance or behavior of a form based on certain conditions Such as to :

  • Hide/show fields
  • Enable/disable fields
  • Hide/show tabs
  • Assign styles to fields or the entire form
  • Automatically assign values to fields, e.g. date & time, location, company number, etc.

OnLoad rules can be configured by system administrators. They can also be imported and exported between different instances of Resco Mobile CRM.

Resco Unload Rule

The image above shows an example of making a form on account read only if it was created over 6 months ago. Below is a demo of the effect.

 

As you can see in the replay above, our form for the New account is editable whereas the old accounts are not.

Resco onLoad rules can greatly improve the efficiency and accuracy of data entry and help to ensure that your business processes are consistently followed. They can also make it easier to use the Resco platform, by automating repetitive tasks and streamlining workflows.

On Load rules are best suited to handling initializations because sers must wait for the On Load rule to be fully executed before seeing the form in the desired format. 

It is best practice to set up only the initialization actions in the On Load rule, mainly because  its execution time is minimal.

Be cautious when configuring OnLoad rules: It is advisable to use OnChange Rules to  Hide/show/enable/disable fields and tabs dynamically – after initialisation. The actions related to changes on a form while working with it are better set up in the On Change rule.

Check out our blog on OnChange Rules.

Stay up to date with our Newsletter

By entering your email, you agree to our Terms and Conditions and Privacy Policy.

Stay up to date with our Newsletter

By entering your email, you agree to our Terms and Conditions and Privacy Policy.

2530833