UI Actions crossing application scope

[Andrew_Shaw]

We have a custom table in the Customer Service application that inherits from Case which in turn inherits from Task.

There is an OOB UI Action on the base Task table labelled Responses which gives the support agent the opportunity to select a defined Response Template when dealing with one of these cases.

My goal is to make that same [Global] UI Action available on the form for the records in our custom table, but what I think I have learned is that because our custom table is in the Customer Service application scope it seems that the UI Action on the underlying Case/Task table does not flow through - which makes sense (once I figured out what was going on !!!!)

I have been able to effectively duplicate the underlying UI Action in the Customer Service scope and the UI Action now appears on the form for our custom table, but it occurs to me a better solution might be to expose the underlying UI Action (which effectively only allows the selection of the appropriate response template).

Is that thinking:

a) possible

b) sensible 

If neither of the above then I need a better solution !!!!!!

I suppose one option might be to make the new scoped UI Action simply invoke the Global one, but that might have its own problems. (UI Action conditions etc).

Any tips much appreciated !!!!

[Andrew_Shaw]

** Update **

A few days later this now appears not to be a problem after all !

I have made no changes and now the Responses UI Action on the Task Table is appearing as expected on our table in the custom app which extends case, and therefor Task.

Unsure why this was not apparent last week, but I believe this is a non-issue !!