Administrative

Hi Mark,

I uploaded the production signed client in the ticket. 

Best Regards,

Paul

Hi,

We have potential customer that may be closing a contract with us but they are asking a "proof" that we (NDD) are "approved" or "certified" from Ricoh to be creating applications for Ricoh Devices.

What can we use to show them that we are an approved company from Ricoh perspective? There is any document that we can use?

Best regards,

Elison.

Compatibility Testing Submission Generated by Support System ...
 

Hi,

I am not sure if this is the right way to ask, but we need to update one user and create new NDD users to access ricoh-ridp.com.

guilherme.santos@ndd.tech (this is existing user, we need to update the previous with the new domain)

elison.coelho@ndd.tech (new)

spartans@ndd.tech (new)

Best regards,

Matheus.

Compatibility Testing Submission Generated by Support System ...
 

Compatibility Testing Submission Generated by Support System ...
 

Hi,

We are facing the following exception while installing our application after the update of the RXOP libraries with v3.8.7.  

ricoh.rxop.rxcommon.RxopException: -- install -- ERR_APP_INSTALL_ERROR :: install failed. :: ERR_JAR_HASH :: install failed. ::
        at ricoh.rxop.rxinst.RicohJavaDevice.c(RicohJavaDevice.java)
        at ricoh.rxop.rxinst.RicohJavaDevice.a(RicohJavaDevice.java)
        at ricoh.rxop.rxinst.RicohJavaDevice.install(RicohJavaDevice.java)
        at ricoh.rxop.rxinst.RicohJavaDevice.install(RicohJavaDevice.java)
        at com.pharos.ricoh.deployment.RicohDeployer.run(RicohDeployer.java:110)
        at java.lang.Thread.run(Unknown Source)
Caused by: ricoh.rxop.rxinst.g: ERR_APP_INSTALL_ERROR :: install failed. :: ERR_JAR_HASH :: install failed. ::
        at ricoh.rxop.rxinst.RicohJavaDevice.a(RicohJavaDevice.java)
        ... 6 more

Previously we suspect that it could be because we were using an unsigned bundle after the RXOP libraries update. So, we requested for maintenance build for the Ricoh Pharos iMFP for Ricoh.

 MAINTENANCE SIGNATURE FOR IMFP 1.5.11 

INCIDENT ID#: 4447 

and tried that certified bundles still faced the same issue.

could you please look into this and let us know if anything needs from our end. 

Thanks 

Nick

Compatibility Testing Submission Generated by Support System ...
 

When incidents are closed the URL rewrite stuff seems to regenerate the random part of the URL. The notification occurs before this, though and has a reference to the old and now missing URL, leading ot a 404 if you visit a bookmarked URL or the one in the notification.

Ideally the random part is not regenerated. Or we delay sending the notification until the new one is created. Or maybe we can use the "changed" field if it has been changed when the Rule is being processed?