Deprecating Telco List for Order CaptureIn Washington release, we are deprecating Telco List (a variant of Default List page under CSM Configurable Workspace in UI Builder) and Telco Simple List (a variant of Default Simple List page under CSM Configurable Workspace in UI Builder) by deleting their corresponding assets from our code base in Configurable Workspace for Order Management. We introduced these two variants to enhance order capture experience in pre-Washington releases. When user initiates order capture process but does not finish in one setting, they should be able to come back to that order and resume order capture process using our order capture UI, instead of being directed to record page (which is the default behavior). We achieved this by customizing Default List’s record opening logic in Telco List, i.e., checking order state and some other attributes, and redirect to order capture UI instead of record page. In Washington release, Configurable Workspace for Order Management plugin is being used by multiple other plugins, and these two variants are interfering with Declarative Action functions that are introduced by other teams. Consequently, we made the decision to remove these two variants. New users of OMT (Washington and on) should not experience any issues by installing latest versions of Order Management plugins. For existing users who choose to upgrade to Washington version of Order Management, they will not have these two variants removed; instead, a fix script “Deactivate telco list screen records” will run to inactivate these two variants. If the screens of these two variants were not deactivated upon plugin upgrade, then user can manually run this fix script. This step ensures user upgrading to latest OMT will get the full experience of new order capture. It is advised that all users who choose to upgrade to Washington deactivate their telco list screens. If user decides to continue using old order capture UI after having upgraded to Washington version of OMT, then they can do so by creating a True/False system property “pre_washington_order_capture_enabled” under Configurable Workspace scope (sn_app_orm_wksp). The following issues may occur if user decides to old order capture UI Since telco list and telco simple list are deactivated, user will not face any issues using existing declarative actions on List page. For example, clicking “New” on List view or “Create Order” on account page will open old order capture UI in a modal, if “pre_washington_order_capture_enabled” property is true. However, if user reactivates telco list at this time, Declarative Actions configured on List may not work. A use case would be: user activates telco list but decides to use new order capture modal pop up. User needs to check the following: In corresponding declarative action, ensure appropriate UX Add-on Event Mapping records are created. Records in this table are responsible for linking modal opening actions to appropriate macroponent definitions. Notice in this screenshot, this DA has event mappings configured to open new Order Capture UI but not the old one.Ensure appropriate UX App Routes are created under macroponent definition page. Notice in this screen shot, both old UI (Interceptor) and new UI (orderGenerator) are present. If old UI is enabled and user does not finish order capture in one setting and leaves the UI, they have the option to return and continue work on that order in old UI. In this scenario we are noticing an issue where two tabs are opened: both the new UI and old UI are opened in two separate tabs. If, upon record opening, user decides to click on new UI tab, then page will forcefully refresh and redirect user back to old UI. If user wishes to close this order record, they should first close new UI tab, which is not displayed, otherwise the page will refresh. This is a known platform limitation which we are working with corresponding teams to resolve.