Regarding a system property 'alias_filtering_behavior'

[kumar junior11]

do any one aware of these property 'alias_filtering_behavior'. is these property only related to mid server. if no then where it can be used. if i create these property in my instance how to test these property behaviour. advantages and disavantages. if anyone has any information it will be helpfull.

thanks ,

regards kumar.

[kumar junior11]

alias_filtering_behavior' actually this property not exist in my instance, i wanted create it in my instance if and only if it is completely not related to mid server. if the property is used without mid server then i need to create it and test the behaviour of these property.

[Robbie]

@kumar junior11,

Think of a system property as a place to save and store values which can be configured (which in turn externalize and save any changes to code).

If you do not use a mid server, and you are going to create a new system property, why potentially introduce a duplicate or overriding in the future.

Create your own unique system property to avoid all confusion and potential issue.

@kumar junior11- To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.

Thanks, Robbie

[kumar junior11]

so your conclusion is without having mid server creating these property is waste or there is no use, is it correct?.( on your words and servicenow doc's these property belongs to mid server ).

is there any negative impact if i create these property without mid server, i want some analysis on these to explain my team on why i shouldnot create these and what the behaviour if we create will it change existing behaviour ...

thank you for the response.

[Robbie · Accepted solution]

@kumar junior11,

My point is, why would you create or use a system property that SN created for any other use than it was intended?

Just because you don’t use a mid server today, it doesn’t mean you won’t in the future.

As for negative impact - as I’ve stated, it’s simply a place holder for a value. As long as nothing is leveraging (calling) this system property (and using the value stored), than there will be no impact.

Hence why I’ve mentioned searching and checking to see it isn’t used.

However, to remove all risk, create your own thus removing any issue or potential issue. It would also be handy to see in the system property name and handle that it’s unique (created by your team / org)

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.

Thanks, Robbie