As I'm sure many of you have noticed I can bitch and moan quite a bit. I won't typically apologize for that behavior as most of the time my frustrations are spot on.
However, I will try to share my positive experiences as well (I already have with SuiteScript and Web Services).
I'd like to share a recent solution to a use case that uses saved searches and SuiteLets. It's not complex (at all) but once I fleshed it out it opened my eyes to how much further I could extend this pattern (and already have).
We are a DME (Durable Medical Equipment) company and sell direct to patients. We also bill patient insurance (nightmare) and depending on the insurance this can be very involved and require many different steps and workflows. Once every thing is done we need to submit our claims to the insurance companies. "Submitting a claim" currently means entering data from NetSuite into a 3rd party EDI billing application. I don't like this workflow, but we are stuck with it until I can find the time to deploy our own web service with EDI capabilities (not simple).
Anyway, the data we need to enter comes from the following records:[LIST]
[*]Patient (Customer)
[*]Sales Order
[*]Invoice
[*]Claims (children of Invoice)
[*]Physician's Order
[*]Physician
[*]Insurance Policy
[*]Insurance Plan
[*]Insurance Company
[*]HCPCS Code
[*](several custom lists)[/LIST]Some of these relationships are 4+ layers apart, a single saved search was not possible.
The workflow is:[LIST=1]
[*]Each morning a clerk would load up a list of all Claim records with a status of "Pending Submission"
[*]They would click on each one and a new view would display all the data from the above mentioned records.
[*]They would then enter the data into the billing application
[*]Finally clicking "Done" which would update the status of the claim and close the details view[/LIST]I come from a desktop/rich client background and so my first instinct was to use Web Services and load all the above required data into our office desktop application. After roughing out the design over a couple days I quickly had 1000+ lines of really ugly WS proxy-littered code that was taking for ever to load (no joins for custom records in SuiteTalk)
During a smoke break the word "SuiteLet" popped into my head and I started thinking if this could be done purely in NetSuite. (I'm sure many of you are saying "Duh, of course it can" - I was late to the party)
It can. I'm THRILLED with the final workflow, it's so much easier to use, easier to implement, easier to deploy and maintain.
Essentially I'm doing the following:[LIST=1]
[*] Create a Saved Claim Search that pulls all the records that are ready for submission.
[*] Added a formula(text) field to the result that had a URL to a SuiteLet (passing the Claim ID in the url)
[*] Created a SuiteLet that would load all the above mentioned records (on the server, very fast) and then build up a UI.
[*] After the data is entered the user presses a "Done" button
[*] I update the Claim's status and redirect (unsupported) back to the saved search (which is now minus one Claim)[/LIST]This process is repeated until all the Claims have been processed.
Like I said, very simple but that is where the beauty lies.
I have already copied this pattern to take care of two other workflows and each took about 6 hours to create. Had I gone the WS/desktop route this would have been easily 4x that amount of effort.
So...NetSuite team, Evan, Yang, etc: [edited] SuperDuper® job with SuiteLets and searches!!!
This post wouldn't be complete without a wish/observation/suggestion list.
[LIST=1]
[*]Support redirecting to saved searches from SuiteLets. As you can see, this is a powerful use case and "just makes sense"
[*]When a search only has one result the single record will be show rather than a result list with 1 match. This breaks my workflow as I'm presenting a list for users to click a custom link, not navigate to the record. Please consider making this an option in the search setup (or somewhere)
[*]Allow me to remove the "Edit | View" column
[*]Allow me to remove the "New" column
[*]Allow me to remove the icon column
[*]SuiteLet control layout is tough to work with, I'm finding it quite challenging to build an attractive UI. Consider colspan and rowspan support.
[*]Multiple submit buttons, I may want to have 3 buttons that each will submit my SuiteLet but carry a different parameter. It could be this is possible, but I don't think so.
[*]More control of nlobjField formatting (width, visible, enabled, etc)
[*]Support for radio buttons[/LIST]