Software Products tab on Reclamation Rule navigates to wrong table in workspace - samp_sw_product in
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2026 08:56 AM
Detailed Description:
When creating or editing a reclamation rule in the Software Asset Workspace, the "Software Products" tab behavior differs between two instances:
Expected Behavior :
- After saving a reclamation rule, clicking "New" on the Software Products tab opens the M2M relationship table samp_m2m_rule_product
- URL pattern: /sub/record/samp_m2m_rule_product/-1_uid_1/
- This correctly creates the many-to-many relationship between reclamation rules and software products
Actual Behavior :
- After saving a reclamation rule, clicking "New" on the Software Products tab incorrectly opens samp_sw_product table directly
- URL pattern: /sub/record/samp_sw_product/-1_uid_1/
- This bypasses the M2M relationship table entirely
Troubleshooting Performed:
- ✅ Checked UX List configuration (sys_ux_list) - only one record found for samp_sw_reclamation_rule, no Software Products tab configuration visible
- ✅ Searched UI Builder for record page configuration - no dedicated page found for samp_sw_reclamation_rule (runs under License Operations page)
- ✅ Checked System UI > Related Lists for samp_sw_reclamation_rule - no related list configurations found on either instance
- ✅ Checked System UI > Form Design - no visible difference between instances
- ✅ Searched for samp_m2m_rule_product and samp_sw_product related configurations - no configuration differences identified.
Any help would be appreciated.
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2026 09:51 AM
Hi @Ram113
1.
Navigate to Plugins: Use the application navigator to go to System Definition > Plugins.
Find the Plugin: Search for Software Asset Workspace (or the internal ID sn_sam_workspace).
Repair: Click on the plugin from the list. In the plugin details view, click the Repair.
2. Using cache.do in navigator, clear instance cache and check.