Update Confluence Page with data from Multiple Work Items

[Troy Anderson]

In trying to implement Edit Confluence Page , I am running into an error.

1. Any known ways to get details on the error?

2. I have used JQL in the trigger step (scheduled and manual) as well as tried a Branching step instead.  Goal is to update a single confluence page with, essentially, a row for each work item using data from each work item.  I theorize that both of these options (Branching for sure) are asynchronous and therefore the multiple updates to the page ultimately step on one another.  Thoughts?

[Bill Sheboy]

Hi @Troy Anderson 

Without seeing the specifics of your rule and the Edit Page action...

Perhaps the content has some markup that is leading to an error when the rule engine calls the REST API endpoint.  Or, there is a racetrack timing issue making the call.  (The Send Web Request action has this same timing challenge when a complicated smart value expression is used in the request body.)

To reduce the risks of page update collisions with multiple work items to add, I recommend using the Lookup Work Items action to gather them for one single edit call.

To reduce the risks of racetrack timing problems, and to help with debugging, perhaps try first creating a variable with the data to add to the page (adding that to the audit log to check for markup problems), and then use that single variable in the edit page action.

Kind regards,
Bill

[Bill Sheboy]

Hi @Troy Anderson 

Just following up to check if this answered your question.  If so, please consider marking this one as "answered".  That will help others with a similar need find solutions faster.  If not, please let the community know what help you need with the rule changes.

Thanks!

[Troy Anderson]

Hey Bill.  The question was specifically with regards to the 'new' Edit Confluence Page action.  Your suggestions on how to update a page are how I have it running currently (and will keep it that way!)

-Troy

[Bill Sheboy]

Thanks for that update, @Troy Anderson 

To summarize: using the REST API directly works but the new Edit Confluence page with the same content does not.

I recall other questions for this new action where some markup caused problems...possibly due to how the action processes the content before making the very same endpoint call as you are doing.  You could test this by:

• Using the create variable action, pre-build your content and store it.  That will eliminate a racetrack timing problem as the cause.
• Then use that variable as the sole content in the page edit action
• test and observe the results

[Bill Sheboy]

Hi @Troy Anderson 

Just following up to check your question is solved.  If so, please consider marking this one as "answered".  That will help others with a similar need find solutions faster.  If not, please let the community know what help you need with the rule changes.

Thanks!