Confiform Edits and Links

[SKAdmin]

Loving the level of customization within Confiforms but I've run into to problems I can seem to get past. 

1) I have a confiform setup that creates a new child page after form completion, and it sends a email to the person listed with a link to the new page. Works perfectly. I also have  IFTTT setup on modified, which works except the link goes to the parent not the page that was just updated. The fields pull in fine. How to capture the id of the page child updated? 

Tried HTML <a href="https://confluence.x.com/pages/viewpage.action?pageId=${page.id}">Review updated Request</a>

2) Is there anyway to allow users access to the "Edit Controls for ConfiForms" button on the child page just created, but prevent the user from editing the page and block from inline editing as well? And also prevent them from editing the parent page. If I add restrictions to the parent page, the initial form still works, and they can not edit the parent page, but then the Edit Control button on the child page is hidden. Trying to prevent users from accidently messing up any of the confiform configs by editing the page.

I have the super user setup to be the product own added to the form. 

Been using this as my guide - https://wiki.vertuna.com/display/CONFIFORMS/Confluence+page+permissions+and+ConfiForms

[Alex Medved _ConfiForms_]

Hi

1. Do you store the value for the sub page in your form? I mean, as a hidden field or a page field type? Because I am not sure what is the "${page.id}" and what value it has

2. Yes, you can restrict edits on the created page, by using the https://wiki.vertuna.com/display/CONFIFORMS/Configuring+ConfiForms+IFTTT+actions+and+rules#ConfiguringConfiFormsIFTTTactionsandrules-RestrictPageEdit

Alex

[SKAdmin]

@Alex Medved _ConfiForms_ 

I have the form definition will all the field definitions on the master page. The Registration Control only has the 1st set of fields needed for the form, then in the IFTTT Rule has all fields are listed and added to the new child page. The Edit Controls macro is also included in the same IFTTT Rule. All the users with ready only access to our space can use the submit a request, but they can't use the edit control on the child pages. 

[SKAdmin]

This one works perfectly after the new page is created. 

<a href="https://confluence.com/pages/viewpage.action?pageId=${iftttResult_0.id}">New Request</a>

I was able to capture the new page id and use that for modifications. 

[SKAdmin]

I think I solved the 2nd part. I was trying to use this 

In ConfiForms Form Definition under super users 

[entry.partnerOwner],[entry.productOwner],[entry.productionOwner]

had to use a group in confluence instead.