Convert Multiple Transaction Line Items into Configured Items in

Converting multiple line items into configured items within a single session can greatly enhance productivity and streamline the configuration process. The NetSuite CPQ Ecommerce Integration (version 1.2.1) introduces significant improvements that allow users to manage this process more efficiently.

What Changed in the CPQ Ecommerce Integration?

Previously, when handling multiple configuration submissions for the same product, users needed to group the product logic into a single action and utilize the recalcRulesets() function to refresh building blocks. This update simplifies those requirements significantly.

Now, with the restart parameter for the submitConfig() function, users can submit configurations to the transaction and restart the processing flow. This restart allows you to refresh building blocks and run further actions, improving the flexibility and readability of the code. Additionally, you can now use the product parameter to dynamically switch between different products across various transaction lines within the same session. This adjustment is particularly beneficial for large transactions, as it minimizes the number of script launches and saves necessary, thereby enhancing overall performance.

Example of Using submitConfig()

Here's an example showing how to use the submitConfig() function with both the restart and product parameters:

submitConfig({
    afterSubmitAction: '">new',
    restart: true,
    product: 13
});

Note: Keep in mind that when invoking submitConfig() with restart set to true, all subsequent actions will not execute. Therefore, it is essential to apply this in the final action of your list to ensure all necessary actions complete.

Introducing restartConfig() Function

Additionally, to facilitate even better transaction line management, the restartConfig() function has been implemented. This function enables users to restart the conversion process into configured items without submitting any configurations, which is ideal for preparing transaction data before processing.

When using restartConfig(), specifying a different product ID allows users to switch products based on the varying transaction lines. Using this function can be particularly useful in scenarios where a dedicated product prepares conversion tasks for multiple lines.

Example of Using restartConfig()

Here’s how you can utilize the restartConfig() function:

restartConfig({
    product: 13,
    copy: false
});

Note: If you call restartConfig() without any parameters, it will restart the processing flow with the same product ID and with a blank configuration.

Who This Affects

• Administrators: Benefit from simplified code management and enhanced performance.
• Developers: Gain flexibility in processing multiple transaction items within a single session.
• Sales Teams: Improve efficiency in handling complex configuration tasks.

Key Takeaways

• The restart parameter in submitConfig() enhances flexibility during multiple configurations.
• The product parameter allows dynamic product switching within a session.
• restartConfig() prepares transaction data without submitting any configurations, streamlining workflows.
• This functionality aids in reducing script loads and transaction saves, significantly improving performance.

Source: This article is based on Oracle's official NetSuite documentation.