Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
10 replies
Subscribers
8 subscribers
Views
4190 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Updating existing document stored in Appian I have a pdf document te
abhinavg
over 9 years ago
Updating existing document stored in Appian
I have a pdf document template being stored in Appian say ABC.pdf (version 1), due to some changes i need to update ABC.pdf with a new copy ( same file name ) and was done using upload new version wizard, keeping the earlier file name, updated copy got saved as version 2 as expected.
Constant of Document type was made to refer that ABC.pdf in proceses and expression rules
Issue : constant still refers to older version 1 instead of referring to new version 2, as a result processes & expression rules using that constant still points to old copy of ABC.pdf , some how older pdf copy (version 1 ) is getting cached and getting reflected wherever the constant being used.
I have manually updated the constant too by selecting the ABC.pdf document again from directory browser but no luck.. Is there anything being missed during document update as it's being used as a constant ?
OriginalPostID-149668
OriginalPostID-149668
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 9 years ago
What custom function are you using to get the document that makes you think it's retrieving the old version?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
abhinavg
over 9 years ago
I'm using Merge PDF Smart Service and here it always merge the document with older copy of document version 1, where it should have merged with new version 2
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
abhinavg
over 9 years ago
forum.appian.com/.../f-110409
Seeing same behavior as mentioned in above post
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Tim
Certified Lead Developer
over 9 years ago
This looks to be a bug in the code, when locating the document it isn't specifying ContentConstants.VERSION_CURRENT to ensure it's dealing with the most recent version. From what I recall the API's were changed back in the mid version 6s to handle this, perhaps this code hasn't been updated as it's been around for a while.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Steve
over 9 years ago
Yes, IIRC, I've seen the same bug with the custom smartnode which generates Excel spreadsheets from a template.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
abhinavg
over 9 years ago
Thanks Tim & Steve ...should i raise support ticket for the enhancement ??
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Tim
Certified Lead Developer
over 9 years ago
Shared Components are provided "as is" with no official support from Appian. They're mainly community provided assets. The plugin comes with it's source code and anyone can apply to modify and upload a new version.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
abhinavg
over 9 years ago
Agreed !
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
abhi.jana
Appian Employee
over 9 years ago
A new version of PDF Tools (v1.5.5) is now available on Forum, which addresses this reported behaviour and uses the current version for merging instead of the original version.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
abhinavg
over 9 years ago
Thanks Abhi !
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel