You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Akeneo is responsible for the UI extensions framework itself, including the APIs and administrative interface. We provide support for these components. Your organization or your integrator is responsible for any custom code, iframes, or other custom development built within the UI extensions. Support for this custom code falls to your organization or integrator, not Akeneo.
4
+
5
+
### How can I add a new UI extension to my PIM?
6
+
Adding a new extension to your organization is easy! Just follow the steps in [this guide](https://api.akeneo.com/extensions/ui-extensions.html#getting-started).
7
+
8
+
### The UI extensions entry isn't showing up in my PIM. Could you help me understand why?
9
+
If you don't see the UI extensions entry in your PIM, it's likely due to permission settings. [This guide](https://api.akeneo.com/extensions/ui-extensions.html#authorization) will help you check and activate the necessary permissions.
10
+
11
+
### I'd like to see my extension in a position that isn't currently available. What can I do?
12
+
Currently, UI extension placements are limited to those defined by Akeneo. However, we highly value your feedback! Please contact your Customer Success Manager or our Support team to share your specific placement needs. This will help us understand your use case and consider it for future development.
Extension position determines where your extension appears within the Akeneo PIM interface. You can select from a variety of available positions, which vary depending on the specific extension type.
6
+
7
+
**Key Concepts:**
8
+
9
+
***Position Options:** Each extension type offers a set of predefined positions. These positions control the location of your extension's interface elements.
10
+
***Contextual Relevance:** Position options are designed to align with the functionality of each extension type, ensuring a seamless user experience.
11
+
12
+
**Best Practices:**
13
+
14
+
* Choose a position that aligns with the extension's intended functionality and user workflow.
15
+
* Review the available position options for each extension type to ensure optimal integration.
16
+
* Consider the impact of the position on the overall user experience within the PIM.
Copy file name to clipboardExpand all lines: content/extensions/ui-extensions.md
+7-81Lines changed: 7 additions & 81 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -494,75 +494,6 @@ Examples :
494
494
}
495
495
```
496
496
497
-
## Positions
498
-
499
-
**Extension Positions**
500
-
501
-
Extension position determines where your extension appears within the Akeneo PIM interface. You can select from a variety of available positions, which vary depending on the specific extension type.
502
-
503
-
**Key Concepts:**
504
-
505
-
***Position Options:** Each extension type offers a set of predefined positions. These positions control the location of your extension's interface elements.
506
-
***Contextual Relevance:** Position options are designed to align with the functionality of each extension type, ensuring a seamless user experience.
507
-
508
-
**Best Practices:**
509
-
510
-
* Choose a position that aligns with the extension's intended functionality and user workflow.
511
-
* Review the available position options for each extension type to ensure optimal integration.
512
-
* Consider the impact of the position on the overall user experience within the PIM.
Several choices are offered to deep dive into our API, to discover all the endpoints, and their request/response schema:
591
527
592
528
- You can <ahref="https://api.akeneo.com/api-reference-index.html#UIExtensions"target="_blank">consult this static documentation</a>
593
529
- Discover it thanks to <ahref="https://api.akeneo.com/files/Akeneo%20PIM%20API.postman_collection.json"target="_blank">the postman collection</a> (see the [Postman section](https://api.akeneo.com/extensions/ui-extensions.html#using-postman))
594
530
595
-
## FAQ
596
-
### Who is responsible for UI extensions?
597
-
Akeneo is responsible for the UI extensions framework itself, including the APIs and administrative interface. We provide support for these components. Your organization or your integrator is responsible for any custom code, iframes, or other custom development built within the UI extensions. Support for this custom code falls to your organization or integrator, not Akeneo.
598
-
599
-
### How can I add a new UI extension to my PIM?
600
-
Adding a new extension to your organization is easy! Just follow the steps in [this guide](https://api.akeneo.com/extensions/ui-extensions.html#getting-started).
601
-
602
-
### The UI extensions entry isn't showing up in my PIM. Could you help me understand why?
603
-
If you don't see the UI extensions entry in your PIM, it's likely due to permission settings. [This guide](https://api.akeneo.com/extensions/ui-extensions.html#authorization) will help you check and activate the necessary permissions.
604
-
605
-
### I'd like to see my extension in a position that isn't currently available. What can I do?
606
-
Currently, UI extension placements are limited to those defined by Akeneo. However, we highly value your feedback! Please contact your Customer Success Manager or our Support team to share your specific placement needs. This will help us understand your use case and consider it for future development.
531
+
::: panel-link UI extensions available positions [Next](/extensions/positions.html)
0 commit comments