This is good to have. Dealing with users and their password isssues has
been a hassle. The workaround I've used is to always use the same
generic password when setting up the user account, always use the same
Welcome Email message that includes that generic password, and force all
new accounts to change password on next login. But you're right, that
should automatically be handled without me having to do that.
When setting up processing rules you are not always sure youwill get the
desired outcome, especially with suites that contain many rules. It
would be great if there was some functionality to run the processing
rules against a test string to see if the desired outcome is what I was
expecting. For example, I would be able to enter my value somewhere, and
see what it would look like after all of my processing rules ran.
Currently it is way too difficult to do any real testing to ensure the
Couldn't agree more. The current bot report is a great idea, but I would
prefer it was done in two stages. First enabling the report would just
let you identify all of the bot traffic, then we should have the option
to filter out that traffic. Identifying if we want it filtered after it
gets filtered is a little bit of a backwards approach. The ability to
identify our bot traffic and know before hand the impact of filtering it
out before we take that step would be a great addition to have.
In processing rules, I woud like to see an option when setting up a
condition to preform the action if the value of a variable has changed
since the last time it was recorded. So for example only copy the value
of prop1 to eVar1 if the value of prop 1 has changed since the last time
it was recorded during that visit. I understand that processing rules
cannot read cookies, so it would need to go back and look at the
previous hits in that visit to check for the value. This basically will
give us t...
I would like there to be a way to force variables to lower case from the
admin console. There are a couple ways to make it happen. When setting
up a prop or an eVar there could be the option to "force all to
lowercase" so I wouldn't see ford, Ford and FORD in the report. This
could also be handled by a change to the processing rules as well. There
could be the "force to lowercase", "force to uppercase", or "force to
propercase" options for any variable. I prefer the processing rules
method, but ...
I would like to ability to purge all of the values from a prop when I
want to repurpose it. For example, if I capture time of day in prop1,
but later decide that prop1should be current url, It would be nice if
all data that prop has captured could be purged so there are no problems
when viewing that prop overtime. I understand that this could be vary
powerful so it should be something that I would have to call client care
When uploading a SAINT file we have the ability to use FTP or a upload
the file right from the browser. When uploading a Data Sources file
there is no browser import option, there is only FTP. A browser import
option would be nice. I mean like really really nice.