search

horelvis / alfresco-pdf-toolkit

Automatically exported from code.google.com/p/alfresco-pdf-toolkit
Other
0 stars 0 forks source link

Encrypt PDF rule action uses same target folder as other actions #16

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create new folder rule with 2 steps: Step 1: Encrypt PDF with target folder 
"encrypted", Step 2: Move to target folder "original".
2. Note that Step 1 will change to use target folder of step 2 (i.e. "original" 
instead of "encrypted").
3. Rule fails because encrypted PDF goes into "original", then step 2 tries to 
move into same folder, get conflict.

What is the expected output? What do you see instead?
Rule fails. Encrypted PDF goes into "oroginal" folder instead of "encrypted" 
folder.

What version of the product are you using? On what operating system?
Alfresco Enterprise 4.1.0, Alfresco PDF Toolkit 1.0.0, Windows 7 Pro 64-bit

Please provide any additional information below.

Original issue reported on code.google.com by mark.s...@alfresco.com on 20 Sep 2012 at 2:48

GoogleCodeExporter commented 9 years ago 
Nice catch Mark, thank you.  It's probably something in the client-side 
Javascript that is incorrectly setting the parameter on the first action when 
the second action (move to) is added to the rule and configured.  I'm looking 
at it now, will have it fixed before we release 1.1.  This likely affects other 
actions as well, since they all share the same client-side renderers.

Original comment by nmcminn on 27 Sep 2012 at 1:22

GoogleCodeExporter commented 9 years ago 
It looks like correcting this will require changing the parameter name used for 
the destination folder in all of the PDF actions to something unique to that 
action.  Unfortunately this change will break any external code (scripts, 
workflows, etc) that call the custom actions.

We might have to live with this as a known limitation for now.

Original comment by nmcminn on 3 Oct 2012 at 2:08

GoogleCodeExporter commented 9 years ago 
I worked around this by using multiple rules with 1 step each (one to encrypt, 
one to move). Thanks.

Original comment by mark.s...@alfresco.com on 3 Oct 2012 at 2:18

GoogleCodeExporter commented 9 years ago 
Since fixing this will require potentially breaking any scripts that depend on 
this action and a workaround is available, going to close it out.

Original comment by nmcminn on 8 Oct 2012 at 9:04