Community Home

HP Forum

Technologies	Topic Count	Replies	Last Post
Immersive Welcome to the Immersive developer community forum.	17	26	1 year 1 week ago by sprout.dev@hp.com
PrintOS PrintOS community discussion and support.	42	42	1 week 2 days ago by max.finger@gramps.ch
SmartStream SDKs Improve production efficiency and produce high-value applications using HP SmartStream solutions.	9	12	6 days 6 hours ago by contato@clientespelainternet.com.br
Client Management Solutions Community discussion and support for HP Client Management.	23	72	1 week 2 days ago by riturosleimura12@gmail.com
HP Client Management Script Library Community discussion and support for HP Client Management Script Library.	27	141	2 days 2 hours ago by carlos.castanheira
HP DaaS Proactive Management Support, discussion and community regarding HP DaaS Proactive Management.	6	5	-
PrintOS Composer API	1	0	4 months 3 weeks ago by nabil.gamil@click-group.com
PrintOS PrintBeat API	7	17	5 months 3 weeks ago by cstevens
PrintOS PrintBeat Jobs API	24	51	2 weeks 2 days ago by richard.ives@moo.com
PrintOS SiteFlow API	6	4	1 year 1 week ago by peter.romberg@exakta.se
Production Center REST API SDK	3	1	3 weeks 8 hours ago by cstevens
Production Pro JDF SDK	39	105	2 weeks 1 day ago by charnisch
SmartStream Production Center Product & SDKs	5	13	8 months 2 weeks ago by cstevens
PPML SDK	1	1	2 years 4 months ago by ameliawilson
PrintOS Device API	6	17	1 month 3 weeks ago by hoangmanh.nguyen
Production Center JDF SDK	1	0	3 years 6 months ago by cstevens
SmartStream Production Pro SDKs	3	5	5 months 3 weeks ago by Thiago Consales
PrintOS Box API	4	4	3 years 3 weeks ago by cstevens
Mobile Scan SDK This forum is for the purpose of discussing the Mobile Scan SDK; its uses and functionality across the iOS and Android platforms.	11	30	3 months 2 weeks ago by zeleleinspace@hotmail.com

Recent Blog Posts

HP UWP Application Pack Deployment in a Microsoft Endpoint Configuration Manager OS Deployment Task

Author : nkofahl

With the move to the DCHU driver model many of the typical tray applications have migrated to a Universal Windows Platform (UWP) application. These applications are typically installed from the Windows Store into a specific user profile. However, in environments where the Windows Store is blocked or IT needs to deploy these applications as part of a bare metal OS deployment task, a different in

Optimized Windows Power Profiles with HP System Default Settings

Author : dan.felman

Modern Standby: Why HP System Default Settings The HP System Default Settings Softpaq was developed to optimize settings and battery utilization on HP systems. HP recommends the Softpaq be installed on all supported mobile platforms, with and without Modern Standby support. According to Microsoft -

Packaging UWP drivers for deployment in MEMCM

Author : dan.felman

Installing Driver Appx packages during MEMCM/OSD 4/30/2020 The implementation of the UWP driver model by Microsoft imposes restrictions on how a complete driver package can be deployed when a PC is (re)imaged. Drivers with a control UWP application are split between the hardware-enabling driver and an appx package, typically installed with DISM. Ev

News and Events

HP Workpath SDK 1.4.1 (Rename Preview) Now Available

HP is pleased to announce availability of the HP Workpath SDK version 1.4.1 (Workpath name change preview)

As we announced in December, HP has been working to implement the name change from “HP JetAdvantage Link for Device” to “HP Workpath” throughout our ecosystem. And while not all of this work is complete, we are pleased to announce the availability of the first HP Workpath SDK package with the new naming implemented throughout, including the APIs (namespaces, types, methods, etc.) -- HP Workpath SDK v1.4.1.

This new Workpath SDK v1.4.1 is functionally equivalent to the JetAdvantage Link or Device SDK v1.4.0 in every way – only the names have changed. It is also backward compatible with existing device firmware. But due to the API name changes, you will need to make the corresponding name changes in your app code in order to use it.

All future SDK releases will use the new Workpath naming convention, so you will need to make this change to your app eventually. So why wait? By downloading the new Workpath SDK 1.4.1 and rebuilding your app now, you will avoid this additional step when you upgrade to an even newer SDK to access additional features in the future.

The HP Workpath SDK v1.4.1 is available on the Downloads page.

Remote App Configuration Now Available for All HP Workpath Apps

HP is pleased to announce that Remote App Configuration is now available for all HP Workpath apps.

HP has been working hard to enhance app deployment through HP Command Center (HPCC). A few months ago, we introduced the ability to create and deploy app configurations remotely from within HPCC for several HP developed apps. We have used the intervening time to test and improve that feature under production conditions.

HP is pleased to announce that we are now making Remote App Configuration available for all HP Workpath apps. With a little work on your part, HPCC users will be able to create a unique configuration for a customer and deploy it to your app installed on that customers’ devices -- all through HPCC.

For details, please visit the new Remote Configuration page on the developer portal.

Oreo is here! FutureSmart firmware and Link for Device SDK 1.4 Now Available

HP is pleased to announce the release of Oreo and version 1.4 of the Link for Device SDK.

In June of last year at the 2019 HP JetAdvantage Partner Conference, HP announced our intention to upgrade the HP JetAdvantage Link for Device platform to API version 26 (a.k.a. Oreo) within a year. We are happy to announce that the implementation is now complete, and is included in the latest FutureSmart Bundle (4.10). Thank you to those of you who participated in the Oreo Beta program, helping us ensure the quality of the platform.

To enable all the new features in API version 26, we are also pleased to announce the release of the JetAdvantage Link for Device SDK version 1.4 (associated with the release of FutureSmart Bundle 4.10 device firmware).

Link for Device SDK and Simulator (version 1.4):

Please note: A device firmware upgrade to FutureSmart Bundle 4.10 is required to use this SDK. The firmware will be available on hp.com soon. In the meantime, the firmware has been made temporarily available for download from the SDK Download page.

Download the new SDK and Simulator from the Download page.

Major new features of this version include:

Android API Version 26 (Oreo)

Other notable changes in this release include:

HPKTool Change

It is now possible to package a Home Screen (Kiosk) App that also uses Accessories

Restrictions:

[MASSSTORAGE] Size of getFreeSpace() and getTotalSpace() is not correct.

Tips for making sure your apps are “Oreo ready”:

Review the API changes introduced between Kitkat (4.4) and Oreo (8.0), to identify any deprecated APIs you might be using:
- 4.4. to 5.0 (https://developer.android.com/about/versions/android-5.0-changes)
- 5.0 to 6.0 (https://developer.android.com/about/versions/marshmallow/android-6.0-changes)
- 6.0 to 7.0 (https://developer.android.com/about/versions/nougat/android-7.0-changes)
- 7.0 to 8.0 (https://developer.android.com/about/versions/oreo/android-8.0-changes)
Due to a change in permissions, PrintFromMassStorageBuilder cannot be used to print files from a USB thumb drive. Instead, you must use PrintFromUSBBuilder.
UI anomalies have been observed when id tags are used within the include tag in an xml layout file (<include android:id=”@+id/my_id” />). Remove ids from your xml layout files.
UI anomalies have been observed when loading scalable vector graphics (svg) images. Use ContextCompat/AppCompatResources to load svg images from resources. Also ensure vectorDrawables.useSupportLibrary = true is added under defaultConfig in the gradle file.
UI anomalies have been observed on devices with higher resolution displays (1024x768). Include resources appropriate for a display density of mdpi/160dpi (res/drawable-mdpi).

For any anomalies found in your app, first check your usage of the APIs. Most of the anomalies found during Beta were actually due to the app’s incorrect use of the APIs or reliance on deprecated APIs.