TRUNK-6190: Clarification needed on implementation approach (Order field vs Order Attributes)

1

Hello everyone,

I am currently working on TRUNK-6190 (Add fulfiller location in orders).

I noticed that there was an earlier PR and discussion on this ticket where the recommendation was to avoid adding a direct field on the Order object and instead use Order Attributes for now.

Before proceeding further, I would like to confirm the preferred approach so that I align with the agreed design and do not duplicate or redo work.

Specifically, I would appreciate guidance on:

  1. Should the fulfiller location be implemented strictly as an Order Attribute for now, without any changes to the core Order data model?
  2. Is there any plan or timeline where adding a first-class fulfillerLocation field to Order would be acceptable in a future platform version?
  3. For the current work, should the focus be on:
    • Enhancing Order Attributes (including REST/FHIR support), or
    • Revisiting a core model change once attributes are insufficient?

I already have a local branch where I explored the direct Order field approach, but I have paused further work until this is clarified.

Best regards,

1 Like
2

In otherwords, are you saying that the ticket does not clearly specify what is to be done?

3

Hi @dkayiwa,

Based on earlier discussions recommending the use of Order Attributes rather than adding a direct field to the Order model, I’ve been following that approach and have opened a PR accordingly. I wanted to pause and confirm the preferred direction before proceeding further.

Thank you for the clarification and guidance.