Make Dejaclick support Angular
Currently when you try and record an Angular Web page in Dejaclick it is hit or miss. Dejaclick does not interact with the Angualr Element, it just clicks and sends keys. If you want to see the issues in action go to www.delta.com and record a flight search. Then play it back. Does not work well. Selenium is better suited for manuvering through Angular Journeys.
Ability to open browser as specific user (to validate SSO)
It would be beneficial if there is an option toopen browser as specific user that will enable us to validate SSO scenario just like how an enterprise end user would access an application. If we are including the login process as part of transaction, then we are not actually emulating the end user and hence this functionality is much required for several use cases that we have.Important Firefox DejaClick Announcement
Dear AlertSite Customer Mozilla is making significant changes to Firefox’s extension architecture with version 57. This version is slated for a November 14 th release. The AlertSite DejaClick plugin will not work on Firefox version 57 and above. To continue using DejaClick on your computer it will be necessary to have a version of Firefox running v56 or lower. Depending on your normal use of Firefox, there are several ways to accommodate this change. 1. Turn off Automatic Updates on your current Firefox browser to keep it at v56. This can be done from the Firefox Preferences panel. In v56, Firefox Updates is in the General tab. In previous versions, Firefox Update configuration appears in the Advanced tab. 2. Download and install an earlier of version of Firefox and install alongside your auto-updating version of Firefox. If this is your preferred approach, we recommend installing Firefox v52. This version will be installed to our monitoring network in Q4 2017 allowing you to record your web transactions with the same Firefox version used for monitor playback. Here are some key links: Windows 64-bit: https://ftp.mozilla.org/pub/firefox/releases/52.4.1esr/win64/en-US/ Windows 32-bit: https://ftp.mozilla.org/pub/firefox/releases/52.4.1esr/win32/en-US/ Mac: https://ftp.mozilla.org/pub/firefox/releases/52.4.1esr/mac/en-US/ General Information: http://kb.mozillazine.org/Go_back_to_an_old_version_of_Firefox For those looking for Linux or other Windows language options, the full v52 download page can be found here: https://ftp.mozilla.org/pub/firefox/releases/52.4.1esr/ IMPORTANT NOTES: You must disable auto-update immediately once v52 is installed as shown above. Auto updates can happen very quickly. To prevent immediate updates from occurring, we recommend disconnecting your computer from the internet prior to launching version 52 for the first time. In v52, Firefox Updates is in the Advanced tab in Preferences. It is best to close any open instances of Firefox before installing v52. V52 should also be installed to a different location to the existing version. A third option is to use DejaClick for Chrome. The Chrome version of DejaClick works with current versions of the Chrome browser. More information can be found here: https://support.smartbear.com/alertsite/docs/monitors/web/transaction/dejaclick-reference/chrome/index.html If you have any questions, please feel free to ask via comments or reach out to me or your customer success manager. Thanks! Denis Goodwin AlertSite Product OwnerFirefox 78
We're happy to announce that we have deployed Firefox 78 to the public monitoring network. This returns Firefox to the platform after a too-long absence. As with Chrome, we've added the ability to select browser versions, you can do this on the Advanced tab in monitor configuration. You'll have a choice of Default, Firefox 78, and Firefox 52. Please note that 52 runs a legacy version of DejaClick and should only be used by existing Firefox 52 monitors. Monitors created in the new Firefox version of DejaClick are not compatible with Firefox 52. Many legacy Firefox 52 can be converted to version 78, but your mileage will vary. Firefox 78 and Version Switching will be coming to Private Nodes in version 3.3, which will begin rollout in the 2nd half of January.Important Firefox DejaClick Announcement
Mozilla has recently removed access to legacy Firefox extensions, which prevents DejaClick from being added to older versions of Firefox (such as version 52). Until a Firefox Quantum-compatible DejaClick extension is available, please choose from the following options: 1. Use our Chrome extension. For instructions, see here: https://support.smartbear.com/alertsite/docs/monitors/web/transaction/dejaclick-reference/chrome/quick-start.html. Note that monitors recorded in Chrome can be uploaded as either Chrome or Firefox monitors. 2. Install Firefox 44 and manually add DejaClick. For users who must have a version greater than 38, the most current version of Firefox that allows installation of unverified extensions is version 44. Once that version is installed, you can install DejaClick directly using this file: https://cdn.alertsite.com/dejaclick/xpi/dejaclick.xpi. For more information on manually installing extensions on older Firefox versions, see this link: https://support.mozilla.org/en-US/questions/1101877Important AlertSite Monitoring Network Upgrade Notice
Dear AlertSite Customer, I’m excited to tell you about updates we’ll be making to our monitoring network in the next few months. We will be updating the browser versions for all three DejaClick playback options. First up will be Firefox, which will be upgraded from v38 to v52. This update will roll out to our public monitoring network in January of 2018. We will also be updating Firefox to v52 for PrivateNode Server v2.1 and greater* and this update will likely arrive in late January. Our Internet Explorer locations will moving from IE9 to IE11. This update should be complete in February 2018. There is also a likelihood that some location changes my accompany this version upgrade. Stay tuned for more details. Last, but not least, Chrome will be upgrading from v47 to (most likely) v64 (depending on the timing of our final QA, the exact version might swing to v63 or v65). We are targeting February 2018 for this upgrade and will communicate more specific timeframes as soon as possible. As with Firefox, this upgraded Chrome version will also be included in a PrivateNode update for PrivateNode Server v2.1 and greater* in the same general timeframe as the public location rollout. We will keep you in the loop as these rollouts progress. If you have any questions, please feel free to ask via comments or reach out to me or your customer success manager. * if your PrivateNode Servers (or InSites) are on a version prior to 2.1, please contact your CSM to learn about upgrade options Thanks and Happy New Year! Denis Goodwin Director Product Management, AlertSite
