Execute listener side of flow without SFDC trigger?

I am brand new to Celigo (and actually still a little raw with SFDC development). Is there a way to test a listener in a flow (in this case, Jira Cloud) without actually executing the SFDC trigger? Essentially, I just want to test the mappings to see if they actually produce the necessary data in Jira (issue create/update).

 

Thank you!

0

Comments

10 comments
Date Votes
  • Hi Mike Darretta

    You can test the flow by providing mock data in the 'Mock output' field on the listener. 
    Please refer to Debug a flow in test mode.

    Thanks!

    0
  • Thank you for the prompt reply! I did as you stated, and received a Mock response. 
    Is there a way, though, to actually execute the update in Jira itself using this methodology?

    0
  • Hi Mike Darretta,

    On the import step, toggle preview panel to "Send" and click the "Send" button. This will send the data to Jira, allowing you to view the actual response and see the updates in Jira.

    Please refer to Preview HTTP response for more details. 
    Thanks!

    0
  • Thank you again...you have been very helpful!

    Here is what I have so far:

    1. I have created a Integration Flow with a Salesforce Listener and Jira Import

    2. I go to "Exports", open my Salesforce Listener, select "Preview", and copy the Parsed Output

    3. I then go to "Imports", open my Jira Import, select "Edit mock input", and copy the data from the prev step

    4. At this point, whether I choose "Preview" or "Send", I receive a Success message:

    Success!

    1 Page, 1 Record

    .... but there is no HTTP request/response, nor parsed output.

     

    I feel I'm really close but evidently missing something critical. Here is a snippet from the Parsed Output from step 2:

     

    {
      "page_of_records": [
        {
          "record": {
            "attributes": {
              "type": "Pilot__c",
              "url": "/services/data/v54.0/sobjects/Pilot__c/a5eUG0000006R5ZYAU"
            },
            "Id": "a5eUG0000006R5ZYAU",
            "Name": "My IC Pilot",
            "Pilot_Drivers__c": "We want to provide assurance ,,,,",

    <plus lots of other stuff>

    ....

     

            }
          }
        }
      ]
    }

    0
  • It looks like my issue may be a bug(??) or workaround at best. I realized that the Send request did not have a valid URL associated with it. I went into my connection and refreshed the info (it was working prior), and now things seems to be executing, albeit with an error on the response.

    0
  • My next question is how do I access custom fields when mapping my data? As of now, I am simply typing them in manually, but this seems to requre that I have underlying understanding of the resultant JSON required to successfully execute the request. Is there a way for the mapping tool to automatically recognize (and thus format) my custom fields?

    0
  • Actually, back to the original question :). It seems that my connectivity to Jira works intermittently - that is, the base URI seems to be recognized or ignored without any changes to my configuration. As mentioned two posts earlier, I was able to execute the Send command (with HTTP errors...that ok), but once again no request is sent and no attempt to access the Jira endpoint is made. Do I need to file a bug ticket, or is there a workaround/gotcha that I need to be aware?

    0
  • Hi Mike Darretta,

    Could you please share the details of the Jira import and connection configurations, or submit a support ticket for further analysis? Please ensure any PII or sensitive information is masked. 

    Thanks!
    0
  • Hello again. Please close this ticket since the issue simply no longer occurs. There must have been something going on with the flow being out of sync or connectivity issues with Celigo. I have not encountered the issue for 2 days now. (Did nothing to fix it.) Thank you!

    0
  • Thank you Mike Darretta for the update.

    0

Please sign in to leave a comment.

 

Didn't find what you were looking for?

New post