admin
section of your manifest file. There you can define <action-button>
elements in order to add your button, as seen as below:action
: Unique identifier for the action, can be set freely.entity
: Here you define which entity you're working on.view
: detail
or list
; to set the view the button should be added to. Currently, you can choose between detail and listing view.sw-version
header.shopware-shop-signature
it too contains the sha256 hmac of the request body, that is signed with the secret your app assigned the shop during the registration.shop-id
shop-url
timestamp
sw-context-language
sw-user-language
shopware-shop-signature
shopware-shop-signature
, which is a hash of the request's query part, signed with the shop's secret key.shopware-app-signature
containing the sha256 hmac of the whole response body signed with the app secret. If you do not need to trigger any actions, a response with an empty body is also always valid.openNewTab
action type. You need to pass the url that should be opened as the redirectUrl
property inside the payload.notification
action type. You need to pass the status
property and the content of the notification as message
property inside the payload.reload
action type with an empty payload.openModal
action type. You need to pass the url that should be opened as the iframeUrl
property and the size
property inside the payload.actionType
: The type of action the app want to be triggered, including notification
, reload
, openNewTab
, openModal
payload
: The needed data to perform the action.redirectUrl
: The url to open new tabiframeUrl
: The embedded link in modal iframestatus
: Notification status, including success
, error
, info
, warning
message
: The content of the notificationsize
: The size of the modal in openModal
type, including small
, medium
, large
, fullscreen
, default medium
expand
: The expansion of the modal in openModal
type, including true
, false
, default false
JsonResponse
to give feedback to the user in the administration.