Skip to main content

TenderUpdateInput

Input data for updating general tender information.

Contains fields for modifying tender metadata such as status, references, contact information, and validity settings. At least one field must be provided for the update to proceed.

input TenderUpdateInput {
  status: String
  reference: String
  remarks: String
  email: String
  type: OrderType
  validUntil: String
  source: String
  attributes: [AttributeBulkCreateInput!]
}

Fields​

TenderUpdateInput.status ● String scalar​

Current processing status of the tender.

Updates the tender's workflow status to reflect its current state in the processing pipeline.

TenderUpdateInput.reference ● String scalar​

Customer reference number or identifier for the tender.

Custom reference provided by the customer for their own tracking and identification purposes.

TenderUpdateInput.remarks ● String scalar​

Additional comments or special instructions for the tender.

Free-form text for any special requirements, notes, or important information related to the tender.

TenderUpdateInput.email ● String scalar​

Email address for tender confirmations and communications.

Must be a valid email address. Used for sending order confirmations, status updates, and other tender-related notifications.

TenderUpdateInput.type ● OrderType enum​

Business type classification for the tender.

Determines the processing workflow and business rules that apply to this tender. Must be one of the supported order types.

TenderUpdateInput.validUntil ● String scalar​

Expiration date for the tender validity.

Must be a valid ISO date string. After this date, the tender may no longer be processed. This is for display purposes only.

TenderUpdateInput.source ● String scalar​

Origin source of the tender.

Maximum length of 50 characters. Identifies where or how this tender was created for tracking and reporting purposes.

TenderUpdateInput.attributes ● [AttributeBulkCreateInput!] list input​

Order-level attribute values for this tender, merged into the set captured at tender start.

Additive: attributes you do not mention are always kept. An entry whose description is already stored overwrites its value; a new description is appended. To remove a single attribute, send it with a null value. An omitted array changes nothing; an EMPTY array removes every order-level attribute in one call.

Either identifier addresses the same attribute: an entry sent with attributeDescriptionName is resolved to its description before it is stored, so it updates or removes the entry a previous attributeDescriptionId write created, and vice versa. Both identifiers come back on every read regardless of which one you sent.

Caveat: resolving the identifier you did not send is best-effort, and is briefly unavailable during an attribute-description outage. The write still succeeds, but such an entry is stored carrying only the identifier you sent; until a later write resolves it, a differently-addressed write cannot reach it and removals for it are not synced when the order is processed. An empty array carries no identifiers and is therefore always safe to clear with.

Member Of​

tenderUpdate mutation