Suitelet and RESTlet Deployments
The following table lists service deployments and their supplied availability.
|
Deployment |
Script |
Service Role |
Supplied Availability |
|---|---|---|---|
|
|
Field Service Suitelet |
General FSM service endpoints. |
Available Without Login box checked. Application access and authentication rules still apply. |
|
|
Field Service Suitelet |
Schedule Board entry point. Field Service URL defaults to |
NetSuite login required. |
|
|
Field Service Suitelet |
FSM Setup. Field Service URL defaults to |
NetSuite login required. Audience includes Administrator and Field Service Admin ( |
|
|
Field Service Suitelet |
FSM Mobile entry point. Field Service URL defaults to |
Available Without Login box checked. Application access and authentication rules still apply. |
|
|
Field Service Suitelet 2 |
Account-key setup and supported service and translation requests. |
Available Without Login box checked. Its serviced operations apply their own access rules. |
|
|
Field Service Restlet 2.x |
Authenticated service, file retrieval, and FSM Mobile request forwarding. |
RESTlet authentication and permissions apply. |
All service deployments are supplied as Released, Deployed, and Audit. The Suitelet deployments use Field Service System (customrole_nx_system). Available Without Login is a deployment setting. It does not make all FSM operations anonymous.
The main Suitelet's handled error response can include the stored error record ID. The RESTlet's local catch logs a failure and returns a general error. It does not create a Field Service Error record in that branch. A forwarded request can separately produce a downstream Suitelet report. An unsuccessful network request does not necessarily have a corresponding error record.