Skip to Content
author's profile photo Former Member
Former Member

Agentry App crashes on Device but not in the ATE Testenvirement


we make a app which works fine in the ATE Testenvirement and also in a iPhone but our main Plattform is the The WIndows Mobile Pocket PC.

We use a Motorola MC65 with Windows Mobile 6.1 Professional.

On the Motorola the app crashes in a definite transaction when we close the transaction screen.

Workflow is this: we open a detail screen with a listview -> with double click we pick a object from a collection and starts the transaction -> close the transaction screen -> now a rule decide what will happen (you can see the rule in the picture) -> but the app crashs before something happens.

Could we debug the client or could we create some loggings on the device? We dont know how we could find out why the app crashes. (as information: if the agentry client crashes on this point, we could not end the task from the agentry client with the task manager, we have to restart the Motorola client)



Tags edited by: Michael Appleby

rule.jpg (509.5 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 04, 2014 at 07:16 AM


    now we fixed the problem.

    As i told you we start the transaction screen from the detail screen and after ending the gtransaction the screen did not close and the client did not respond anymore.

    We fixed the Problem in this way that we do a navigationstep after the transaction step. In this we make the decision which screen should be shown as the next screen an open it. Thats all. In all other Client beside the WinCE Client the Transactionscreen closed and we could see the last detail screen. But on the WinCE Client we nedd the navigation step.

    I dont know if this is a bug from the WinCE Agentry Client Version but this workarpund was the solution for us.

    @Jason: we breaking the rule down to separate subrules so the debugging in much better but we loose the reference to the object we used in the main rule, so we keep the active object refernce in a temp attribut at the main object and get the active object with this id in the subrules

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 22, 2014 at 02:11 PM


    What version of the Agentry client are you currently running?

    What type of transaction are you running prior to the crash?

    This is something where you need to look at all the steps of the action and targeting of subsequent steps. Your rule runs other subactions which also need to be reviewed in trying to determine where the problem is.

    I would recommend that you open up a ticket with Support as they can help you better troubleshoot and diagnose the problem.


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.