06.22.06-00

Improvements

1. Complete re-modelling of Service Work Orders

   • Defined Service Work Order Stages. (R2-18825)

   • Availability of Assets 'In-Service' are now blocked only till End Date/Due Date. (R2-18825)

   • Seamless Status Transition of Assets 'In Service' during Physical Inventory — Serial Item, Serial Kits, and Non-Serial Items.

   • Visibility Of Conflicts On Future Orders In Cases Of Extended Service Periods. (R2-18825)

   • Reserve Assets under Repair on future orders

2. Enter Free-text 'Notes' for Order Lines in R2. (R2-19114)

Bug Fixes

1. SR-8830 — System is not printing the Event UDF Fields data

2. SR-8898 — System was displaying identical looking icons for a list of features.

3. SR-8664 — System is displaying incorrect pricing details even though the information has been modified.

4. SR-8933 — Asset projection view is not displaying expected details when any of the assets are locked.

5. SR-8463 — System is displaying Warehouse schedules, even though no item is reserved for the selected department in the selected site.

6. SR-9101 — System was displaying Warehouse schedule for an Order, even though it was searched using 'Project ID'.

Improvements

1. Enable HSTS for R2 Mobile User Maintenance app.

   In our constant endeavor to make all our web applications more secure and conform to latest security standards we have upgraded R2 Inventory Web Application with HTTP Strict-Transport-Security (HSTS). This means that R2 Inventory Application defaults to and works with "https" protocol. Any request with http protocol will automatically get redirected to https and thus making all request/response call over secure channel.

   To implement the required changes, we have made the required changes to the Web.config file and the enhanced security is already live from this release.

   What is HTTP Strict-Transport-Security (HSTS)?

   The HTTP Strict-Transport-Security response header informs browsers that the site should only be accessed using HTTPS, and that any future attempts to access it using HTTP should automatically be converted to HTTPS. Websites using HSTS often do not accept clear text HTTP, either by rejecting connections over HTTP or systematically redirecting users to HTTPS (though this is not required by the specification). The consequence of this is that a user-agent not capable of doing TLS will not be able to connect to the site.

   In its simplest form, the policy tells a browser to enable HSTS for that exact domain or sub domain, and to remember it for a fixed and predefined duration.  

   All Sub-domains associated with the parent domain must support HTTPS. You do not have to implement it for each sub-domain have their own HSTS policy.