Chromebook Inventory Extension White Labeling (EOL)

What

ItWhite was previously possible to customize the user-visible information forlabeling the FileWave Chromebook Inventory Extension.Extension Itis wasno possiblelonger toavailable. customizeThe icons,steps namebelow andrecord description.the Thisprevious involved:support-assisted process for historical reference; do not use them for a new deployment.

1. DownloadAdministrators downloaded the historical chromebook-whiteboxing.zip package and modifymodified theits dataicon insideand (adding a new icon, description, etc.)metadata.
2. CreateThey opened a support Ticketticket titled "Chromebook Custom Extension"Extension and attachattached your newthe modified ZipZIP Filefile.
3. WaitAfter tillSupport we send back your "whiteboxed" extension then continue toreturned the "Howcustomized toextension, publish"they sectionpublished belowit through the Chrome Web Store developer dashboard.

When/WhyStatus

AsFileWave partremoved ofcustom anpublishing overhaul ofwhen the extension moved to leveragenewer newChrome APIsAPIs. The supported path is the standard FileWave inventory extension.

Current workflow

FileWave 15.4 and enhancementslater do not support this customization. Deploy the ability to publish it with customizations is removed for now. If this returns in a future version then this article will be updated.

How

This customization is not possible in FileWave 15.4+ and this article remains to make customers aware of the change. You would use thestandard inventory extension asby outlined infollowing Chromebook Client Pre-Requisites rather than this customized method..

Related Content

• Chromebook Client Pre-Requisites

DiggingHistorical Deeperprocess details

ThisThe wasremaining steps and screenshots document the actualretired processpublishing to publish in the past.process.

The ZIP file contained:

• icon_.png (so far we have 19, 38, 128 as size)
• data.json

data.json

{
  "name"``: "<NAME_HERE>"``,
  "description"``: "<DESCRIPTION_HERE>"
}

HowHistorical Chrome Web Store publishing steps

After FileWave returned the customized extension, administrators used the following Chrome Web Store steps to publish a "whiteboxed" version of the extensions

Once you get the "whiteboxed" version of your extension, you haveit to follow some steps to make it available to yourtheir organization.

1. Login/Create an account to Google Developer Dashboard

2. Click on the "Add New Item" button
   

3. Upload the ZIP file
   

4. Edit/add Additional Info
   

5. Publish the extension