Question
Tokio Marine & Nichido Fire Insurance Co.,Ltd.
JP
Last activity: 29 May 2024 13:18 EDT
interrogate comes off
Please tell me about the differences in "openspan_path".
Regarding the RPA resources that reference Salesforce, the "openspan_path" has changed, and it may cause the interrogation to come off.
I think the cause is some changes on the Salesforce side, but it also occurs when migrating from a sandbox environment to a production environment.
In this case, the "openspan_path" for all reference items is changed, the interrogation comes off, and re-interrogation was performed in the production environment.
Since the re-interrogation is being done by stopping the production environment in use by the user, it takes time.
Therefore, please tell me how to prevent this phenomenon from happening.
For example, changing some settings or whether upgrading to version "v Proprietary information hidden(3.1.20)" will resolve the issue.
The "openspan_path" is recognized as being numbered by Pega.
For reference, I will provide the paths before and after the change for the items that actually had differences.
Before the change:
Please tell me about the differences in "openspan_path".
Regarding the RPA resources that reference Salesforce, the "openspan_path" has changed, and it may cause the interrogation to come off.
I think the cause is some changes on the Salesforce side, but it also occurs when migrating from a sandbox environment to a production environment.
In this case, the "openspan_path" for all reference items is changed, the interrogation comes off, and re-interrogation was performed in the production environment.
Since the re-interrogation is being done by stopping the production environment in use by the user, it takes time.
Therefore, please tell me how to prevent this phenomenon from happening.
For example, changing some settings or whether upgrading to version "v Proprietary information hidden(3.1.20)" will resolve the issue.
The "openspan_path" is recognized as being numbered by Pega.
For reference, I will provide the paths before and after the change for the items that actually had differences.
Before the change:
BUTTON,LIGHTNING-BUTTON-MENU,LI,UL,RUNTIME_PLATFORM_ACTIONS-ACTIONS-RIBBON,DIV,DIV,DIV,DIV,LST-LIST-VIEW-MANAGER-HEADER,LST-COMMON-LIST-INTERNAL,LST-RELATED-LIST-VIEW-MANAGER,ARTICLE,LST-RELATED-LIST-SINGLE-APP-BUILDER-MAPPER,LAF-PROGRESSIVE-CONTAINER,LST-RELATED-LIST-SINGLE-CONTAINER,DIV,DIV,LST-RELATED-LIST-CONTAINER,FLEXIPAGE-COMPONENT2,FLEXIPAGE-TAB2,FLEXIPAGE-TABSET2,FLEXIPAGE-COMPONENT2,FLEXIPAGE-RECORD-HOME-THREE-COL-TEMPLATE-DESKTOP2,RECORD_FLEXIPAGE-DESKTOP-RECORD-PAGE-DECORATOR,FORCEGENERATED-FLEXIPAGE_INSUREDPERSONPAGE_INSUREDPERSON__C__VIEW_JS,FORCEGENERATED-ADG-ROLLUP_COMPONENT___FORCE-GENERATED__FLEXIPAGE_-RECORD-PAGE___-INSURED-PERSON-PAGE___-INSURED-PERSON__C___-V-I-E-W,ONE-RECORD-HOME-FLEXIPAGE2,DIV,DIV,DIV,DIV,DIV,DIV,SECTION,DIV,DIV,SECTION,DIV,DIV,DIV,DIV,SECTION,DIV,DIV,BODY,HTML
After the change:
BUTTON,LIGHTNING-BUTTON-MENU,LI,UL,RUNTIME_PLATFORM_ACTIONS-ACTIONS-RIBBON,DIV,DIV,DIV,DIV,LST-LIST-VIEW-MANAGER-HEADER,LST-COMMON-LIST-INTERNAL,LST-RELATED-LIST-VIEW-MANAGER,ARTICLE,LST-RELATED-LIST-SINGLE-APP-BUILDER-MAPPER,LAF-PROGRESSIVE-CONTAINER,LST-RELATED-LIST-SINGLE-CONTAINER,DIV,DIV,LST-RELATED-LIST-CONTAINER,FLEXIPAGE-COMPONENT2,FLEXIPAGE-TAB2,FLEXIPAGE-TABSET2,FLEXIPAGE-COMPONENT2,FLEXIPAGE-RECORD-HOME-THREE-COL-TEMPLATE-DESKTOP2,RECORD_FLEXIPAGE-DESKTOP-RECORD-PAGE-DECORATOR,FORCEGENERATED-FLEXIPAGE_INSUREDPERSONPAGE_INSUREDPERSON__C__VIEW_JS___LMT___1699332503000,FORCEGENERATED-ADG-ROLLUP_COMPONENT___FORCE-GENERATED__FLEXIPAGE_-RECORD-PAGE___-INSURED-PERSON-PAGE___-INSURED-PERSON__C___-V-I-E-W___-L-M-T___1699332503000,ONE-RECORD-HOME-FLEXIPAGE2,DIV,DIV,DIV,DIV,DIV,DIV,SECTION,DIV,DIV,SECTION,DIV,DIV,DIV,DIV,SECTION,DIV,DIV,BODY,HTML
Situation by version:
-
Resources not referencing Salesforce: "v Proprietary information hidden" → No interrogation comes off
-
Resources referencing Salesforce: "v Proprietary information hidden(3.1.7)" → Interrogation comes off
Accepted Solution
Updated: 29 May 2024 13:18 EDT
Pegasystems Inc.
US
@SatoshiK17114718
In short, to better match your control so that it matches in different environments, use different match rule(s) than the OpenSpan_Path match rule in this case since it differs between environments.
Longer answer:
@SatoshiK17114718
In short, to better match your control so that it matches in different environments, use different match rule(s) than the OpenSpan_Path match rule in this case since it differs between environments.
Longer answer:
The OpenSpan_Path match rule uses the path to the control in HTML hierarchy as its means of matching. In this case, there is a difference in the two paths. I don't think you can RegEx the elements in the path match rule, so you probably want to look for a better match rule to use. Remember that any match rule you choose can be affected by the application depending on how the developers coded that application to function. In this case, they have specifically used different HTML tags between environments for some purpose. To match them accurately, you now know this and can adjust how you match them accordingly. While it is not common for applications to do this, I have seen it plenty of times before. I prefer to use more specific match rules for controls that are unlikely to change between releases of the application. I generally do not like using the Path to match since a developer could insert a DIV or some other non-visual element into the path of a control for styling or other purposes and not change any of the application's functionality. This would then cause your bot's matching to fail for the control. My principal is to match on things that a developer would not change with minor releases (basically things that they cannot change without retraining users of the application or updating screenshots). A developer cannot simply change the text of a button if they feel like because even though it might be the same button, users would be confused suddenly seeing a "Search" button instead of a "Find" button. At the very least, screenshots and training materials would need to be updated for that change making one a developer is likely to do in a minor release.
Before:
FORCEGENERATED-FLEXIPAGE_INSUREDPERSONPAGE_INSUREDPERSON__C__VIEW_JS
FORCEGENERATED-ADG-ROLLUP_COMPONENT___FORCE-GENERATED__FLEXIPAGE_-RECORD-PAGE___-INSURED-PERSON-PAGE___-INSURED-PERSON__C___-V-I-E-W
After:
FORCEGENERATED-FLEXIPAGE_INSUREDPERSONPAGE_INSUREDPERSON__C__VIEW_JS___LMT___1699332503000
FORCEGENERATED-ADG-ROLLUP_COMPONENT___FORCE-GENERATED__FLEXIPAGE_-RECORD-PAGE___-INSURED-PERSON-PAGE___-INSURED-PERSON__C___-V-I-E-W___-L-M-T___1699332503000