Question
atos
IN
Last activity: 10 Jan 2024 10:40 EST
Control mismatch issue
We are facing a control mismatch issue for an oracle form control. It is matching in our local machine but failing in PROD VM.
We checked the IE version is different but the java version is still same.
Please tell if this difference is impacting us or there can be some other underlying issue which needs to be looked after.
The match rules used are sequence match rule and position match rule. As mentioned earlier the control matches in local machine but fails in PROD VM.
***Edited by Moderator Rupashree to add Capability tags***
Accepted Solution
Updated: 10 Jan 2024 10:40 EST
Pegasystems Inc.
US
@anshumanj16952342 It is best to think of match rules and how they might apply to different environments as if you were the developer writing the application you are interrogating. In this case Oracle Forms. A match rule can be thought of like instructions you might give to a valet who you are sending to retrieve your car in a parking garage. The more specific you can be, the better the chances of getting the correct car brought back to you. In this case, what are the differences between environments? Since you are using a Position match rule, is the control you are looking for in a new position in production? The sequence match rule will essentially be the order in which that type of control is added to the form. Could production have different controls that would change the sequence? These two are likely not very specific match rules that are obviously different between environments. Are there any other properties you can use that are more specific? For example, does the control have a name, ID, or some text you can use as a match rule? Are there other match rules that might be more specific that would apply? One trick you can use for some controls that are "generic" but have children that can be matched specifically, is the Control Children Match rule. This matches the parent based on the match of the children.
@anshumanj16952342 It is best to think of match rules and how they might apply to different environments as if you were the developer writing the application you are interrogating. In this case Oracle Forms. A match rule can be thought of like instructions you might give to a valet who you are sending to retrieve your car in a parking garage. The more specific you can be, the better the chances of getting the correct car brought back to you. In this case, what are the differences between environments? Since you are using a Position match rule, is the control you are looking for in a new position in production? The sequence match rule will essentially be the order in which that type of control is added to the form. Could production have different controls that would change the sequence? These two are likely not very specific match rules that are obviously different between environments. Are there any other properties you can use that are more specific? For example, does the control have a name, ID, or some text you can use as a match rule? Are there other match rules that might be more specific that would apply? One trick you can use for some controls that are "generic" but have children that can be matched specifically, is the Control Children Match rule. This matches the parent based on the match of the children. Going back to our parking garage analogy, you might not remember the parking space you are parked in, but you can help the valet locate it by giving them some very specific information about your vehicle. If you give them your license plate value, then once they locate that, they will know what parking space (the space is the parent in this case) your vehicle is in.