Hi
Migration to Nprinting 17+ (latest is November 2020 and I suggest to use it) is not a simple process. One thing you have to remember is that it is not an upgrade - it is migration and difference between 2 is fundamental.
I suggest you migrate to the latest version of NPrinting. Regarding your other questions https://help.qlik.com has 500+ pages help document with all prerequisits and requirements. There is no point to copy and paste all requirements but from my experience if you have never worked with NPrinting 17+ you should get someone who has good experiece with it to asses what will have to be done.
So before migration you need to asses all reports from current environment and see if current solution will be possible in new environment. Asses things which are not supported like: Linked fields, ftp destinations, users with the same email, lack of reload task, lack of jobs (which could setup task dependencies like reload qvw->import users->run and distribute report), office reports converted to html and embeded in email body, the way variable work in new nprinting (they dont expand), supported QlikView documents (no always one selected, no macros, no triggers, no webview, no hide/show columns in tables etc...)
Then you have account and server configuration and requirements like, dedicated server, dedicated service account, correct QlikView version and all setup things which need to be followed according to documentation.
Then you have report output formats: As soon as you use cycle functionality your output files will be zipped (are you prepared for that), some outputs may not be available, HTML report attachement is always zipped, Html report content is embedded (previously library of images was attached in coresponding folders and now is embedded as base64 code).
Lastly - User setup in NPrinitng is largely different. If you were using import task of users from QlikView entity or were replacing users before each task with new NPrinintg you may not be able to do that and will have to think about different solution. On top of that setup of tasks needs to be reviewed as there is no job feature all schedules have to be set from scratch.
So as you can imagine you need to be fully aware of how new NPrinting will work which judging by your actual question you are not. Therefore I strongly suggest you ask for help Qlik or Qlik partner to asses amount of required rework. Make sure you get experienced NPrinitng developer!
Summary:
My aim was to make you aware that it is not upgrade which goes: next-->next-->next--> finish & restart. Depending on size of your environment, amount of reports and their complexity it may be quite large and difficult task which I want you to be aware of. You have to be aware that potentially you may have to build new qlikview application(s) to support your new NPrinting.
hope this helps
cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
