Here is a list of the questions sent out during the webinar and the answers that were provided.
What is a trigger and why did you set it to be set to ALL?
In the workflow definition page, the TRIGGER field defines when the workflow initiates. It can be set to Before Record Load, Before Record Submit or After Record Submit. By default, it is set to ALL which usually means it'll initiate at the earliest trigger- which is Before Record Load.
What's the link that shows all the field ID and field name? Looks like a good resource to have.
You can check SuiteScript Records Browser and Filed Level Help on SuiteAnswers ID 74610 and 10043 respectively.
How did she view that the "Title" field was named "Title". She opened up a different window to see the field name.
This should be found under Parameters section when defining a Set Field Value Action. The FIELD dropdown shows different fields that are specific to the Base Record where the workflow is applied to.
I did not see values in my sandbox in the same manner of the instructor.
In case you're referring to the field ids, you may enable this by navigating to Home> Set Preferences> General > Put a checkmark for Show Internal IDs on the Defaults section.
Must you do set field value action before any workflow?
You can add any action on your workflow based on the order that will suite your business. It is not required to do the Set Field Value actions first before other workflows but it will be more convenient to do it that way if you need to set default values when on page load.
I heard there are 3 Options for Creating Workflows in NetSuite. Basic Workflow, Custom Workflow or Suite Flow. What option are we discussing? Can you please comment on the best usecase for each of the available options?
There's a few ways to create new workflows such as from scratch and from template, but they all navigate to the same Workflow Interface and create the same "type" of workflow. In that sense, there really aren't different types of workflows. SuiteFlow is what the feature is called and can be used interchangeably with "Workflow".
I knew that the system performance would be impacted depend on number of workflows/scripts on the record, any resource on this topic?
You may refer to SA 79632 to know more about the best practices in using the SuiteFlow feature.
In Accounting Preferences -> Approval Routing. How does this relate to Custom Approval Routing OR Suite Approvals?
Once the Approval Routing was enabled in your account, you can use Custom Workflows for your Approval Process. You can check SuiteAnswers ID 11104 for more details.
Where can we find more details about "case when " statements>?
There are a lot of case when function samples we can see from SuiteAnswers. The sample we used is one of the most basic but we have more complex samples available from SuiteAnswers. We can use case when for setting up conditions on Dates and Amounts. You can check SA 10101 for all the available SQL expressions and more details for Case When.
For performance should we be using certain triggers over others?
Triggers are dependent on how you want the action to be executed on the record. This is divided into 2 types, server and client triggers. You may check SuiteAnswers: 40568 - Triggers Reference for more details.
Can I add a line to a sales order based on condition on another line with the subsist action group? i.e. if any item on order has characteristic field A, add item 1234 to the order?
You can add conditions on your Sublist Action Group for each sublist field action. However the scenario you described cannot be do e directly but you can consider using a separate custom field as a flag(workflow custom field) to signify any change that we want to check in other lines as a workaround. You can also check this thread related to this.
I would like to use an Account's available credit limit to release an order, the credit limit will be sourced from the customers Account balance record and credit value available to determine whether to release the order to go to pick and ship
As long as the records are linked/related you can review if they are available fields under From Field or also use our Formula field and utilize the dot notation.
Can we see history of who changed a workflow when?
On the Workflow Pane, we have a History tab in which we will be able to see who edited the workflow.
