New Dashboard for Asset Management – Adjutas Feature Update

asset default dashboard type


We have been listening to our user feedback and the result of that is a new dashboard type called “Asset Default”. This new dashboard type is built with our customers who use Adjutas for asset management and were bogged down by the default service desk dashboard.

This feature has been rolled out and is available to all our users.

asset default dashboard type


As a user, you can now get into your profile section and choose the asset default dashboard.

Asset Default dashboard provides snapshots about your entire service management.

Rollout pace:

Immediate full rollout


All end users

Action: Change management suggested/FYI


Benefits of adopting Google App Engine

developers image

Google App Engine (GAE) is a powerful platform to build both web and mobile apps. Its very scalable and takes google app engine imageaway the headache that comes along with a regular server. We have been using Google App Engine for everything from our internal applications to our flagship product Adjutas. We would like to share the reasons we went with Google App Engine so that it might be useful to you.

Continue reading

Adjutas New Feature Alert – 25-Jan-2017

Dear Customer,

Starting from today the following new features have been implemented in Adjutas:

New dashboard types

– Toggle between the default dashboard and the new classic dashboard.

Flexibility in enabling/disabling email alerts

– Enable the email alerts that you want your and disable the ones you don’t.

Feedback for resolved tickets

– You can now automate the process of collecting feedback for all your resolved tickets.

Asset activity details

– Track all changes related to the assets like changes in user, administrator, service updates etc.

Asset single import

– With advanced import you can now created assets, employees and vendors in one single upload. We believe this would greatly reduce the complexity around creating and managing assets.

Ticket requestor details

– Ticket requestor details can be viewed from the ticket details page.

Bulk upload customer login

– You can now create multiple end users by uploading a .csv file with all the details.

Please feel free to get in touch with us if you need any details regarding the features and how they benefit you.

We will also be sending a detailed help article to you by tomorrow.

Team Adjutas

Using an external database with Google App Engine



Recently we helped a situation where the customer for certain reasons did not want to use cloud SQL but wanted to use Google App Engine. This means that now we had to setup the application on Google App Engine but the database would run on an internally hosted server.

Theoretically this was possible but we did run across some issues while setting up.

'hostname' => '',
'username' => 'user',
'password' => 'password',
'database' => 'dbname',
'dbdriver' => 'mysqli',

The moment we made this change in our database.php file we got the following error.

Error: Server Error
The server encountered an error and could not complete your request.
Please try again in 30 seconds.

Google and Stackoverflow did not help us so had to post a new question on Stackoverflow (our question), but that was not of much help either. So we had to stick with what we knew and some trial and error. I decided to change the IP address to a proper host name.

'hostname' => '',
'username' => 'user',
'password' => 'password',
'database' => 'dbname',
'dbdriver' => 'mysqli',

The error that we go after we deployed to Google App Engine was different this time. The error said that the server was not able to connect to the server. We then looked at the error log and found out that the socket API was disabled. We then activated the billing for this project and the socket API was on (this might take some time, so in case you get an error, please give it some time and try again).

We then tested and everything was fine. Our software worked seamlessly. The performance might not be as good as Google Cloud SQL, but it was good enough and our client was not complaining.

Related help article:

Using Third-Party Databases