Reply to: Are there any restrictions with Document name while creating package?
Wednesday, March 28, 2018 at 11:15am
0
votes
Thanks for the clarification. I referred another question on the forum https://community.onespan.com/forum/restricted-symbols-document-names This says that special symbols ( ':\|/*?<> ) are converted to underscores. We have a requirement where we depend on the document name to identify signed documents. So, say, we pass document name as 'Document1' while uploading the document, it gets successfully uploaded but renamed to Document_Test_1 in eSignLive without letting the consumer know about this internal conversion. When the signed package is fetched, the documents come back in the zip with the transitioned name (Document_Test_1). This makes life difficult for us as the original document name is no more valid to compare. Can you throw an error upfront if document name has these special characters while creating the package?
Reply to: Are there any restrictions with Document name while creating package?
Wednesday, March 28, 2018 at 09:43amReply to: Are there any restrictions with Document name while creating package?
Wednesday, March 28, 2018 at 11:15amThanks for the clarification. I referred another question on the forum https://community.onespan.com/forum/restricted-symbols-document-names This says that special symbols ( ':\|/*?<> ) are converted to underscores. We have a requirement where we depend on the document name to identify signed documents. So, say, we pass document name as 'Document1' while uploading the document, it gets successfully uploaded but renamed to Document_Test_1 in eSignLive without letting the consumer know about this internal conversion. When the signed package is fetched, the documents come back in the zip with the transitioned name (Document_Test_1). This makes life difficult for us as the original document name is no more valid to compare. Can you throw an error upfront if document name has these special characters while creating the package?