Business Rule Condition field is too short

[felipe_barbosa]

I know this might sound crazy, but, currently I am having issues with a long condition I need on a business rule, and the current size of the field (254) is not attending my needs. Do anyone knows of any impact of changing this size to maybe 400 ?

What I need to know in summary is, if I change the size, will it continue to work as usual?

Thanks and regards,

Felipe

[ashish68 · Accepted solution]

Hi,

So there are two ways:-

1. Best practice of ServiceNow is to write a script include and call it in the condition. The Script include will do all your calculations and return true or false. This way you do need to update the OOB feature i.e. length in your case & so you will not have any upgrade issues in near future.

2. If you still want to go with the same, then you can surely increase it, but remember that it will not be updated by the Upgrade process when you do an upgrade form your current version to the version out by ServiceNow.

Thanks

Ashish

[geoffcox]

I approve ashish's answer!

[poyntzj]

We do Ashish says

I have a Script include called <company>LongConditionList

inside I have various functions (for the different conditions, etc)

depending on your need, you can make it return a true / false or a long string

true / false example

(new GroupMLongConditionList().VersiantWSDLBR(current)) == true;

The function returns true / false

returning long string

(new GroupMLongConditionList().MonitoringAddresses())

The function returns a long string line

email.from.toLowerCase().search(\'address1@domain.com\') || email.from.toLowerCase().search(\'address2@domain.com\') ||

email.from.toLowerCase().search(\'address3@domain.com\') ||

email.from.toLowerCase().search(\'address4@domain.com\') ||

and so on.

[ashish68]

Hi Julian,

Can you please mark the answer as completed by me.

Thanks

Ashish

[poyntzj]

Hi Ashish, I can't do anything here myself besides agree your answer is correct - I just elaborated on yours