Does anybody have a javascript to track changes in a document created in Livecyle Designer? Am looking for something that does the same track changes as in MicroSoft Word where you can show what was deleted and what was added and allow the ability to accept the changes.
Is there such a script?
Track changes
2011-06-06 18:04:13
My Product Information:
LiveCycle Designer, Windows
LiveCycle Designer, Windows
2011-06-07 13:00:30
#1
I've never seen one but you can print to static PDF and then run document compair in Acrobat.
2011-06-08 01:09:42
#2
Change-tracking isn't something that a PDF (either an Acrobat PDF or an XFA form) is designed to support. When something is edited, there's no internal reference kept about what the old version looked like, who/why/when the change was made, etc. - so "not accepting" the change is a logical impossibility. You could in theory do something with a plugin, but storing change-tracking data within the file itself would be a technical nightmare as the PDF specification doesn't really give you a place to put it which won't then confuse users or interfere with other software - you'd probably end up having to attach binary data to the PDF, which users without the plugin wouldn't be able to use.
It's also important to say that the privacy protection issues around change-tracking are a real concern for users of products that do support it (Office for example goes to great lengths to give users the opportunity to get rid of it again). The inbuilt functions in Acrobat (such as Sanitize) wouldn't handle any plugin-related private data.
It's also important to say that the privacy protection issues around change-tracking are a real concern for users of products that do support it (Office for example goes to great lengths to give users the opportunity to get rid of it again). The inbuilt functions in Acrobat (such as Sanitize) wouldn't handle any plugin-related private data.
2011-06-08 03:28:34
#3
Hi,
here is a nice example, to create a kind of undo function in a XFA form.
You can use this to store any changes in the extras object of your form fields and you possibly can script a method to compare the current values with older values.
Then you can highlight changed field or recover an earlier state.
In fact, you still have to do a lot of scripting by yourself, but with this example, you have a great point to start with.
here is a nice example, to create a kind of undo function in a XFA form.
You can use this to store any changes in the extras object of your form fields and you possibly can script a method to compare the current values with older values.
Then you can highlight changed field or recover an earlier state.
In fact, you still have to do a lot of scripting by yourself, but with this example, you have a great point to start with.
2011-06-08 09:21:14
#4
@radzmar: That script may work for keeping a history of the _data_ entered into a form field, but you can't track changes in the _document_ because neither Acrobat nor LCD will record what they're doing. As I said, that's the domain of a plugin, and not something anyone would realistically want to use given how much user-visible data it would have to embed into the file.
2011-06-16 18:05:19
#5
How about a script that hightlights text or characters or words when a change is made. For example, if the original document has a sentence such as "the cow jumped over the moon" and another use changes "cow" to "dog", is there a way to write a script to automatically highlight the word because there has been a change?
2011-06-17 00:16:33
#6
Acrobat has a built-in function to compare documents. It does pretty much what you described.
Edit: I see this was mentioned earlier... At real-time, though, this is not possible with a script. However, I can imagine a script that makes a textual comparison of a file with a in-memory version of it, but it will still have to be triggered manually since there's no event launched when editing a file.
Edit: I see this was mentioned earlier... At real-time, though, this is not possible with a script. However, I can imagine a script that makes a textual comparison of a file with a in-memory version of it, but it will still have to be triggered manually since there's no event launched when editing a file.