Tender Cloning

Feature Overview:

Winmore supports two types of tender cloning:

1. Basic Cloning – Creates a new tender with only minimal information copied from the source tender.

2. Deep Clone Tender – An enhanced cloning option that creates a complete duplicate of an existing tender.

This article focuses on the Deep Clone Tender feature.

Deep Clone Tender allows you to create a full copy of an existing tender, making it easy to reuse previously issued tenders when updating pricing or making adjustments. It eliminates the need to re-import tender files, redo column mapping, or repeat setup steps when the tender structure remains the same.

Using this feature, you can clone a tender, update the necessary details, and continue with pricing and submission.

Business Benefits:

The Deep Clone Tender feature delivers the following benefits:

• Significant time savings by eliminating the need to re-import tender files and repeat column mapping.
• Reduced manual effort in setting up tenders with identical structures.
• Improved accuracy and consistency by reusing validated tender configurations and data.
• Faster pricing cycles for repeat or revised tenders.

Feature Configuration

The Deep Clone Tender feature is controlled using a feature flag.

• Feature Flag Name: Deep Clone Tender

• How to Enable: Contact your Winmore representative to request activation of this feature.

Behaviour Based on Feature Flag Status:-

• When the flag is OFF:
  The system performs Basic Cloning and copies only minimal tender data.

• When the flag is ON:
  The system uses the Deep Clone Tender functionality and creates a full duplicate of the source tender, as described in this article.

  NOTE: Once the feature flag is enabled, the same cloning flow automatically performs a deep clone workflow. No separate action is required.

Functionality Details:

What Happens During a Clone Action with Flag - ON:

When a tender is cloned using with Deep Clone Tender feature flag turned ON, the cloned tender will contain the same data and set-up as the source tender. 
The primary data components which gets copied over are:

• Import History Table.
• Price Inspector Table (Audit details and cell-level comments are excluded).
• User Assignment Table.
• Bid-Level Exchange Rate Table.
• Manual and Shipper Blackouts.
• All Tender-Level Formulas.
• Ad-hoc Charge Code Table (if available in the source tender).

This ensures that the cloned tender mirrors the original tender setup as closely as possible.

Post-Clone Behaviour:

After a tender is successfully cloned,

1. Source Tender Reference

• Audit records related to the cloning activity will be captured in the cloned tender, within the tender level audit details.
• The cloned tender includes a reference link to the original (source) tender.
  
  

2. Automation and Extensions

• All pre-configured studio-level automations and extensions are automatically triggered for the newly created tender.

 3. Status Retention

• The bid-level and lane-level statuses in the cloned tender remain the same as in the source tender. 

4. User Flexibility

• Users can modify pricing, update lane details, or make other required changes before submitting the tender.

Additional Details:

1. Any user having tender create permission will be able to perform tender cloning.
2. Deep clone is only available for tender record template types (the standard record types which are associated with any of the pricing templates). Any other standard record type is cloneable but without the deep clone feature.

3. Same tender can be cloned multiple times.

4. User is able to further clone the cloned tender.

5. When user performs the deep clone action, system will not copy over the below data from source tender:
   • Price Inspector audit details and cell level comments details.
   • Create Submission table data.
   • Workflows data.
   • Conversations.
   • Conversation Files.
   • Attachments.
   • Activities.
   • To Dos.
   • Audit Trail
   • Enrichment History. 
   • Agent collaboration data. (if present)
   • Segment collaboration data. (if present)

Known Limitation:

Currently, when cloning an existing tender, users do not have the option to choose specific data components to be copied over to the cloned tender.