I have added a property and configured it as an Actionable Button, and I have also provided a Local Action ID without any visibility condition. However, when attempting to create a case from the Interaction Portal, the button is not visible on the form.
Additionally, upon reviewing the metadata, I noticed that the Local Action ID starts with @L, which appears to reference a label rather than a local action.
Could you please help me understand the correct way to configure an actionable button and associate a local action with it?
You are also trying to use this in Pega Customer Service, inside and Interaction case?
Could you share some of the configuration, where have you done this in the Interaction (which View) and how is the component configured? Personally, I can’t say I’ve seen anyone use this at an interaction level, you may hit some limitations there as an Interaction is a very specific framework case, it doesn’t work like a regular pega Case Type.
We had a similar requirement to create new work when an interaction was resolved. Instead of using a DX component button, we implemented it via a local action. This approach is easier to maintain, avoids DX dependency, and provides required flexibility.
@Aditi Mehta thanks and this is the right approach! Only in highly exceptional cases we should use DX components. If you ‘need’ a button you can always use promoted actions, you can enable promoted actions in your case type full case view: Pegasystems Documentation