Starting 2019.2, you can now set the following workflow actions to fire using Client Triggers and execute on the supported sublist:
Return User Error
- SuiteFlow now supports triggering the Return User Error action using client triggers.
- The action supports 2 client triggers (After Field Edit and After Field Sourcing).
- The action can now be triggered by sublist change.
- Currently, only the Items Sublist on Transactions and Expenses Sublist on Expense Reports are supported.
Sample Scenario: Validate the value of Item's Amount upon change on Sales Orders.
Sample steps to set up:
1. Navigate to Customization > Workflow > Workflows > New.
2. For this example, set up the Workflow Definition Page according to the screenshot below. Adjust depending on your needs.
3. Click Save.
4. Double-click on State 1 and choose New Action.
5. Select Return User Error action.
6. Configure the action based on the screenshot below:
Note: When you change Triggering Client Fields from Sublist to Body, the following pop-up message will prompt:
7. Set a Condition.
Note: Sublist fields will become available for selection on the Condition Visual Builder if Triggering Client Fields is set to Sublist.
8. Click Save on both the Condition Builder window and the Workflow Action window.
Expected Result: Once Item Amount is changed in a Sales Order, a pop-up with the error text will prompt depending on the condition set for the action.
Set Field Display Type
- SuiteFlow now allows setting the Display Type of Sublist Fields.
- This enhancement extends the behavior of the Set Field Display Type action to work with custom fields on the supported sublist.
- Currently, only the Items Sublist on Transactions and Expenses Sublist on Expense Reports are supported.
Sample Scenario: Set the display type of a Custom Sublist Field to Disabled on Sales Orders which makes the field uneditable.
Sample steps to set up:
1. Do steps 1-4 on the previous example above.
2. Select Set Field Display Type action.
3. Configure the action based on the screenshot below:
4. Click Save on the Workflow Action window.
Expected Result: The Custom Sublist Field becomes grayed out and its value cannot be edited.
Set Field Value
- Users will now be able to trigger Set Field Value action on the client-side upon changing sublist values.
- Users can use a Set Field Value action triggered on a sublist field to insert data into a body field.
- Like the Return User Error action, Set Field Value supports 2 client triggers (After Field Edit and After Field Sourcing).
- Currently, only the Items Sublist on Transactions and Expenses Sublist on Expense Reports are supported.
Sample Scenario: Set the value of the Memo body field when the value of a certain Sublist Field is changed.
Sample steps to set up:
1. Do steps 1-4 on the first example.
2. Select Set Field Value action.
3. Configure the action based on the screenshots below:
Note: Like in the Return User Error action, the following pop-up message will prompt when you change Triggering Client Fields from Sublist to Body:
4. Click Save on the Workflow Action window.
Expected Result: Once the value of the Sublist field is changed (Amount for this example), the action is triggered and the Memo body field is set.
Have you already implemented any of the features for your business process?
Let us know what you think about the new features described.
-Jack