CON-1098 - Updating to 4.3.2 breaking change - Old xPath selectors in Save Email Workflow

Created by Warren Buckley 10 Jun 2016, 12:40:10 Updated by Warren Buckley 27 Sep 2016, 13:40:10

By trying to fix up the xPath selectors that are described as working such as $current $site etc in CON-1085 we have broken the use of$currentPage/@id

2 Attachments

Comments

Mike Delamater 13 Jun 2016, 14:15:41

It's the $current that does not seem to be working. I am assuming that if I set the Where to save to $current, then the saved nodes should actually save as nodes under that parent...


Warren Buckley 13 Jun 2016, 14:49:30

Yes please can you try that @miked and let me know if that resolves it for you. Apologies for the breaking change.

I will not be able to get onto this until after CodeGarden I am afraid


Mike Delamater 13 Jun 2016, 15:03:34

That is what I have been doing, and it does not save the form as a child.


Warren Buckley 14 Jun 2016, 05:29:26

Can you remove the last backslash and try with just $current please & let me know

Thanks Warren


Mike Delamater 14 Jun 2016, 14:15:35

Still no save...


Warren Buckley 14 Jun 2016, 14:26:51

Sorry I am currently at our annual developer conference; CodeGarden to help look at this moment. I will back at my desk next Monday so will be able to take a look then.


Mike Delamater 14 Jun 2016, 14:31:08

Yes, I know. It's all good. If it would be helpful, I can create a user account so you can log in. Just contact me off list.

Thanks so much for the help Warren, and have fun at CodeGarden.


Warren Buckley 26 Sep 2016, 09:49:54

Apologies for the delay @miked I had forgotten about this issue and will look into this sprint for you.


Warren Buckley 27 Sep 2016, 12:31:21

@miked I have tried this in a workflow and set the parameter to be $current and my node was saved under the node with the form on correctly.

Can I have more details or notes please on how to reproduce.


Mike Delamater 27 Sep 2016, 13:37:30

To be honest, I went another direction with this project. I don't even have Forms installed on this site any longer. It turned out to be much easier to do by using ContentService to save the comments.


Warren Buckley 27 Sep 2016, 13:39:56

OK sorry to hear that. If you ever come across the problem again and can provide steps to reproduce then I will happily re-open this.

Thanks, warren


Priority: Normal

Type: Bug

State: Closed

Assignee:

Difficulty:

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint:

Story Points:

Cycle: