I am trying to automate a web application using firefox on blue prism. When I use the application modeler to launch the web application, first it is asking for credentials to login on a pop up window. Application modeler cannot identify this pop up has appeared. So I cannot automate the login. However after login manually, I can spy other elements in the application as normal. Any idea on how to automate the pop up window asking for user name and password?
I assume that you specified your application as browser based in application modeler. It's hard to answer your question without knowing how this web application looks and works like. There are few options that you can try nevertheless:
In the latest version (6.4) Blue Prism introduced Firefox plug-in. If you would be able to upgrade your version to the latest one (if you are not using it already), then maybe you'll be able to spy the pop up.
If this web application does not necessarily need be launched via Firefox in particular, then you can test its behavior and spying possibilities on other browsers - Internet Explorer and Google Chrome (supported by BP since 6.3 version).
You can spy the whole browser's window using Region mode and use Surface Automation techniques to input credentials and log in. SA functionalities are greatly improved since version 6.
You can try using web services (if applicable with this website) to connect with the API of the web application, you'll be able to pass/validate your credentials via web services as well. Blue Prism natively supports SOAP based web services, you might need to come with some code stages to wrap it up. It's pretty advanced stuff though and I wouldn't recommend it as a 1st choice.
Hope this helps.
Related
I decided to use the Housez theme as it advertises as super easy and flexible to use. I am not a web designer but have managed to get my site up and running. www.islandestates.net The problem I have is that there is no search option for the properties on a mobile device? The desktop version works well but how do I get a search box onto the mobile version?
The support from Housez is non existent, I have submitted a request to favetheme but they never reply.
Any help would be aprreciated.
Malcolm
After Summit 2019, we were excited to start working on updates for 2018R2, and I practiced adding mobile screens for our custom modules in my sandbox.
We decided to fully refresh our DEV instance and reapply our customizations. No problem there, but when I try "Add New Screen" in the mobile section and then try to enter my screen number, the mouse goes to "waiting" and I can't add my new screen. Eventually, I get a "timed out" message. Same problem even when trying to add a standard Acumatica screen. Everything else in the project and Acumatica web interface seems to work fine.
Any ideas on where to look for what is preventing adding a new screen?
I'm on Build 18.209.0021.
It seems like an Ajax issue in the customization project editor. After callback to server the client page javascript is stuck waiting on the server response. You can try using Chrome browser which has less of those Ajax hangs and update Chrome if you're already using it.
There is also a known issue specifically affecting 2018 R2 Mobile that leads to generic error Sequence contains no matching element on mobile detail page. Based on your question this doesn't seem to be the issue you are having but you can give the workaround to this bug a try:
Open Generic Inquiry screen (SM208000)
Select FS-ServiceOrder inquiry, uncheck Expose to mobile and save
On Apply Updates screen (SM203510), click on Restart Application
This was identified by Acumatica support as a bug. Upgrade to a new release for the fix.
I am trying to build a simple web application, which capture users photo and sent it my custom server there by connected to some other business use-case. My web page uses HTML's file input control to launch native camera or gallery pick up option.
var input = document.createElement('input');
input.setAttribute('accept', 'image/*');
input.setAttribute('capture', 'camera');
input.setAttribute('type', 'file');
input.click();
This web app, I placed in local webserver with a name "PhotoLocker" and testing with url like
https://localhost(ipaddress to access via mobile browser)/PhotoLocker/index.html
This link is working fine both on desktop and mobile chrome browsers and am able to debug any issues. Where as same link, I try to access from WeChat browser (just opening above link from chat window), it is not at all opening my application in WeChat in app browser.
After googling, I found that https URL scheme is not supported by WeChat. is it True? When I paste the same app url as weixin://ipaddress/PhotoLocker/index.html, I am able to see my web app home page but it is not working as expected.
My Question is - how to debug my webpage opened in WeChat browser? Do I need a official WeChat Dev account even to develop and test sample apps?
Additional Info :
I am able to debug webpage from WeChat web devloper tool as mentioned in below link. But, unable to debug mobile wechat page in this tool. It is always opening chrome dev tools.
https://mp.weixin.qq.com/wiki?action=doc&id=mp1455784140&t=0.06697335132505233#1
I am a frontend developer in China, Chinese. Forgive my English for any mistake, misunderstanding I could make. Some links (dev docs mostly) below contain sites complete in Chinese, because I can not find corresponding English ones for now.
how to debug my webpage opened in WeChat browser?
Tencent provide an IDE for developing regular web interface and WeChat-mini-program, with which developer can directly interact with:
JSSDK (basically a special weixin
Object lives only in in-WeChat-browser);
API provided in WeChat-mini-program.
If you download that IDE:
First it will ask you is to use you WeChat to scan the QRCode, then confirm login with your WeChat account;
Next it will show up two square button (image below), left one is for WeChat-mini-program, the right one is for you to testing regular web page.
Click the right blue one, then you can find your way out, it's just something built top on project Blink.
As you can see the part of debugging regular webpage in WeChat IDE is no more than a simulator (in the WeChat-mini-program part, developer can write code directly in it), and in my experience it does have bugs, you will still need to test code in real machine.
For that Tencent provide another tool called vConsole, tutorials here, with it you can do following things directly in in-WeChat-browsers:
View console logs;
View network requests;
View document elements;
View Cookies and localStorages;
Execute JS command manually
and so on
Do I need a official WeChat Dev account even to develop and test sample apps?
Depends.
You may know the Official Account inside WeChat, with webpages directly opened in any context inside in-WeChat-browser, it will have the ability to interact the weixin Object, or have some API like login with WeChat, pay with WeChat Pay:
API like close current in-WeChat-browser, hide-share-button will not required anything special, you don't need to register any Official Account;
But if you want yo do the Pay, Login thing, you need an Official Account and pay for the ability every year (not sure about this outside China).
The localhost problem you faced
I don't have my working machine with me now so I can not test. Regularly I can proxy localhost with Charles then debugging in WeChat, but never do the https, I will try it later.
All the information got regarding how to debug webpage opened in wechat browser redirects to how to see log or ajax/netwrok calls analysis.
Even with WeChat web devloper tool as mentioned in below link, I am unable to debug mobile wechat page in this tool. It is always opening chrome dev tools.
https://mp.weixin.qq.com/wiki?action=doc&id=mp1455784140&t=0.06697335132505233#1.
Hence further analyzed remote mobile webpage debugging and found that there is no way to put break points, watch, expressions and all just like in chrome dev tools is not possible.
As a work around - you are able to debug code, when you simulate page in dev tools but no way to debug webpage in mobile device.
Same webpage when tried to do remote debugging as per WeChat web devloper tool documentation. here we can only see console logs and network calls.
I would need the list of currently opened desktop apps (+ files opened in it) from a Chrome Extension, or at least the active application name (With current focus on the desktop).
Use case : Imagine a chrome extension that would get the list of tabs with URLS (I solved it with Chrome.tabs) and in addition would give the name of the current active app when Chrome loose the focus (idle) : exemple => powerpoint.app / documentname.ppt.
I'm looking for any option, ideally without having to implement a Desktop App that would exchange messages with the Extension. But if this is the only way, any example/experience to do so with Electron (http://electron.atom.io/) or Node-WebKit?
This may be possible in an electron app, but I don't think so as Electron is more multiplatform-oriented and this is a platform-oriented feature. You only will have access to methods that the developers chose to expose to you, and I doubt that they exposed a way to have this kind of information. (I have very little knowledge in the tech since I used it only once, so I might be wrong).
The only solution I see is the one you talked about in your question, a real desktop app messaging with the chrome extension.
I think most of the SharePoint developers and administrators know that with the change form Firefox 2 to Firefox 3 some functionality of SharePoint have became unavailable.
Especially adding Webparts to a site and using the PeoplePicker don't work anymore with Firefox 3. So I want to know how you deal with this problem when some of your users are complaining about having to use the IE to get the same functionality as with Firefox 2.
It's quite plain to me that it is not possible to get the full functionality with Firefox but it would be great to get at least the same with Firefox 3 as you got before with Firefox 2.
Or are there any workarounds to get Firefox 3 working with SharePoint properly?
I am using IE Tab: https://addons.mozilla.org/en-US/firefox/addon/1419
The main problem seems to be the fact that whenever a pop-up windows opens during a SharePoint action, like adding a webpart to a site, the information or data form the pop-up windows is not transmitted to the initial window which opened the pop-up window.
What underlying code is it trying to run that Firefox 3 won't support?
Is it just using a bad agent sniffer? that can't handle v3?
The only thing I've encountered in v3 that isn't handled as nice as v2, is the ability to call .focus() on non-form elements. It worked better in v2, v3 seems to have some issues.
The official announcement of Service Pack 2 for WSS 3.0 and MOSS 2007 contains the following text:
Also with the new service pack,
Internet Explorer 8 will be added into
browser support matrix as level one,
and Firefox 2.0 and 3.0 as level two.
So maybe an upgrade to SharePoint SP2 will fix your problems? More details on SP2 are scheduled for release next week.