I just tried it and the begin directive does not clear the env vars set via def env() in my test

->def env("pxplus_var")="Hello"
->?env("pxplus_var")
Hello
->begin
->?env("pxplus_var")
Hello

Looking at the code I can also confirm it can't.

Maybe something else is happening that is starting a new process?

Any insights?

Thank you Devon.

Hi Jerry,

Once basic authentication is turned off you will need to use OAuth2 to authenticate. You will get a error from the server otherwise.

PxPlus and *web/email support OAuth2 authentication as of PxPlus 2025 (v22).

Check out the doc here there are several examples at the bottom on how to do this.

Hi All,

So I had asked about this back in 2022 (see below). If you search for OAUTH you will see it (in the forum).  We are currently exploring options but I want to confirm with anyone. If Microsoft does go forward with this time line will *web\email basically stop working for anyone relaying emails thru Office 365?

Thanks,

Jerry

Microsoft has updated its timeline for retiring Basic Authentication (username/password) for SMTP AUTH in Exchange Online. While initial deadlines were earlier, the new schedule sees Basic Auth disabled by default for existing tenants at the end of December 2026. New tenants will have it disabled starting in 2027.

We're looking at the DEF ENV directive to set some things up as we start our application. Doing some very preliminary tests, it seems as though the BEGIN directive clears out anything that had been set. I thought this was setting the Windows Environment variables for the session, which I would think would be session-permanent.
Is BEGIN supposed to clear these out?

The issue is with the FedEx sandbox.  It is very particular concerning sequence of JSON as well as options submitted.

Quote from: Jane Raymond on April 17, 2026, 12:11:41 PMIf it's just one user, it could be something in their query user profile, i.e. something in the options they have set for themselves in that particular query. You can see what options are set using the Query Profile Information Maintenance utility, which you can access through the Nomads Utilities menu, or through the IDE Graphical Application Builder > Utilities menu.

Enter the directory and library where the query is located, the query that is affected and choose the User. This will display the information that has been saved for the user. If there is anything listed under Info Type it may be causing the issue, so you select it and delete it and re-run the query to see if that was the issue.

I had a look at the Query Profile Information Maintenance and the only thing that displays is "NO DATA"

If it's just one user, it could be something in their query user profile, i.e. something in the options they have set for themselves in that particular query. You can see what options are set using the Query Profile Information Maintenance utility, which you can access through the Nomads Utilities menu, or through the IDE Graphical Application Builder > Utilities menu.

Enter the directory and library where the query is located, the query that is affected and choose the User. This will display the information that has been saved for the user. If there is anything listed under Info Type it may be causing the issue, so you select it and delete it and re-run the query to see if that was the issue.

Okay, I'll have to see if FedEx supports 1.0 at the customer is on an older version of PxPlus.