{"id":4701,"date":"2025-02-05T10:49:42","date_gmt":"2025-02-05T08:49:42","guid":{"rendered":"https:\/\/in4mobackupstg.wpenginepowered.com\/support\/?post_type=resources&p=4701"},"modified":"2025-02-05T10:49:42","modified_gmt":"2025-02-05T08:49:42","slug":"main-improvements-in-in4mo-release-16-0","status":"publish","type":"resources","link":"https:\/\/www.in4mo.com\/support\/resources\/main-improvements-in-in4mo-release-16-0\/","title":{"rendered":"Main Improvements in in4mo Release 16.0"},"content":{"rendered":"

Auto-assignment of Task to Deputy in the Absence of the Auto-Assignee<\/h2>\n

In in4mo it is possible to set certain or all tasks to be automatically assigned to specific members. This is an effective way of ensuring that work progresses swiftly. However, if the person that tasks are set to be automatically assigned to is unavailable, e.g. because of vacations, the task was not automatically assigned to the deputy until now. In this release we are introducing an improvement that eliminates the need to manually assign tasks in these situations, as the task will now be automatically assigned to the deputy.<\/p>\n

Note, however, that if a deputy has not been set in in4mo for the person that tasks are set to be automatically assigned to, or if the deputy does not have sufficient certification, or if the deputy is also unavailable, the automatic assigning will not be successful, and the task has to be manually assigned.<\/p>\n

 <\/p>\n

Possibilty to Generate Custom Reports as .docx<\/h2>\n

It has been a wish of our customers to be able to create Report Builder reports in .docx format, to have more options to edit the reports and to easily copy content into and out of the reports. Earlier all the reports created in Report Builder were only available in .pdf format, but with this release, all in4mo custom reports can now be created in .docx format. Whether custom reports are created in .pdf or in .docx is based on a portal setting, which means that the activation of this functionality affects the creation of all reports.<\/p>\n

There are now three different portal settings available:
\n1) All Report Builder reports will be created in .pdf;
\n2) All Report Builder reports will be created in .docx;
\n3) All Report Builder reports will be created both as a .pdf and a .docx document.<\/p>\n

Below follows an example to explain:<\/p>\n

Insurance company ABC has created a Report Builder report regarding a checklist for roof damage, called \u201cRoof check\u201d. The insurance company has chosen that in their portal Report Builder reports in will be created in both .pdf-format and .docx format.<\/p>\n

In a given case, a user is filling out the report and selects \u201cCreate report\u201d.<\/p>\n

\"\"<\/p>\n

As a result, there are now two generated reports in the Document folder:<\/p>\n

\"\"<\/p>\n

This feature can be activated only by in4mo. If you want this activated for your portal, please contact your in4mo contact person.<\/p>\n

 <\/p>\n

Reminder About Expiring Password<\/h2>\n

For security purposes, in4mo passwords need to be renewed on a regular basis. To allow for passwords to be changed before it expires, we now send email reminders to users 3 days and again 1 day before the password is set to expire. The email contains a link through which the new password can be set.<\/p>\n

 <\/p>\n

Generic Rest Integrations \u2013 API to Get Case List and Improvements to Existing APIs<\/h2>\n

One of in4mo\u2019s main targets in our current development is to improve on our integration interfaces towards our customers. In this release we have implemented generic Rest integrations regarding fetching a list of all cases.<\/p>\n

If this integration is activated, our customers can via APIs fetch a list of all cases. The API allows limiting the case list based on case statuses: Open; Closed; Aborted.<\/p>\n

Furthermore, we are improving our existing integrations for
\n– Get iCC Workplan: Now this API also includes all auto-trips
\n– Get case info: Now this API also includes the user that made the compensation decision<\/p>\n

This means that up to and including the current 16.0 release we have now implemented generic Rest integrations within the following areas:<\/p>\n