Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-19336

Salesforce Source kamelet: notifyForFields isnt very usable

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • camel-k-1.8.1
    • camel-k-1.6.7
    • Camel-K
    • None
    • False
    • None
    • False
    • % %
    • +
    • Automated

      salesforce-source kamelet has an option notifyForFields that can notify when something changes in salesforce through salesforce streaming api (more on notifications here: https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/notifications.htm)

      The problem with the kamelet is that there is hardcoded what it notifies on:

          from:
            parameters:
              notifyForFields: '{{notifyForFields}}'
              notifyForOperationCreate: "true"
              notifyForOperationDelete: "false"
              notifyForOperationUndelete: "false"
              notifyForOperationUpdate: "false"
      

      So it only notifies when I create a new object in salesforce.

      Salesforce always require to have at least Id in the query: "message":"'Id' field must be selected","fields":["Query"], so it doesn't matter what I specify in the notifyForFields, as I always get the notification on the Id change (as that is always "changed" as it is generated when creating a new object), because the kamelet only supports notifications on object create

              acosenti Andrea Cosentino
              avano@redhat.com Andrej Vano
              Andrej Vano Andrej Vano
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: