Robopack settings

1 Where to find it

Open Settings in the sidebar and click Configuration. In the list on the left, open the ROBOPACK group and click Robopack. The group is only there when your licence includes the Robopack module. Like every setting, the changes are stored when you click Save Settings (see Configuration).

2 The settings

Setting	What it does	Default
Default Deployment Template:	The deployment template the download wizard uses when it opens. With a default, clicking an application shows the one-screen summary; without one, the full six steps open. It is the same setting as the Default Template option inside a template — ticking that option changes this list, and the reverse. Choose “ - Select one - ” for no default.	None
Default Robopack Script Template:	The packaging script template Robopack uses when it builds a package for you. The list is read from your Robopack account, so it is empty until the API URL and key work; an entry looks like Default (PSADT 4.1.8). The template you choose is sent to Robopack with every import. Leave “ - Select one - ” to let Robopack use its own default.	None
Robopack API Url:	The address of the Robopack API. Change it only if Robopack has given you a different address.	`https://api.robopack.com/`
Robopack API Key:	The key from your Robopack account that identifies your organisation. Without a URL and a key the module does nothing — the service does not check for new versions, and downloads do not start. The key is a secret: only people who may open Settings should see this page.	Empty
Application Detector Enabled: tick box Enable Application Detection	Lets SoftwareCentral compare the applications found on your devices with the Robopack catalogue, to find software that is installed but not managed. The result is shown in Radar. The Windows service runs the scan when it starts and then every 6 hours; it needs a working API URL and key as well.	Off
Robopack Package Share:	The folder (UNC path) where software downloaded from Robopack is stored, instead of the site’s normal package share. Leave it empty to use the normal share. The account running the SoftwareCentral service needs write access, and SCCM needs read access to distribute the content. A separate share keeps Robopack’s many versions away from your hand-made packages.	Empty
Patch Flow versions to keep:	How many versions a Patch Flow keeps; older ones are deleted. 0 to 100. See below.	0 (keep all)

Set the connection first The two template lists, the catalogue, Radar and the automatic version check all depend on the API URL and key. Enter and save them before anything else, then come back for the rest.

3 Patch Flow versions to keep

Every new version a Patch Flow imports adds an application, source files and (in Intune) groups. This setting limits how many of those are kept.

The versions are counted separately for every place they were imported to: a flow that imports to SCCM and to two Intune tenants keeps the chosen number of versions in SCCM and in each tenant.
When a new version has been imported, the oldest versions beyond the number are deleted together with their application, their source files and the Intune groups that belong to them. A group that the versions you keep are also assigned to is not deleted.
Only versions that were imported successfully are counted. Failed imports older than the oldest version you keep are cleaned up with them.
Never deleted: the version that was just imported, the version marked as the newest, and any version that is still being imported.
Only flows that are enabled clean up. With 0 nothing is ever deleted.
If an old version cannot be deleted completely, it is tried again after the next import, and a warning is written to the log.

Deleted versions cannot be brought back The applications are removed from SCCM and Intune. If devices or deployments still use an old version, they lose it. Keep at least 2, so the previous version is there if the newest one has to be abandoned.

4 Settings that are not on this page

Three more settings change how Robopack behaves. Two of them have no switch in Settings at all; one lives under Interface Settings.

Setting	What it does	Where it is set
Default only show Patch Flows	When ticked, the Patch Flow Manager of the full edition opens with Have Patch Flow already ticked, so it lists only the applications that have a flow. It does not change the Flows view of Application Manager Only, which always shows only flows.	Settings › SoftwareCentral › Interface Settings, row Application Manager: Default only show applications with Patch Flows.
Use the Patch Flow name as the application name	When on, an application that a flow imports is created in SCCM and Intune as <Patch Flow name> <version> instead of <Robopack product name> <version>. In SCCM the application’s collection name follows the same name. It only applies to flows that are enabled, and to applications imported while the setting is on. Use it when your naming standard differs from the vendor’s product name — name the flow what the application should be called. Applications imported without a flow keep the product name.	No switch in Settings. The configuration value is `Robopack_UsePatchFLowNameAsAppName` (`true` or `false`); ask SoftwareCentral support to set it.
Force TLS 1.2 for Robopack	Makes SoftwareCentral use TLS 1.2 when it connects to Robopack. Turn it on only if the connection to Robopack fails with a secure-channel or TLS error on a server whose defaults do not allow TLS 1.2 — for example when the Robopack catalogue stays empty and the SoftwareCentral log shows a secure-channel (TLS) error for `api.robopack.com` although the address and key are right. It applies to all outgoing secure connections of that SoftwareCentral process, not only to Robopack.	No switch in Settings. The configuration value is `Robopack_ForceTLS12InRobopack` (`true` or `false`); ask SoftwareCentral support to set it.

Name the flow before you rely on the naming setting With Use the Patch Flow name as the application name on, the flow name is what your users see in the shop and in Intune. Choose it as carefully as you would an application name, and do not rename an enabled flow lightly: later versions are then created under the new name.

5 The same connection in the Setup Guide

The Setup Guide has a Robopack card with the same Robopack API URL and Robopack API key fields and a Test connection button that saves them and asks Robopack for your script templates. Use it the first time; use this page afterwards. A green result is a first check only: confirm that the key works by opening the Robopack view (the catalogue must list applications) and that Default Robopack Script Template above offers a list.

6 Best practice

Enter the API Url and the API Key first. Without both, the module is not configured and the check for new versions does not run.
Leave Patch Flow versions to keep at 0 unless you want old versions removed. At 0 nothing is ever deleted. The value can be 0 to 100.
Only enabled Patch Flows clean up. A disabled flow never deletes old versions.
The newest version is never deleted. The version that was just imported, the version marked as the newest, and a version that is still being imported are always kept.
Set a Robopack Package Share only when you want downloads in their own folder. Software downloaded from Robopack is then stored there instead of in the site’s package share.

7 Troubleshooting

Symptom	Cause	What to do
“RoboPack address or API key is missing.” is shown in the Setup Guide.	The Robopack API Url or the Robopack API Key is empty.	Enter both, click Save Settings, and use Test connection in the Setup Guide.
No new versions are found. The log says: “The Robopack integration is not configured. The service does not check for new versions until a Robopack address and API key are configured.”	The URL or the key is missing, as above.	Enter both and save. The service checks the settings again every 30 minutes, so it starts on its own without a restart.
The template lists stay empty.	The URL or the key does not work, so Robopack returns no templates.	Check the URL and the key. Then use Test connection in the Setup Guide.
Application detection finds nothing.	Enable Application Detection is not ticked, or the API URL and key are missing. The scan runs when the service starts and then every 6 hours.	Tick Enable Application Detection, click Save Settings, and make sure the URL and key are set.
The log warns: “could not be deleted completely. They are tried again after the next import.”	Deleting an old version of a Patch Flow failed for at least one application.	Read the messages written above that warning in the log. The cleanup runs again after the next import.