Currently there are settings that use the name to try and build up an exclusion NOT list of resources so that when a customer opens their programs/local files/transactions they don't see the DFH, CE, ... ones and only see the ones that represent that application resources in the region.
Rather than using name, it may be better to use DEFINESOURCE. If by default we exclude SYSTEM and DFH* that looks as though it is more effective that using name.
We should allow a user to extend the list to include vendor DEFINESOURCE values as well.
We could model the UI based on how VS Code allows users to add filters to restrict the files they see, where values are entered and combined together, rather than have a raw CRITERIA value (which makes it more error prone as a mistake in the field value would cause a bad request to be made)
Currently there are settings that use the name to try and build up an exclusion NOT list of resources so that when a customer opens their programs/local files/transactions they don't see the DFH, CE, ... ones and only see the ones that represent that application resources in the region.
Rather than using name, it may be better to use DEFINESOURCE. If by default we exclude SYSTEM and DFH* that looks as though it is more effective that using name.
We should allow a user to extend the list to include vendor DEFINESOURCE values as well. We could model the UI based on how VS Code allows users to add filters to restrict the files they see, where values are entered and combined together, rather than have a raw CRITERIA value (which makes it more error prone as a mistake in the field value would cause a bad request to be made)