- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2024 06:14 AM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2024 11:22 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2024 06:38 AM
MID Server properties
alias_filtering_behavior Sets the behavior of Discovery aliases. Behaviors define how strictly the system enforces the use of credential aliases in Discovery schedules.
- Type: string
- Default value: loose
- strict: Aliases defined for the credential must match the aliases configured for the probe.
- loose: The probe's credential is used if it contains all the aliases specified in the schedule.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2024 06:40 AM
Hi @kumar junior11,
'alias_filtering_behavior' is a system property specific to the MID Server. As per the docs link below:
"Sets the behavior of Discovery aliases. Behaviors define how strictly the system enforces the use of credential aliases in Discovery schedules.
- Type: string
- Default value: loose
- strict: Aliases defined for the credential must match the aliases configured for the probe.
- loose: The probe's credential is used if it contains all the aliases specified in the schedule.
To answer your question more generally, system properties store system property values in server-side caches to avoid querying the database for configuration settings. They are used extensively across the SN instance and you are able to create your own.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2024 07:18 AM
we dont have mid server in our instance , is there any use of these property without mid server . i need a clarity like these property completely related or comes under mid server .
thanks for the response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2024 07:52 AM - edited ‎07-01-2024 08:00 AM
Hi @kumar junior11,
To answer your question directly - if you don't have a mid server, then you're correct, there is no use (or use as it was intended) for this property.
I'm guessing your question is, what should you do it if it's not being used.
First off, search to see if it's being called or referenced in any business rules, script includes etc.
In the global search on the homepage, type the system proeprty in there for a starting point.
A good example for comparison is another widely used system property:glide.sc.checkbox_width which when you search in the gobal search should return 2 results, both the system proeprty itself and a common business rule it's referenced in.
Note - they are extremely low footprint and I would advise against deleting or removing system properties (to avoid any current or potential future use, especially if it's a SN generated property) unless it it one you have created and know it's full use or non-use etc.
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
