Domain separated instances encounter "Unable to execute UI Action <name>"against a record belonging to global domain - Known Error

Domain separated instances encounter "Unable to execute UI Action "against a record belonging to global domain Description Instances configured with domain separation (com.glide.domain) on versions of Rome and San Diego experience errors when attempting to execute UI Actions defined in a non-global domain on records in a global domain. Example error: Unable to execute UI Action 'XXXX' against record belonging to domain 'global' because action is defined in domain 'YYYY' .

Steps to Reproduce

This defect only affects domain-separated customers. On an OOTB instance,

Install Domain Support - "Domain Support - Domain Extensions Installer" plugin Switch to domain TOP/ACME. Go to sys_ui_action.do?sys_id=7b37cc370a0a0b34005bd7d7c7255583 Change name to 'sysverb_new_acme'. Go to 'sc_req_item' list and create a new one in ACME domain. Click 'New' from related list 'Catalog Tasks'. Actual behavior: Error shown - Unable to execute UI Action 'sysverb_new_acme' against record belonging to domain 'global' because action is defined on domain 'ACME'.

Expected behavior: New record for sc_task is created.

You can repeat the test with the following properties and return the same results:

glide.sys.domain.use_record_domain_for_data = false glide.sys.domain.use_record_domain_for_processes = false Workaround This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

The following workaround can be applied before or after upgrading instances to an affected version:

Go to sys_properties.LIST Create a new property with the following values: Name: glide.script.action_script_processor.enforce_action_for_current_domain Type: true/false Value: false Related Problem: PRB1563531