Newly Create Page URL

[Chris Iacovelli]

I have a Confluence page that employs a ConfiForm to creates new pages, via IFTTT integration Create Page rules, with a given dynamic page title (per the entry data) and a corresponding dynamic label (per data entry). Works great and has helped automate new project/program repository build out (e.g., notes, referenced documents, action items).

1. Is there a way in the trap/capture the resulting URL of the page created via the IFTTT integration Create Page rule?
2. Can the trapped URL be used as the parent page in a subsequent IFTTT integration Create Page rule?

Looking for creative ideas here as I am unable to find an answer for this in the Atlassian knowledge base (I am limited by what key words I can think of).

[Alex Medved _ConfiForms_ · Accepted solution]

@Hi @Chris Iacovelli 

Will try to provide answers below

1. Best way is to capture back the page id of the created page, but you can also capture the url - both examples can be found here https://wiki.vertuna.com/display/CONFIFORMS/Creating+links+in+original+ConfiForms+entry+to+just+created+page

2. Yes, you can. Save it back as a page id (as mentioned in #1) into some field on your record and then reference that field in "Parent page" parameter

Som the IFTTTs will be as follows]

1. IFTTT to create main (parent) page
2. IFTTT to save back the page id of a create page
3. IFTTT to create another page, but that has a macro parameter for "Parent page" to be the field value (via [entry.field_name] notation) 

Hope that helps

Alex

[Chris Iacovelli]

Alex,

thanks for the info above. i followed the instructions but changed the URL to align with my server address, specifically:

entryId=[entry.id]&initCreatedPage=<a href="https://collaborate.mydomain.com/pages/viewpage.action?pageId=${iftttResult_0.id}">${iftttResult_0.displayTitle}</a>

i did notice it saved a "unknown macro" so perhaps my admins have prohibited return results usage (investigating with them now).

unfortunately, i am not getting the expected results (see below):

• iftttResult_0.displayTitle = ${iftttResult_0.displayTitle}

[Alex Medved _ConfiForms_]

Oh you are using a very old version of ConfiForms... Consider updating

But this should not be a problem for this specific issue

You have a very strange IFTTT that you put as a first one to run - remove it

Also, I really suggest to use the Page.Blogpost field type and you the example "on the right" from the page I have shared earlier.

This will help you to implement step #3

[Chris Iacovelli]

ugh, i did not even look at the version. i'll bring that up with our admin team as well.

shifting the ifttt rule you called out to the end alleviated the problem. appreciate the pointer.

[Alex Medved _ConfiForms_]

Yeah, we have 2.27.x now... and you are on 2.18.x

Makes sense to update at some point - lots of knowledge has been put to improve and extend the ConfiForms app.

[Chris Iacovelli]

thanks for the great insights @Alex Medved _ConfiForms_ . is there some documentation on all the components of the ifttt response object you can point me to?

[Alex Medved _ConfiForms_]

Hi @Chris Iacovelli ,

Yes, sure there is a documentation on this :-)