Change Log
2.30
- Introduced a Mappings tab where you can map country names that are not supported by the App to the corresponding country names which are supported by the App. For example: Deutschland is not supported by the App and thus you will see Unknown as the value shown in the Local Time fields. However, if you map this value to Germany as shown below, then the Local Time fields will show the correct time zone information.
- The way the App related triggers run is modified in this version. If the records to be processed by the trigger exceeds the limit specified in the Record Limit option, then all these records will be processed asynchronously through a batch job. By using the Batch Update Frequency (Hrs) option, you can setup the frequency of these batch jobs.
These changes are done to ensure that the App related triggers do not take a long time to perform its time zone lookup logic, and thus potentially run into Apex CPU time limit exceeded errors. These situations could arise when there is a mass create/update of a large number of records.
2.29
- Updated the Apex classes to Salesforce API version 58.0.
- Tested and updated the App to ensure that it is compatible with Salesforce Summer 23 release.
- Added time zone lookup support for additional North American telephone area codes:
USA: 235, 324, 353, 436, 457, 624, 645, 686, 729, 738, 821, 837, 924
Canada: 257, 879, 942 - Added time zone support for the Salesforce User object. Please read this blog to understand how it works.
2.28
- Added support for the following Antarctica bases and research stations.
- Artigas Base
- Bellingshausen Station
- Belgrano II Base
- Carlini Base
- Casey Station
- Davis Station
- Dumont d’Urville Station
- Esperanza Base
- Escudero Station
- Great Wall Station
- Halley Research Station
- Maitri Station
- Mawson Station
- Marambio Base
- McMurdo Station
- Mirny Station
- Neumayer-Station III
- Orcadas Base
- Palmer Station
- Progress Station
- Rothera Research Station
- San Martín Base
- Scott Base
- Syowa Station
- Troll Station
- Vostok Station
- Zhongshan Station
- Added support for the following countries.
- Bouvet Island
- British Indian Ocean Territory
- French Polynesia
- Kiribati
- New Caledonia
- Saint Helena
- French Southern Territories
- South Georgia
- Deprecated Find Local Time buttons. These JavaScript buttons are initially developed for Salesforce Classic. However, JavaScript buttons are not recommended to be used in Lightning Experience due to security concerns. In case you are looking for similar functionality, please use the Local Time Action component instead.
2.27
- Further optimized trigger code for Account, Contact, Lead, Task, and Event objects to run more efficiently.
- Tested and updated the App to ensure that it is compatible with Salesforce Spring 23 release.
- Added the following new lightning components. These components are available as part of the Extended licensing option. Please contact us if you would like to upgrade your license from Standard to Extended.
2.26
- Updated the Apex classes to Salesforce API version 55.0.
- Tested and updated the App to ensure that it is compatible with Salesforce Winter 23 release.
- In the Local Time Config tab, added a new Default Timezones subtab. For countries with multiple time zones (example: United States), you now have an option to define a default time zone. In cases when the App lookup fails for a record in finding the time zone based on address and phone fields, the App will then use these defaults to populate the time zone information on the record.