<#C298P0BCK|> <#C29UWN90Q|> <#C29HQS63G|> I just s...
# suitescript
n
#C298P0BCK #C29UWN90Q #C29HQS63G I just saw a note that Netstuite will be deprecating the Available Without Login feature for Suitelets. I wonder if it will be a hard shutoff or just deprecated support and eventually to be completedly deactivated!??!?
c
Where did you see this? I saw that the external URL format is changing and existing links will not function after July 30, but nothing about the feature being deprecated.
n
It was a message from one of the Vendors we use, that has a SuiteBundle we've installed
c
I hope they were referring to the changes to the external URLs only - https://suiteanswers.custhelp.com/app/answers/detail/a_id/31709/kw/31709#subsect_0605063419
n
This was the note from their email "We are writing to inform you of upcoming modifications due to a change from NetSuite. Effective July 30th, 2024, NetSuite will deprecate the Suitelet's 'Available Without Login' feature for security reasons. To ensure a seamless transition, we will implement these necessary modifications for all customers on Tuesday, July 16th, 2024."
They are literally pushing an update today with like 4 hours notice...LOL
c
ha 🤡 🙃 🤠
n
But yeah I can't tell either....I see the release notes about the External URL, but this alert seemed somewhat sudden and also urgent!!
lol
e
This doesn't sound right. The 2024.2 release notes that were recently published still refers to the "Available without Login" setting several times. I wonder if the vendor is confused about the actual change.
c
It could be that something in the implementation of their bundle is incompatible with the change to
url.resolveScript()
m
There have always been restrictions on BFN SuiteApps using external suitelets
👍 1
c
FWIW A quick query in our environment shows a couple of dozen script deployments in third party bundles that meet the criteria
isonline = 'T'
s
@nsAI Was that email from NetSuite? Because I'm pretty sure we're not deprecating Available Without Login but changing it so that it is more secure, which includes breaking changes.
n
@Steve Goldberg thanks for the insight.....it was from a Vendor that has a Suitebundle they deploy
s
OK, they may wish to read the notice we sent and the supporting docs more closely
d
Sorry to resurrect an old thread, but will this affect files that aren't scripts - such as .csv files that have 'Available without a login' ticked?
s
It affects the API methods. What you're doing with them is largely irrelevant.
n
So, is it just me, or is the amount of advance notice given to a breaking change like this insufficient? I only became aware of this because of the advisory email that I received today about "Suitelets that are available without login have updated External URLs as of *May 9, 2024*" I checked my email and this is the first communication I've received about this particular change. (That includes the weekly "Release Notes" for May 6th and 13th. this topic is not even mentioned in either of those.)
s
You would need to talk to support about this. Notifications are targeted, both on the account level and the contact level. It is possible that your account was not flagged because we did not identify that you were already using this feature, or it could be that you were not identified as the primary contact, and so someone else at your business receives updates. I can't say speculatively.
n
I'll check with my AM/support, but even so, why would a change like this not be documented in the Release Notes / Help Center Weekly Updates published around that time?
s
Human error. It is in the updated 2024.1 release notes https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N3949604.html and I have already mentioned to the PM that it should have been mentioned in the Help Center Weekly Update page.
👍 1
n
@Steve Goldberg this is the notice from NetSuite "You are receiving this message because https.requestSuitelet(options) is used in one or more SuiteScript scripts in your account. The behavior of this API will change in the coming months. What is changing? Effective June 13, 2024, https.requestSuitelet() will be supported for internal URLs. This will become the default behavior, without the need to set the option.external parameter. As of July 30, 2024, option.external will be removed as a parameter option, and use of option.external=true will stop working. Previously, this parameter could be set to option.external=true to call Suitelet marked Available Without Login using the External URL on the script deployment record. After July 30, Suitelets called with https.requestSuitelet(options) will default to external=false behavior. This change also applies to the promise version: https.requestSuitelet.promise(options). Required actions You should remove usage of the https.requestSuitelet(options) method with option.external=true from your scripts as soon as possible. In the context of authenticated sessions, you can call your Suitelet using its internal Changes to the https.requestSuitelet(options) SuiteScript method URL by removing the option.external parameter from https.requestSuitelet(). Best practices to keep in mind when developing Suitelets include: Suitelets are not intended for use in systems integration use cases. Restlets are intended for this use. External Suitelets should be reserved for creating online forms. For more information on general guidelines for Suitelets, see SuiteScript 2.x Suitelet Script Type, SuiteAnswers ID 43799. For more information about the https.requestSuitelet(options) method, see https.requestSuitelet(options), SuiteAnswers ID 108345. If you have additional questions, please contact NetSuite Customer Support. Thank you, The Oracle NetSuite Team
104 Views