Tranquil IT Forum

Hello,

I've noticed recently that the icons in the WAPT web console (currently version 1.7.4) have disappeared on workstations, replaced by question marks.

According to the documentation (see https://www.wapt.fr/fr/doc/wapt-create- ... n-png-file), each package should contain a PNG file that allows you to associate an icon with the package.

On the other hand, on the WAPT server, we have a /var/www/wapt/icons that contains the icons extracted from the executables.

I would therefore like to know what this directory is for, if it's still used, and if it's really necessary to extract the icons manually to include them in the package.

Sincerely,

Hello,

The web self-service will gradually disappear... some features are likely no longer functional. A native application has been developed to replace it. You will find it in your programs. More information: https://www.wapt.fr/fr/doc/wapt-usage/w ... %20service

The /var/www/wapt/icons directory is used to store the icon.png files included in your packages. When you upload your package to your server, the server extracts these files and places them in this folder. The self-service downloads the icons from your packages into this directory via an HTTP request. Yes, it is therefore necessary to include the icons in the packages in order to see them in the self-service.

Best regards,

Evan Blaudy

Thank you for your prompt response.

Regarding self-service, is it limited to the Enterprise version? I'm using console version 1.7.4.6077 and I haven't found any mention of it.

Furthermore, the new version seems to require administrators to perform a manual task where previously there was an automated one (automatic extraction of icons from .exe files). This seems like a regrettable step backward.

corriou wrote: ↑Sep 25, 2019 - 4:56 PM Thank you for your prompt reply.

Regarding self-service, is it limited to the Enterprise version? I'm using console version 1.7.4.6077 and I haven't found any trace of it.

Furthermore, the new version seems to force administrators to perform a manual task where previously there was an automated one (automatic extraction of icons from .exe files). This seems like a regrettable step backward.

No, the same self-service functionality is available in both the Community and Enterprise versions of the native client. It's a matter of operational sophistication.

In Community, self-service is all or nothing. You either allow your users access to your entire available application catalog or you deny all your users access to the catalog.

In an Enterprise environment, you will associate software packages with Active Directory (AD) security groups, and software catalogs will be restricted to members of those AD groups. Therefore, someone in accounting will not see the CAD software intended for the engineering department, and vice versa; the engineering department will not see the accounting software available to the accountants.

Regarding the second part of your comment about admins having to perform a manual task, we will need more details to provide a suitable response.

Sincerely.

Vincent

corriou wrote: ↑Sep 25, 2019 - 4:56 PM Furthermore, the new version seems to force administrators to perform a manual task where previously there was an automated one (automatic extraction of icons from .exe files). This seems to me a regrettable step backwards.

I don't understand what you're talking about; the feature for "automatically extracting icons from .exe files" never existed

sfonteneau wrote: ↑September 26, 2019 - 11:13

corriou wrote: ↑Sep 25, 2019 - 4:56 PM Furthermore, the new version seems to force administrators to perform a manual task where previously there was an automated one (automatic extraction of icons from .exe files). This seems to me a regrettable step backwards.

I don't understand what you're talking about; the feature for "automatically extracting icons from .exe files" never existed

I think some .exe files were supposed to automatically display their icon.

Hello,

Regarding the "automatic icon extraction feature from .exe files":
I was indeed mistaken. I work with the WAPT repository and my own packages. The latter do not contain icons, which is reflected in the self-service interface => resolved.

Regarding the self-service interface: choosing the executable over the web interface is fine, but I preferred the web interface. The icon size is perhaps a bit small and detracts from the aesthetics. A shame.