<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Emrox News</title>
	<atom:link href="http://www.emrox.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.emrox.net</link>
	<description>News and information about the Emrox network products</description>
	<lastBuildDate>Fri, 14 May 2010 21:31:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Emrox network version 2.1.11 released</title>
		<link>http://www.emrox.net/2010/05/14/emrox-network-version-2-1-11-released/</link>
		<comments>http://www.emrox.net/2010/05/14/emrox-network-version-2-1-11-released/#comments</comments>
		<pubDate>Fri, 14 May 2010 21:31:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emrox.net/?p=274</guid>
		<description><![CDATA[

Updates mostly relating to shipments and costs handling. An automated flow for both costs and notifications to customers has been added.


Categories and main categories

Maintenance of these has been simplified. No longer is it necessary to input a translation for every language just enter whatevery it should be called and that is it.



Order actions

Actions that have [...]]]></description>
			<content:encoded><![CDATA[<ul style="list-style-type: none; list-style-position: initial; list-style-image: initial; margin-left: 0px; padding-left: 0px; width: 784px;">
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Updates mostly relating to shipments and costs handling. An automated flow for both costs and notifications to customers has been added.</h3>
<p/>
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;"></h3>
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Categories and main categories</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Maintenance of these has been simplified. No longer is it necessary to input a translation for every language just enter whatevery it should be called and that is it.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Order actions</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Actions that have been done a service are now listed in the service. Example: &#8220;Customer was contacted about delay from workshop&#8221;</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Auto-notifications</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Possible to automate most of the behaviour in certain follow up views and other places by automatically trigger SMS/Email messages to customers to stores</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">The possible autonotifications are for: delayed services in workshop, services ready in store, unansweredd estimates and track-and-trace info</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">These settings can be modified from within Maintenance-&gt;General-&gt;Order settings or within the connected follow up view</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Loan items</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">If a loan item is manually returned the service status will properly reflect this.</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">For closed orders for which the loan item has not been returned it is now possible to send automated reminders. Relevant templates must be created if this feature is to be used.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Type of service partner</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">There is a new setting on the service partner (end customer communication) controlling wheter info received electronically<br />
from the workshop should be manually screened before published to the end-customer. At the moment, this only concerns cost<br />
estimates. The three levels are: &#8216;Screen&#8217;, &#8216;Pass-through&#8217; and &#8216;Workshop responsible&#8217;</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Screen: The estimates must be screened (no automatic update of debit account/customer notification on incoming estimates).</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Pass-through: The estimates are automatically ok&#8217;d: debit account is updated to &#8220;customer pays&#8221; + customer is notified.</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Workshop responsible: Debit account is updated to &#8220;customer pays&#8221;, but it&#8217;s the responsibility of the workshop to handle customer contact (no notifications is sent). As a consequence, customer web login info is supplied to the workshop in the order message.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Shipments</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Incoming shipments are now handled via searching. The relevant incoming shipment is search by entering a package-/seal-/order-number, workshop-name.</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">It is now possible to view shipments for other organisations to enable Contact Centers to view its associated organisations shipments and for customers to overview shipments on Customer Access</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Printing</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">For accounts in Germany and Norway the print header has been inverted. The horisontal positioning has also been adjusted to make the customers address appear in the window of envelopes.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Workshop access</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Customer number and SSN/VAT has been added to the customer information.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Service</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">When creating a MTR based on a service where a replacement IMEI or serial has been specified (i.e. a replacement object was handed out), the new values will be used.</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Fixed a minor bug that caused the quick-edit fields for customer email and mobile phone number to be reset if a service validation error occured.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Barcode scanning</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Since some barcode scanners in Germany seem to send &#8220;ß&#8221; instead of &#8220;-&#8221; that character is automatically replaced in the quicksearch and transport fields.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">New country tag, FO</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18527/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">A country tag for Faroe Islands (FO) has been added.</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.emrox.net/2010/05/14/emrox-network-version-2-1-11-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Emrox network version 2.1.10 released</title>
		<link>http://www.emrox.net/2010/03/30/emrox-network-version-2-1-10-released/</link>
		<comments>http://www.emrox.net/2010/03/30/emrox-network-version-2-1-10-released/#comments</comments>
		<pubDate>Tue, 30 Mar 2010 21:14:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Release]]></category>

		<guid isPermaLink="false">http://www.emrox.net/?p=266</guid>
		<description><![CDATA[Minor UI tweaks and server upgrades. Lots of behind the scenes modifications to optimize the code and make the environment run more smoothly. Mainly minor UI changes are listed below.


Search export

Possible to export search results to Excel XML (2003) and/or CSV. This feature has been available for some time but has now been spread to [...]]]></description>
			<content:encoded><![CDATA[<p>Minor UI tweaks and server upgrades. Lots of behind the scenes modifications to optimize the code and make the environment run more smoothly. Mainly minor UI changes are listed below.</p>
<ul style="list-style-type: none; list-style-position: initial; list-style-image: initial; margin-left: 0px; padding-left: 0px; width: 784px;">
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Search export</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Possible to export search results to Excel XML (2003) and/or CSV. This feature has been available for some time but has now been spread to more users and integrated tighter with the normal usage of the application</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Service edit</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Possible to more quickly update a customer email or SMS directly from the service edit view.</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Transport numbers are displayed and linked to the transport view.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Workshop statuses</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Renamed the workshop statuses, the &#8220;from/in workshop&#8221; was redundant.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">SelfService</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">If pre-defined error codes (symptoms) are enabled for the selected article, either symptoms *or* fault description is mandatory. Only the symptoms have the mandatory-dot however.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Cost handling</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">When a new cost (estimate or final) is created the status is reset to &#8216;No response&#8217;.</li>
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">When setting a response the change is logged in the order history as well as the sum.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Workshop access</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Rearranged order of sections.</li>
</ul>
</li>
</ul>
<ul style="list-style-type: none; list-style-position: initial; list-style-image: initial; margin-left: 0px; padding-left: 0px; width: 784px;">
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">New calendar</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">Fixes a positioning bug for Internet Explorer.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">RMA follow up</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">More explaination and help added to views.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Encoding error</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">The encoding error page was removed as it served no purpose.</li>
</ul>
</li>
<li style="padding-bottom: 10px;">
<h3 style="font-size: 10pt; font-weight: normal; background-color: inherit; color: #000000; padding: 0px; margin: 0px;">Service prepopulation</h3>
<ul style="list-style-image: url(http://net2.emrox.net/stable/18126/img/bluefront/check-small.gif); list-style-type: initial; list-style-position: initial; margin-top: 5px; margin-right: 5px; margin-bottom: 0px; margin-left: 25px; padding-left: 0px;">
<li style="width: 500px; font-size: 8pt; padding-left: 0px; margin-left: 0px; margin-bottom: 5px;">The transport related stuff in the service prepopulation interface was removed.</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.emrox.net/2010/03/30/emrox-network-version-2-1-10-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Emrox network version 2.1.8 released</title>
		<link>http://www.emrox.net/2009/12/04/emrox-network-version-218-released/</link>
		<comments>http://www.emrox.net/2009/12/04/emrox-network-version-218-released/#comments</comments>
		<pubDate>Thu, 03 Dec 2009 23:23:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Release]]></category>

		<guid isPermaLink="false">http://www.emrox.net/?p=156</guid>
		<description><![CDATA[Lots of GUI changes have been done and should be quite noticable. Attachments are now included inside of comments and can be directed towards specific receivers. Follow up has received an updated design that reflect more of a flow of services and RMA.


GUI modifications

Lots of small visual effects have been added. Fade and roll up effects [...]]]></description>
			<content:encoded><![CDATA[<div class="static_info">Lots of GUI changes have been done and should be quite noticable. Attachments are now included inside of comments and can be directed towards specific receivers. Follow up has received an updated design that reflect more of a flow of services and RMA.</div>
<ul class="entries">
<li>
<h3>GUI modifications</h3>
<ul>
<li>Lots of small visual effects have been added. Fade and roll up effects on windows and similar widgets.</li>
<li>The inbox has been moved to the menu bar instead of the main front page</li>
<li>The logout box has been moved to the menu bar instead of the top right corner</li>
<li>The logo in the header can be folded away by clicking the border around the logo. It can be folded back by click the border of the menu bar.</li>
<li>The menu items have been slightly updated and polished</li>
<li>New clearer icons for ?-boxes and i-boxes are used</li>
<li>The taskbar has been removed</li>
<li>URLs entered in an article description are now clickable</li>
</ul>
</li>
<li>
<h3>Statistics</h3>
<ul>
<li>Performance has been optimized to reassure that it gets generated quicker.</li>
</ul>
</li>
<li>
<h3>Follow up</h3>
<ul>
<li>The look has been modified to display more of a &#8216;flow&#8217; of how services and RMA should be handled.</li>
<li>The names of the view have been updated (and shortended) and more info-boxes have been added to assists the user with how these work.</li>
<li>RMA views have been optimized to make them displayed faster</li>
<li>A new view listing unreturned loan items has been added.</li>
</ul>
</li>
<li>
<h3>Inbox</h3>
<ul>
<li>Multiple links to orders are possible</li>
<li>The messages uses a page switcher so not all messages get displayed at once</li>
</ul>
</li>
<li>
<h3>Shipments</h3>
<ul>
<li>The incoming delivery handling was redone in the style of outgoing delivery.</li>
<li>Incoming shipments electronically communicated by the workshop shows up as prepared shipments.</li>
<li>It&#8217;s now possible to search for shipments (on comm_id) in the quicksearch field.</li>
<li>Transport number (comm_id) has been added to the printout of outgoing deliveries.</li>
<li>Package and seal numbers have been added to the shipment sent screen.</li>
</ul>
</li>
<li>
<h3>Orders (both service and RMA)</h3>
<ul>
<li>Attachments are appended to comments</li>
<li>Comments are added when the user saved a service. Not by first clicking add comment or similar</li>
</ul>
</li>
<li>
<h3>Service</h3>
<ul>
<li>Services only auto-close when recieving the &#8216;cancel&#8217;-answer to cost estimates if the workshop can electronically communicate with the store.</li>
<li>The way a user chooses to perform printouts is stored and reused accessing the printouts the next time.</li>
<li>New cost type &#8216;replacemen unit&#8217; has been added.</li>
<li>Order comments can be turned off via &#8216;Service partner&#8217;-view.</li>
<li>A reminder will popup if the user forgets to print out a loan/rental agreement if loan or rental items have been added to the service.</li>
<li>Customer can respond to comments from Customer Access</li>
<li>The customer will recieve an email with info about the order comment if an email has been specified</li>
<li>Once a workshop has been choosen it isn&#8217;t possible to unset it once the service has been saved</li>
<li>Cost centre, insurance number, purchase place and rma number can now be made mandatory.</li>
<li>Fields that are mandatory or contain an error should not be hidden when &#8220;show all&#8221; is un-checked.</li>
<li>Cost estimate/proposal notes has been replaced by a normal comment which will be displayed next to the cost estimate.</li>
</ul>
</li>
<li>
<h3>RMA</h3>
<ul>
<li>The amount of comments are listed in the tab for comments</li>
<li>Modification to agreements no longer requires a modification to the agreement text. Thus smaller changes can be made without the applicant having to re-accept agreements over and over.</li>
</ul>
</li>
<li>
<h3>Batch close via IMEI</h3>
<ul>
<li>When batch-closing is performed the concerned stores/contact centers will be notified via a message with links to all orders</li>
</ul>
</li>
<li>
<h3>New widgets for order-history, customer-info, article-info&#8230;</h3>
<ul>
<li>A new widget system is used for a lot of the popups which means less popup-windows appear from Emrox. Less clutter on the users workspace.</li>
</ul>
</li>
<li>
<h3>Customer information</h3>
<ul>
<li>Customer number can now be made mandatory.</li>
<li>Social security number/organisation number can now be made mandatory.</li>
<li>Mobile phone number can now be made mandatory.</li>
<li>Email address can now be made mandatory.</li>
</ul>
</li>
<li>
<h3>SelfService</h3>
<ul>
<li>SelfService now has support for category based symptoms.</li>
<li>When registering a new order a warning is displayed if an existing order is found with matching IMEI or serial number. It does not prevent the user from creating the order however.</li>
<li>Contact/user information is always mandatory when registering an order for an organisation.</li>
<li>Fixed a bug that caused some mandatory checks to be ignored.</li>
<li>Links to change the language of the interface have been added.</li>
</ul>
</li>
<li>
<h3>Customer access</h3>
<ul>
<li>When accessed from within a service (using the link) it is not possible to make changes.</li>
</ul>
</li>
<li>
<h3>Contact Center update</h3>
<ul>
<li>A contact center (CC) used to be forced to add the store-license which meant that they had a lot of functionality that wasn&#8217;t really necessary for a CC. This has been fixed by extending what a CC can do and thus it should (for most CC) be possible to remove the store-license and the CC will get a better GUI.</li>
<li>Since most CC don&#8217;t usually don&#8217;t need the outgoing/incoming delivery list these have been removed from this license.</li>
<li>A CC that creates order will get them default set to &#8220;Return to customer&#8221; this means that they will be automatically closed when the workshop sends the &#8220;Finished at workshop&#8221; status.</li>
</ul>
</li>
<li>
<h3>Statistics</h3>
<ul>
<li>Symptom codes are included in the statistics. Single column, comma separated.</li>
<li>Social security number/organisation number is included in the statistics.</li>
</ul>
</li>
<li>
<h3>Printing</h3>
<ul>
<li>For accounts in Germany and Norway the print header has been inverted. This should make the customers address appear in the window of envelopes.</li>
</ul>
</li>
<li>
<h3>ECC/SOMOS</h3>
<ul>
<li>Version 1.3.2 of the SOMOS documentation exists for third-party developers see here for more information: <a href="http://somos.sf.net" target="_blank">somos.sf.net</a>.</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.emrox.net/2009/12/04/emrox-network-version-218-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Brief information about the upcoming release 2.1.8</title>
		<link>http://www.emrox.net/2009/12/02/brief-information-about-the-upcoming-release-218/</link>
		<comments>http://www.emrox.net/2009/12/02/brief-information-about-the-upcoming-release-218/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 09:25:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Release]]></category>

		<guid isPermaLink="false">http://www.emrox.net/?p=153</guid>
		<description><![CDATA[Here is a PDF presentation of the upcoming release 2.1.8
Brief release info 2009-12-04
]]></description>
			<content:encoded><![CDATA[<p>Here is a PDF presentation of the upcoming release 2.1.8</p>
<p><a href="http://213.88.219.71/wordpress/wp-content/uploads/2009/12/brief_release_info_20091204.pdf">Brief release info 2009-12-04</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.emrox.net/2009/12/02/brief-information-about-the-upcoming-release-218/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Emrox network version 2.1.7 released</title>
		<link>http://www.emrox.net/2009/08/28/emrox-net2-version-217-released/</link>
		<comments>http://www.emrox.net/2009/08/28/emrox-net2-version-217-released/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 21:00:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Release]]></category>

		<guid isPermaLink="false">http://www.emrox.net/?p=39</guid>
		<description><![CDATA[Version 2.1.7
Minor release that mainly focusing on RMA details and delivery parts.
A new entry web-site has been done and exists on www.emrox.net.


New main/entry web-site

The site has been slimmed down a little and now focuses more
on news items and tips and tricks for our users. Please
subscribe to this sites RSS-feed to get this
information.
Visit www.emrox.net for further [...]]]></description>
			<content:encoded><![CDATA[<h2>Version 2.1.7</h2>
<div class="static_info">Minor release that mainly focusing on RMA details and delivery parts.</div>
<div class="static_info">A new entry web-site has been done and exists on <a href="http://www.emrox.net" target="_blank">www.emrox.net</a>.</div>
<ul class="entries">
<li>
<h3>New main/entry web-site</h3>
<ul>
<li>The site has been slimmed down a little and now focuses more<br />
on news items and tips and tricks for our users. Please<br />
subscribe to this sites <a href="http://www.emrox.net/?feed=rss2" target="_blank">RSS-feed</a> to get this<br />
information.</li>
<li>Visit <a href="http://www.emrox.net/" target="_blank">www.emrox.net</a> for further information.</li>
</ul>
</li>
<li>
<h3>Order settings</h3>
<ul>
<li>Possible to deactivate certain RMA views/functions (in the<br />
follow up) via order settings. Was patched into 2.1.6.</li>
</ul>
</li>
<li>
<h3>Messages/Inbox</h3>
<ul>
<li>Moved message functionality into the inbox since it was more<br />
intuitive then from the menu.  Now all message functionality<br />
is accessible from the inbox and not spread out across so many<br />
locations as before.</li>
</ul>
</li>
<li>
<h3>Follow up</h3>
<ul>
<li>Possible to deactivate RMA follow up views from &#8216;order<br />
settings&#8217; (only RMA Assignments at the moment).</li>
<li>More info boxes explaining how &#8220;Handling cost estimates&#8221; works<br />
have been added.</li>
<li>Centrally Initiated RMAs (CIR) are now accessible if available<br />
to the Applicants.</li>
<li>Applicants can get a printout of their RMAs from the CIR and it<br />
is also possible to get this from old already handled CIRs.</li>
<li>When examining a RMA (visible to the Dispatcher and Verifier)<br />
and it is set to a &#8220;Valid shipment&#8221; the RMA is autoset to<br />
&#8220;Valid RMA&#8221; to streamline the handling a little.</li>
<li>A icon is visible next CIR RMAs in Classify.</li>
<li>Bug that set the status of a RMA to finished when setting it<br />
to finished at verifier has been fixed.</li>
<li>All active orders with unanswered estimates are now listed,<br />
regardless of debit account.</li>
</ul>
</li>
<li>
<h3>Pre-reg Service/RMA</h3>
<ul>
<li>The frontend when searching and registering new customer has<br />
been updated.</li>
<li>Feedback during both the customer and article part to the user<br />
has been made a little simpler to understand.</li>
</ul>
</li>
<li>
<h3>Service</h3>
<ul>
<li>Product comment is now displayed better to the user.</li>
<li>Track and trace info is now accessible from both the service<br />
and the &#8220;Shipment browser&#8221;.</li>
<li>It is now possible to add a new contact to an existing (organisation)<br />
customer when registering an order.</li>
<li>Fixed a bug that prevented searching for un-answered cost estimates<br />
if they were not created by the searching organisation.</li>
<li>The article comment is nolonger displayed to the right. Instead a<br />
label is added in the article fieldset. The first 15 (or so) letters<br />
are displayed there along with a &#8220;show more&#8221;-link.</li>
<li>References to MTR occurs in multiple locations (history and print outs)</li>
</ul>
</li>
<li>
<h3>Customer handling</h3>
<ul>
<li>Possible to add a new contact person/employee on the fly when<br />
registring a company customer on a service.</li>
<li>Search for customer info at external system should now return data better</li>
</ul>
</li>
<li>
<h3>Support page</h3>
<ul>
<li>Possible to brand the support page like a template which will<br />
be used by children in a chain.</li>
<li>Bluefront support info should not look as much as the normal<br />
store support info.</li>
</ul>
</li>
<li>
<h3>Outgoing delivery</h3>
<ul>
<li>Added timestamps for when a transport was sent or received.</li>
<li>If a shipments hasn&#8217;t yet received any status on its services<br />
from the workshop it is now possible to cancel the shipment.<br />
Thus it is possible to create a new shipment for the<br />
services in the cancelled shipment from the outgoing delivery.</li>
</ul>
</li>
<li>
<h3>Cost communication and handling</h3>
<ul>
<li>Some workshops always used to register costs at their store<br />
even when it wasn&#8217;t so relevant. This doesn&#8217;t happen anymore.</li>
<li>All costs are now shown in the &#8220;Unanswered cost estimates&#8221;<br />
view, no matter what debit account has been choosen.</li>
</ul>
</li>
<li>
<h3>SelfService</h3>
<ul>
<li>Step 4 uses radio buttons instead of checkboxes, forcing the<br />
user to make an active choise. This was patched into 2.1.6.</li>
<li>Added an alert if no hits were found when searching for customer<br />
information via the internet.</li>
<li>Fixed a bug where some customer information-fields weren&#8217;t cleared<br />
when searching for customer information via the internet.</li>
<li>Services registered via SelfService should nolonger show up in<br />
outgoing delivery if they are sent directly to the workshop.</li>
</ul>
</li>
<li>
<h3>Customer Access</h3>
<ul>
<li>Costs are displayed both including and excluding VAT.</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.emrox.net/2009/08/28/emrox-net2-version-217-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>From now on&#8230;</title>
		<link>http://www.emrox.net/2009/08/25/from-now-on/</link>
		<comments>http://www.emrox.net/2009/08/25/from-now-on/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 11:52:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Site update]]></category>

		<guid isPermaLink="false">http://195.42.210.113/blog/?p=6</guid>
		<description><![CDATA[We will publish any news related to the Emrox network and its various products on these pages.
There will be tips and tricks published here as well so please keep track of any news that gets posted here either by subscribing to the RSS-feed or similar.
Kind regards
The BlueFront team.
]]></description>
			<content:encoded><![CDATA[<p>We will publish any news related to the Emrox network and its various products on these pages.</p>
<p>There will be tips and tricks published here as well so please keep track of any news that gets posted here either by subscribing to the <a href="http://www.emrox.net/?feed=rss2">RSS-feed</a> or similar.</p>
<p>Kind regards<a href="http://www.emrox.net/?feed=rss2"></a></p>
<p>The BlueFront team.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.emrox.net/2009/08/25/from-now-on/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
