Web BrowserNX

4 - I'm occassionally getting an "Error occurred.[Validate]" from the simulator.  I assume on the simulator that won't be related to the access token (and the error isn't the same as the validate_failure that i get on the actual device).  I did a search through the doc and didn't see that one mentioned.What does that error mean on the simulator?

3 - On my first try at getting the device to scan, i'm getting a dapi:scanner.error.no_indispensible_param on the simulator.  Is there a way to get additional information about what parameter it doesn't like?

We have a Product ID of 34088704 for our Encapture Ricoh SDKJ Java client.  Are we supposed to use that for our Web Browser NX token request or is there a mechanism for applying for an additional Product ID.

I need to get this ticket assigned to Charles.

The RightFax Ricoh connector is having an issue detecting A4 devices.

Thanks,

Mike Stover

This request is specifically for Charles Coudsi,

You sent email to Windy Hensen (who is working with you for certification) requesting that I open an incident report so you can create an access token for certification of our product.

The development token is in a file named "app-ricoh.min.js" :

The development access toke is:

tGzJ8ar/YsS7SABEn+I3rHxePRzphvGZjGt+Sqg/jhvPKKK2En6HPp256dt8IXyZp/epDlYdk/UqVO/9tt87Ko+GIjy7K070G/EbwRuz+DJ19e5avkFWgvyM5juK27MX1CYIn7P3t1yYSWB70OvVmWoBro96xUgw+61CuOA/elyvvrxqnPFLO5UN3HMFHAXfszxdT+8B3tf5MTra6ekLKeNSB5tPQ8ivUnNEukmGcAI=

It is my understanding (based on conversations that I had with Alex Reyes) that you can generate a new token and then replace our dev token with your new token.

Also, if it helps, here is the information that was used to create the limited token that we have been using for development of the product.

Product ID: 1979711509

Vendor Name: OpenText

Application Type: Web Application (Web BrowserNX)

Application Name: RightFax Connector for Ricoh

URL Location: /rightfax

Target Version: List the SmartSDK version. Example 1.04

MFP Serial number(s):

MP C406Z s/n G135PB00089

MP C3003 s/n E153M310012

Please let me know if there is anything else I can do to help,

Dale Hunt

Software Engineer IV

Open Text

dhunt@opentext.com

Hello,

We have shipped two VMs with RightFax 16 EP2 per the Compatibility Logo Program directions.

We intend to have Ricoh test and certify the following connectors.

1. The legacy SDK/J connector for RightFax on devices 7.x-12.x

2. A new WebBrowswerNX connector for RightFax on SmartPanel devices.

Thanks,

Mike

We just finished up our current Encapture release and are planning our next one (which will include SmartSDK support).

Previously, there was a question about the future of Web Browser NX and I want to verify (before we start any development) that it is still a supported choice for new development going forward.

Thank you,

Scott

To whom it may concern,

We recently requested a new access token for the device we have been developing against. The new token was requested because we have multiple urls that our app may be run from.

Now it seems, the old access token that we were using before is not valid, and the new token that we requested is not valid either. Not sure why, but my question is, why is the old token that was working before now invalid.

Is that something that you guys do as part of the process of creating development tokens or are we just making a mistake that we haven't uncovered yet?

Thanks in advance for your response,

Dale Hunt

Software Engineer IV

OpenText