Our team created for you one of the most innovative CRM systems that supports mainly business processes and allows for customization according to your needs. Be ahead of your competition and implement YetiForce!
In newer versions, registration screen prevents test environment to be debugged properly.
We are assisting a user with a yetiforce 6.5 installation that requires some tuning and some custom workflows to be created for their business.
Since they have added many custom fields and I need to work with realistic data, we tried to clone their installation into my local development server (virtualbox VM on my system).
Since 6.5, the registration system forces the environment a re-registration check which forced us to re-assemble the develompent site with internet connection in order to succeed in the re-registration, but then the following morning the registration in prompted again with "Authentication failed" status. Thus, we're unable to proceed in testing the custom workflow functions.
The environment responds to yeti.something.local, so it's not meant to be publicly accessible.
In newer versions, registration screen prevents test environment to be debugged properly. We are assisting a user with a yetiforce 6.5 installation that requires some tuning and some custom workflows to be created for their business. Since they have added many custom fields and I need to work with realistic data, we tried to clone their installation into my local development server (virtualbox VM on my system). Since 6.5, the registration system forces the environment a re-registration check which forced us to re-assemble the develompent site with internet connection in order to succeed in the re-registration, but then the following morning the registration in prompted again with "Authentication failed" status. Thus, we're unable to proceed in testing the custom workflow functions.
The environment responds to yeti.something.local, so it's not meant to be publicly accessible.
Is there really no way to bypass this??