06.22.11-00

Improvements

1. View Overdue Order in Returning Site. (R2-19384)

2. Setting the default Return Site for Orders. (R2-19384)

3. View 'Affected Orders' when the Return Site is modified. (R2-19730)

4. New Column 'Last Container ID' added in 'Search Asset' window. (R2-19636)

   A field is added to the Search Asset Window or Asset Edit window to display the Last Container to fill the asset.(Highlighted in the screenshot displayed).

   This will help your team to more quickly locate equipment that returned from a show but not unpacked from the container.

5. Introduced set of 50 new CIDs to print UDFs for Purchase Order^* (R2-19743).
   ^*Refer the CID Master document for more details.

Bug Fixes

• SR-11180 — Changing dates of orders are very slow and in some cases it is impossible.

• SR-11545 — Option to turn off Reconciliation Jobs for GAS Script is disabled.

• SR-11359 — System is not closing the selected POs.

Improvements

1. Fax Number in company profile can now be edited. (R2-19733)

   The Fax Number Field can now be edited. All changes to the field will be override any existing values.

   For any technical assistance or implementation to restrict a field as Read-Only, please contact your PMs.

2. Allowing to add fields (including UDFs) as read-only. (R2-19734)

   All Crew Profiles have been given access to change their profile and the editable UDFs within their profiles.

   Although, if a certain field is tagged as Read-Only in the Crew Profile, then all those fields will appear as it is.

   For any technical assistance or implementation to restrict a field as Read-Only, please contact your PMs.

Bug Fixes

• SR-11570 — Order Labor Positions Modified rule failed with special character.

• SR-11606 — System throws a ORA-00600: internal error code, while doing freeform search

Improvements

1. Introducing User Context in R2 APIs for better concurrency management.(R2-17114)

   The R2 APIs have been enhanced to address the above issue, and now shall identify 'the user' (through the request header) who has request for the resource.

   And the requested data is processed accordingly for each of the 'User Request' separately and simultaneously, and without affecting or overriding each other's changes.

   Order of preference for empid:

   1. 'empid' if it exists in UserContext & is not blank

   2. Else 'empid' specified in .ini file

   Order of preference for siteid:

   1. 'siteid' if it exists in UserContext & is not blank

   2. Else default siteid of empid as mentioned in UserContext if empid is not blank

   3. Else default siteid of empid as mentioned in .ini file.