I’m working on adding a “Create Change” action for "cmdb_data_management_task" in CMDB Workspace. Existing “Cancel Task” action is working and appears in the list action menu.
I traced the implementation and found it uses:
- Declarative Action Assignments
- UX Add-on Event Mappings
- UX Events
- Payload Definitions
- task_list source element
- Macroponent = Certification Instance Default
I cloned the existing “Cancel Task” setup:
- created new Declarative Action
- created UX Event ("DM_TASK_CREATE_CHANGE")
- created UX Add-on Event Mapping
- copied payload mapping
- same table / same list context / same selection behavior
However the new action still does not render in the workspace action menu even after cache clear and relogin.
Questions:
1. Is there additional UI Builder / macroponent configuration controlling which declarative actions render?
2. Are list actions filtered somewhere else beyond Declarative Action Assignments?
3. Is there a registry/provider layer for CMDB Workspace task actions?
4. Does “Certification Instance Default” macroponent require additional action registration?
Any pointers on how CMDB Workspace renders these task list actions would help.
