PxPlus, like PHP, runs server side thus the answer is no, you cannot directly access JavaScript variables from PxPlus.

Below is a link to the same question asked about PHP where they discuss why server side processing, like PxPlus and PHP, cannot directly access JavaScript variables.

https://stackoverflow.com/questions/2379224/how-can-i-use-a-javascript-variable-as-a-php-variable

Sir,

1) Is it possible to access pxplus variable in java script

2) java script variables in pxplus

We can do it php.  In php we can use php variable in java script and similarly we can use java script variables in Php.

Is there any such options in PXPLUS
Just give me small example

J.SURIAKUMAR

Thank you Mike, I will do that. But just to make sure I understand, the version of PXPlus I'm on, 12.5, will not work with TLS1.2 or TLS1.3 regardless of what version of openSSL I'm on. Is that correct?
 

While upgrading your PxPlus would likely be your best solution, you might want to consider simply using 'curl' (or 'wget') to send your requests, especially since you said curl can connect.

Obviously it would require some coding changes but invoking curl to submit the request wouldn't be all that difficult and would remove the need to update your PxPlus to a version that supports TLS1.2 or TLS1.3.

Keep up to date with what's happening at PVX Plus.  Please see our latest newsletter.

December 2025 Newsletter

Happy Holidays from all of us at PVX Plus Technologies.

I have a program that has been working for several years that communicates to a Woo Commerce website API. The other day it stopped working. When opening the port I get an error 13. MSG(-1) says Unable to connect securely (err/ret=0/0). I talked to the Woo Commerce people and they told me they only support TLS1.2 and 1.3. The said the change happened a while ago, but I'm not sure I'm buying that. Any way I'm on an old version of PXPLus 12.5. And I'm running on AIX. It's also an Infor product so upgrading the PXPLus version is not a simple thing. After searching this board for a while it looks like by updating the OpenSSL on my server to 1.1.1 PXPLus would be able to do TLS 1.2. First question is, am I understanding that correctly? So I had my OS guy update the OpenSSL. Now I can connect to the Website using Curl. But I have the same issue in PXPlus. Also looking around it looks as though even after updating the openSSL, I have an old version of libssl.so. It seems as though AIX uses something called libssl.a which does have the newer date. I'm not sure which one PXPlus uses. Anyway I'm looking for some guidance on a way to get my old version of PXPlus use TLS 1.2 or 1.3 or any other reason I might be getting this error.

Subject: Requirement for Code Scanning Tool for PXPlus Application

Dear Team,

I am currently serving as a DevOps Engineer within our organization, where we utilize the PXPlus application as our core solution. We have received a security request to conduct a code scan of the PXPlus application. After consulting with our Azure DevOps support team, it has been confirmed that the PXPlus application is not compatible with Azure DevOps code scanning functionalities.

I will be exploring alternative tools that can support code scanning for PXPlus. I intend to recommend suitable options to our security team for acquiring the appropriate scanning tools.

Thank you for your attention to this matter.

Best regards, 
Vinoth Subbiah

James, I tried it with numerical values, but it still doesn't work.

Mike, I tried passing the object from exportOptions and it's still not working. I think your example uses a different version of Crystal Reports; we're using 8.5. As mentioned before, we used the same logic in PowerShell and it works fine, so we think it should work in pxplus.

PowerShell code Works:
$app = New-Object -ComObject CrystalRuntime.Application
$report = $app.OpenReport("C:\temp\customers.rpt")
$report.EnableParameterPrompting = $false
$report.DisplayProgressDialog = $false
$report.DiscardSavedData() | Out-Null
$exportOpts = $report.ExportOptions
$exportOpts.DestinationType = 1
$exportOpts.FormatType = 31
$exportOpts.DiskFileName = "C:\temp\customers.pdf"
$exportOpts.PDFExportAllPages = $true
$report.Export($false)
Pxplus code Fails:
DEF OBJECT CR_APP,"CrystalRuntime.Application"
 LET REPORT=CR_APP'OPENREPORT("C:\temp\customers.rpt")
 LET REPORT'ENABLEPARAMETERPROMPTING=0
 LET REPORT'DISPLAYPROGRESSDIALOG=0
 LET DS=REPORT'DISCARDSAVEDDATA()
 LET EXPORTOPTS=REPORT'EXPORTOPTIONS ! Opts Object EXPORTOPTS
 LET EXPORTOPTS'DESTINATIONTYPE=1
 LET EXPORTOPTS'FORMATTYPE=31 ! pdf
 LET EXPORTOPTS'PDFEXPORTALLPAGES=-1
 LET EXPORTOPTS'DISKFILENAME$="C:\temp\customers.pdf"
 REPORT'EXPORT(0)

I suspect your call to the export method is incorrect.

I did a search on the web and on this page found an example that appears to show the Export method wants the exportOptions to be passed, not a boolean.

    Dim wordExportOptions As New ExportOptions()
    wordExportOptions.ExportDestinationType = ExportDestinationType.DiskFile
    wordExportOptions.ExportDestinationOptions = dfDestinationOptions
    wordExportOptions.ExportFormatType = ExportFormatType.WordForWindows
    wordExportOptions.ExportFormatOptions = Nothing
    
    rd.Export(wordExportOptions)

Have you tried starting with numeric values to convert to Boolean? Would this work?

DEF OBJECT v,"*VARIANT"
v'val=1
v'type$="B"
PRINT v'val
-1
v'val=0
v'type$="B"
PRINT v'val
0