Get started
You have a licence key. This is the shortest path from there to somebody using a screen — about ten minutes, or an afternoon if the engine is involved.
On this page
What you need#
- Admin access to the FSA tenant, specifically the permission to add extensions under Foundational Services → Extensions.
- Your licence key — the long string we emailed you. If you do not have one, start a trial.
- Nothing else. There is no server to stand up, unless you bought something that reads live S/4 data — see step 4.
1 — Work out what you bought#
Your licence carries one entitlement per thing you can use. Two shapes exist and they install differently:
- EasyScreenViewer — the studio your team builds screens in. One install, and the licence decides which of the four screen types appear.
- The ready-made products — Warranty Checker, Stock Checker and the rest. Each has its own install link and its own entitlement.
You can have either without the other. If you are not sure what is on your key, the licence page explains how to read it, and we can look it up for you.
2 — Install it#
Every product installs the same way: one URL pasted into FSA's Add Extension dialog, then your licence key. The install page has the exact steps and the link for each product.
3 — Check it opened#
Open the extension from the FSA Shell. You should see the product, or — in the studio — your screen list and the admin tab, if your role grants it.
If you get a blocking screen instead, it names the reason. Take that wording to troubleshooting, where each state has its own fix.
4 — If it reads S/4 data#
3 of our products, and any screen you bind to S/4, need the connectivity engine running on your own SAP BTP subaccount. It is a single service you deploy once; everything then goes through it.
This is the part that takes longer than ten minutes, because it involves your landscape — see deploying the engine. Products that work against FSA alone need none of it.
Where to go next#
- Building your own screens: the designer.
- Putting a screen on a record page: publishing a screen.
- Getting it onto phones: mobile setup.
- Counting users: seats.