I'm new to Appian, and have created an RPA process by importing a .side Selenium file. This has created a new section in the workflow.
I've tried running this but whenever I attempt to test it, or to trigger it from a process flow it remains queued forever.
Will the sections exectute automatically one after the other, or do I need to add some command to make the process move from one section to the next?
Debug in Appian RPA
Appian RPA includes a debugging tool to walk you through the workflow action-by-action and isolate where issues might arise. To use the tool, you'll select Debugging? when you manually execute the robotic process in the Appian RPA console.
Go to the Robotic processes tab.
Find the robotic process you want to debug in the list.
Click the Execute icon rpa-execute-icon.png in the Actions column. Alternatively, you can find the Execute icon at the top of the robotic process configuration page.
In the Execution options, check the Debugging? checkbox.
Click the Execute icon rpa-execute-icon.png once more to start the execution.
https://docs.appian.com/suite/help/21.4/rpa-7.12/create/troubleshoot.html
Related
My team has an InstallShield configuration that registers a service. Since it's supposed to be automatically started upon a reboot, we can't set it to manual. According to the person responsible for it, InstallShield only gives the option of automatic or manual service setting.
Not being an expert on InstallShield, I'm still trying to help her figure out how to make the registration of the service automatic but not started. I haven't seen any such option in the client.
Am I looking at the wrong spot in InstallShield or is it not doable that way all together? If so, how should one approach the problem?
Assuming a Windows Installer project type in InstallShield, there are 2 different tables at play. ServiceInstall and ServiceControl. It is completely possible to define the service using ServiceInstall with start type Automatic and not actually start the service during the installer. It's the ServiceControl table that controls when to start/stop ( none, install, uninstall, both) a service.
For this situation I'd install the service as automatic and mark it for stop during both and start for none. You may also want to set the REBOOT property to ask for a reboot at the end of the installer.
Another option is to investigate why you can't start it right away. Is this a configuration problem or some other race problem? Often time fixing that will simplify the deployment story and allow her to start it during the install. One example would be if you don't have configuration data yet you have the service spawn off a background process that idles the service and puts a file system watcher on the config data. As soon as the data is there the service goes from idle to active without stopping and starting it.
I am trying to Run a project in Xojo, which used to run okay previously.
Currently observed behavior:
Clicking "Run", has Xojo display various messages, including "Done Assembling Code".
Then, "Build Failed" dialog box flashes briefly. So briefly, I cannot even grab a screenshot.
And then it disappears, and no diagnostic error/warning messages are given.
I am new to Xojo. The project used to build okay. Something must have changed. Is there a way to somehow see what the problem is? Right now it looks like the IDE keeps on working but the Run process just dies, after barely flashing "Build Failed" Dialog Box.
I will consider it a successful answer if it helps or aids me in the direction of solving this issue.
Turns out the Debug folder was locked by another process. Releasing the lock, restored Run operation.
Where can I find crash reports?
Windows allows you to collect a Minidump when a crash occurs.
The procedure requires modifying a registry value using Regedit. You can also do so with the Xojo command Registry http://docs.xojo.com/index.php/Registry
See https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396 for the exact procedure.
We have an app.exe that uses another 3rd party installation wizard app, InstallAnywhere, to install our application.
It is a text-based wizard - meaning a new shell is spawned (and the child process is executing some java.exe in order for its wizard steps to work) when
app.exe -i console
in the parent shell is executed.
Can pexpect be used in this case as a kind of question/answer interaction ?
We tried it with Hudson but it appears that Hudson can only monitor the parent process and not its child process. When Hudson job kicks off the python script, it starts but fails to begin at step 1 of the wizard - it hangs.
How can we overcome this ?
Thanks
If I'm reading this correctly, you want to interact with your executing installer (in this case, using pexpect) during a Hudson job, probably to do automated testing.
I'm thinking that expect may get you where you want to go if you call expect from a shell script (or batch file) that is, in turn, run from Hudson. The script would execute the tests, using your favorite flavor of expect, during which it either exits successfully or fails. Hudson would detect the failure, and you could then react accordingly. Your script, and any expect messages, would write to stdout, which Hudson would collect into your build log.
However, Flexera has a testing framework that allows you to test an installer via JUnit. Look at the bottom of this page. Or check out the JavaDocs.
This might give you more precision than an expect hack. You might even be able to write a Hudson plugin and do way with expect and shell scripts completely.
Update: after looking over the Javadocs, I found that the main class GUIAutomationFixture uses Java's Robot class. This means you probably won't be able to run this class on a headless server. You'll likely need either Windows, or a Linux/Unix box with a working X system.
We have a Visual Studio test controller with 3 registered test agents in a specific test environment setup for our nightly automation runs. I've seen ample documentation on having the build agents run the tests, but we need the test execution to go through the controller and run from the test agents instead.
My thought was to edit the build process template so it would trigger the execution of these remotely executed tests and then wait for the test run results, but I have no experience with build templates and I've been unable to find any examples showing how I might accomplish this. And this is of course assuming that editing the build process is the best/correct solution in the first place.
Can someone with experience with triggering remote execution of tests at the end of a build/deploy cycle point me in the right direction please?
Actually, you don'have to change anything to your template. Just make sure your build definition refers to the correct tests and testsettings file that are configured for remote execution.
Step 1:
Please open http://msdn.microsoft.com/en-us/library/ee256991.aspx and scroll down to the section "Add a test settings for remote execution or data collection to your solution". Follow this to create a test settings file for remote execution.
Step 2:
Edit your build definition: go to the Process page, under heading "2. Basic", open the Automated Tests dialog by clicking the "..."at the end. It the Automated Tests dialog, click "Add". Then browse for your test settings file (for remote execution, the one you just created) and confirm your choices.
Now save your build definition and queue your build. Automagically, your tests are now performed on the remote system, because your testsettings file tells your build system to do so.
Hope that is enough to start your remote tests to work.
I've got a custom ant script for building and other fun stuff. IntelliJ has very nice integration for handling Ant tasks. However, every time I run a task IntelliJ opens the script in my editor panel. It moves to the line of the task I'm running and then I close it; actually I now have it in its own panel, minimized to the max.
Is there anyway to disable this behavior? I just want the Ant script to run the task, pop up its own panel with some feedback (which it does) and then allow me to keep coding without having to close the script. Please tell me this is possible.
Man, I can't believe this only had 4 views, and two of those were me. Pretty weak.
Anyways, I've got a solution that might help someone else down the road. In the Messages window that pops up when the ant build starts there is an Auto Scroll to Source button. Make sure this button is unchecked.