SDK/J

Hello

Pleaes help to sign this maintenance version (Attached)

This version bases on the full signed version Kofax_KofaxMFPClient-5.0.0.850production2018-6-7 with new features  following:

- 1165960 Ability to activate or deactivate the Auto-send function in the Ricoh MFP clients for Java and Android
8989 - Ceská pojištovna, a.s. - Ability to activate or deactivate the Auto-send function in the Ricoh MFP clients for Java and Android
Case Elevation - R&D - KFS {24077953 - inactivity timeout and auto-send function can not be configured with Ricoh Android client}

- 1175576 [Ricoh MFPs] Inconsistent behavior with Scan Status when the client timeout occurs.

Please feel free to inform me if you have any questions.

Thank you very much

Ngoc

Hi

Our SDK/J application do a scan job and it happens paper jam/or cover open, when user resolved paper jam/or Cover open, the device screen will go back to our SDK/J app screen, we would like to raise a method after resolved scan error.

How does SDK/J app detect the event after resolved paper jam/or cover open?

Can you give me a example for it?

Thank you

Ngoc

Hello

We have a customer, they use Ricoh devices with none HDD.

They have used applications and the JavaTM on a SDCard on slot 2 (Java SDcard), and now it is full.

They inserted another SDcard (App SDCard) to the slot 1, and would like to deploy Kofax SDK/J app to it .

The dalp file is using : <install mode="manual" destination="sdcard1" workDir="sdcard" /.  Deploy the App via WIM, destination is "SDCard on the slot 1".

The problem that, After deployed Kofax SDK/J app, the processing location (WorkingDir) is still located on Java SDCard on the slot 2, although the Startup Location is on AppSDCard. (please see the attached)

They would like both Startup Location and Processing Location are same located on the App SDcard.

How to use both Startup Location and Processing location on the App SDcard?

Thank you

Ngoc

Hi,

So, in our SDKJ application, we have an issue with a certificate that is embedded in the zip file that expired.  I thought I might need to go through the full certification process just for that, but emailed with Joe and he said that it may be possible to just update the certificate.  He said that I should be an incident in to check with you guys.

After thinking about that more last night, since  no code change is needed and the jar file is the thing that is actually signed, I believe that I can just repackage all the original certified jars with an updated certificate [certs file] and DALP file, changed only to reflect a version update so we can differentiate them... 1.4.6.1 instead of 1.4.6).

I've done this, internally only, just to see if it would work and I think that functions properly, but I want to make sure that it is ok (and not violating agreements, etc) before I do anything else with it, or if there is anything else that you feel that I should do (or do instead).

Also, if you want me to attach the updated zip or the certs/dalp or anything to the case, so you have a record of it (or if you want to actually create it), let me know.

I'm also available for a phone call if that would be more helpful.

Thank you,

Scott

214-621-3751

Hey,

We're looking at submitting an updated SDKJ Xlet (because a certificate that is embedded in it expired).
I remember that there was a list of tests to run (and the Quick Start Summary in the Compatibility Testing Program document refers to an Xlet and/or Servlet Type Application Evaluation Criteria Specification (which I think is what that was called), but I am unable to find that on the RIDP portal site.

Can you let me know where that is on the site (so I can update our documentation on where to get the latest copy from) and so I can use that now?

Thanks,

Scott

Hi there,

I'm trying to figure out where I can find the password for the keystore generated for the SDK/J. We seem to have lost the information and I can't find it on the RIDP site.

Hello,

Customer has enabled only TLSv1.2 on the server and now when the user selects any XLet buttons, it displays "Connection Reset" error on the panel.  If they re-enable TLSv1.0, then it works fine.

Steps to reproduce:

1) Xlet application is configured to use HTTPS to communicate with teh backend server.
2. Disable all the protocols except TLS 1.2 (you can use IISCRYPTO from https://www.nartac.com/Products/IISCrypto/ or import the customer's SCHANNEL reg file into your 2012 R2 Server)
3. On the Device's Web Image Monitor go to Configuration | SSL / TLS and make sure TLS 1.2 is the only protocol enabled. 
4. Reboot the device and server
5. Go to the device and try to use an Xlet button and you should see "Connection Reset" on the panel.

Please let me know if you need more information.

Regards

Niranjini

Hi,  

We would like to get Maintenance Signature of our nddPrintClient application;  It is applied to 7x, 10x,  11x and 12x. Display supported are uWVGA, WVGA. 

The changes affect just the jar file nddPrintClientRicoh.jar;

In the classes WindowDeleteConfirmation and Releaser.

WindowDeleteConfirmation : 

 Releaser.getInstance().clearAndInitializeAfterDelete(); 

Releaser: 

Sorry to bug you again.

I tried to generate a development signature and it kept failing because i didn't have any product id's listed.

I went to the create product id area to see if there was a way to register it and ended up requesting a new one accidentally.

Is there a way to put our correct product ID (34088704) in the system, so I can generate a signature for that?

Thanks,

Scott