Manage Transaction Line
Overview
This topic covers administration of the sub document (Transaction Line ) using the Redwood interface pages. Refer to Commerce Documents for administration using the classic interface pages.
Each Commerce process contains one document set. There are two types of Commerce documents: main document (e.g. Transaction) and sub-document (e.g. Transaction Line).
A document set is comprised of a main document with an attached sub-document. Using these document types, you can create flexible Commerce processes.
- For every process, Commerce documents are created in a one-to-one relationship.
- Every main document can be mapped to only one sub-document.
- A summary of sub-document data also appears on main documents, in the Line Item Grid.
Example: A process named RFQ can contain a main document and a corresponding sub-document (RFQ sub). Main documents are used for general information pertaining to the Transaction, like customer name or billing and shipping information, while sub-documents are used as product detail pages.
Manage Transaction Line Page
The Manage Transaction Line page provides access to transaction line settings, attributes, actions, and rules.
-
To access the transaction line document, navigate to: Admin Home > Quotes > Process > Manage Transaction Line
| Item | Description |
|---|---|
|
1 |
Access the Deployment Center |
|
2 |
Transaction Line tabs:
|
|
3 |
Basic: Manage / view the transaction line Name, Variable Name, and Description |
|
4 |
Layout: If enabled, this section provides access to the JET and Legacy layouts. For Redwood user side quote interface pages, refer to the Redwood Quote Designer to manage the quote layout. |
|
5 |
Advanced: Manage the following transaction line settings.
|
Administration
Notes
Warnings:
- You cannot add, delete, or update order numbers for documents in a deployed Commerce Process.
- Certain areas of document administration are only visible for Processes that have not been deployed. You cannot delete documents once a Process is deployed.
- Users cannot create or add quotes from Configuration to Commerce if mandatory items are missing.
Notes:
- Sub-documents and main documents have a one-to-one relationship, meaning only one sub-document can be associated with a main document.
- Main document Advanced Default will run when the transaction is first created. Its purpose is to set main document attribute default values. The purpose is to have one script that sets all of these attribute values at once, instead of pulling each of them separately. This also simplifies maintenance because all the defaults are set in a single script.
- Sub-document (line item) Advanced Default will run whenever a line item is added to a quote. The purpose of writing this script is to set all of the line item attribute values at once.
Tips and Considerations:
- Edits are not visible until the process is deployed (or redeployed).
- Create main documents as the primary documents in a set. Create sub-documents as detail pages that link up with main documents, that is, Line Item page for an RFQ.
- There is an option, Run Once For All Line Items, next to the advanced default on sub-documents. Standard functionality of the Advanced Default is that it will run every time a line is added to a quote. Having this option enabled enhances performance.
icon.




