What problem does it solve?
This Skill helps you implement NetSuite SuiteScript extensions for Orderful’s “Process as Custom” flow when standard JSONata-based mapping can’t express your inbound or outbound EDI requirements.
Core Features & Use Cases
- Inbound “Process as Custom” (SuiteScript MapReduce): stages inbound EDI JSON from
customrecord_orderful_transaction, parses custrecord_ord_tran_message, creates/updates the correct NetSuite records, and sets a terminal success/error status.
- Outbound “Process as Custom” (SuiteScript MapReduce or User Event / WorkflowAction): builds the outbound payload and stages it by writing a
customrecord_orderful_transaction in “Ready To Send” for the SuiteApp to POST.
- Maintainable deployment pattern: enforces the required sibling
*_Orderful_lib.js pattern, consistent script-parameter naming, and safe status transitions so transactions don’t get stuck retrying forever.
- Correct doc-series scoping (800 vs 900): guides you to configure the right entity (Customer vs Vendor/Location for 900-series) before writing code, including the 900-series lifecycle mapping to avoid incorrect source/target assumptions.
Quick Start
Ask Claude Code for a custom-process script plan for your specific doc type and direction, then request scaffolded steps that include the mandatory library file, the correct entity configuration, and the deployment parameter checklist.