Thanks, @sachincs1991 , There are few errors in the logs but I don't
believe that these errors are the reason for the issue that you are
facing. Do you get any error when you try to save the template? Or it
just crashes? If you get any error, can you share the error screenshot?
Hi @Praveen_p1 , The package that you would have exported, will contain
the DB related entries of the uploaded files, like the file name, upload
date, MD5 name, etc. The actual file name gets changed during upload and
gets changed to the file name's MD5 hash equivalent. It's uploaded on
the application server's file system in the following directory:
/usr/local/neolane/nl6/var/res// if its Linux and
\var\res\\ in case of Windows. So
you need to copy all the files in the above-mentioned directory...
Hi @isa87 , It's an error thrown by Windows OS. Not associated with ACC
as far as I know. There are a lot of troubleshooting steps available on
the internet and public forums for this specific error "This operation
has been canceled due to restrictions in effect on this computer".
Mostly it's suggested to check a few Windows Registry entries and
settings. You can get this checked by a Windows system admin.
Hi @RadAndric , The Last-Modified field of web-app changes once a
web-app is saved after any modification. The Modified By field also
changes with the mapping of the Operator who changed the web-app.If I
were to track this, I would create a new schema with fields >
Modification Date Time, Modified By, and Web-App IDThis schema will be
1-N mapped from the web-app schema and 1-N mapped from the operator
table.Now I would create a new workflow with a scheduler, query, and
update data activity. The ...
Hi @sachincs1991 ,Please check the web@default logs of the app server.
Higher memory consumption could be due to a repetitive task that the web
module is doing. This generally happens post a continuous retry after an
error. Still, 1.5GB web memory consumption is not that alarming. We have
seen systems working fine with that kind of consumption. Regards,Shivam
There can be a custom solution to this. You can use a counter in JS to
store the number of responses that have been received (After the survey
page and before the end activity as depicted by Script 2 in the diagram
below). You can store this count in a global variable (option) by using
the setOption() method. Now every time the survey is opened, you can add
a JS validator (Script 1 in the above diagram ) that checks the current
survey count from the option that you set earlier (using getOption()...