06.22.12-00

Improvements

1. Default Return Site for Event based Orders. (R2-19907)

2. Seek confirmation before changing return site for Orders with Sub-Rented lines.  (R2-19878)

3. Scan 'Multiple assets' in one go, in the Sub-Rent scan window.  (R2-19582)

4. Defining the 'Idle Timeout' duration for Warehouse tasks to auto-close. (R2-20057)

   In Configuration, Warehouse tab, a new field named 'Idle Timeout' has been defined. The default value for 'Idle Timeout' duration  is BLANK.

   Based on the 'Idle Timeout' duration defined, system will Auto-close the Warehouse Task screens automatically, once the 'Idle Timeout' threshold is crossed.

   However, a BLANK value will keep the window remain open forever without an Auto-close.

5. New CIDs introduced to print the following:  

   1. Summary by Un-discounted section totals in Order prints. ^*(R2-19964).

   2. Sections with section total and item details in Order prints. ^*(R2-19965).  

   3. Section total, Item details, and Item totals in Order prints. ^*(R2-19966).

   4. Item section summary with Un-discounted section totals in Invoice prints. ^*(R2-19967).

^*Refer the CID Master document for more details.

6. Improved system performance on Product Daily Statistics script. (R2-19524)

Product Daily Statistics is a scheduler program which will collect various transaction status of a Product. For this report Repair days is the key.

• Repair Days is the duration when a product was on a service.

• If the SWO is in 'OPEN status', the 'In-Service' duration for the respective product/asset's is considered as Repair Days.

• The following reports cover this statistics — ProductDailyStatsView and ProductDailyStockStatsView.

Bug Fixes

• SR-7370 — System randomly deletes item from an Main Order when a Pool Transfer is created.

• SR-8852, SR-8951 and SR-9131 — Orders not going into Sign-off

• SR-9381 — System shows wrong section total amount on invoice print.

• SR-9394 — Site Average Cost of SKU is incorrectly turning negative upon Receiving Assets.

• SR-11512 — System shows an error 'Number precision exceeding' when an Order is opened.

• SR-11751 — In the COMPANY EDIT Screen , system is not allowing to 'Sort by NAME'.

• SR-11786 — Standard report is not displaying the ship dates for child item.

• SR-11921 — Error while opening the order from the Availability Drill-down after Asset marked missing in transferred site

• SR-12036 and SR-12159 — Warehouse department filter not working.

Bug Fixes

• SR-11019 — Notification fails when we generate notification specific to a site.

• SR-11716 — Graphical Scheduler session intermittently times out even when active after editing Calendar Event.

• SR-12116 — Crews have visibility of personal info of other resources in crew portal from global search.

Improvements

1. Auto Scaling/ De-scaling of DB pool size in R2API & R2 (R2-18975)

   Connection pool:

   In R2, we can edit more than one order in edit mode simultaneously. In such cases, the save of one order shouldn't affect the other orders in edit mode. To manage this, every order is allotted one dedicated connection, and same connection has to be closed, on closing the order. Creating new connection from the DB on every order edit will cause more latency to the system. Hence we need pool the connections at the every R2's client level. In R2, the connection pool is lazy loaded. That means, as and when the existing pool is exhausted, one connection will be taken from the DB and added to the Pool.

   In R2API case also the Connection Pooling is necessary, since every API Request needs a dedicated connection to process the payload.

   Previous to this improvement:

   In r2.ini, we can specify the max number of connection that can be taken from DB. We can increase this parameter to a higher, by which we can allow

   1. Users to edit more order simultaneously, in R2

   2. API server to process more number of Requests simultaneously

   Cons side of this is, the high number connection taken will stay in the Pool, even after

   1. the orders are closed and only a few orders are in use (in R2)

   2. the requests are completed (in R2API)

   After this improvement:

   At any point of time system maintains a buffer in the connection pool. Before the connection pool get exhausted, it creates additional connections and adds to the Pool, to be readily available for the system's consumption. Also when the connection usage gets reduced, system will release the excess connections to the DB, by reducing the Connection Pool size. This applies to both R2 and R2API.

   Parameters in r2.ini related to this feature

Improvements

1. Enhanced UI/UX with better performance through:

   1. Pagination in Search screen view for Opportunity, Company, and Tasks. (R2-19808, 19811, and 19812)

      When you search for Opportunity, Company, and Tasks; based on the count of records listed, system automatically adjust the number of pages that will appear.

      The total count of records are split in multiples of '25 Records per page'. Currently this format of '25 Records per page' is fixed, as this feature to fetch records

      is driven by API which supports extracting 25 records at one go.

Table 1: Filters supported for each of the Entities

Table 2: Linked Entities supported for search page (minimum columns required).

Table 3: Popover Card columns supported

b. Faster response time taken by Activity Timeline to display Tasks, Call Logs, Notes and Email (R2-19813)