Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Is there any type of debugger output in PowerServer?

  1. How-to
0
Votes
Undo
  1. Tom Peters
    Tom Peters
  2. PowerServer 2020 or older (Obsolete)
  3. Thursday, 11 October 2018 15:08 PM UTC

Good Day!

My PB application deploys to PowerServer Web with no errors. I can run the application and it connects to the database. The frame looks great. However...

From that point forward, things are strange; no user objects are created, no data can be retrieved... but no errors are encountered! It's so weird. I can open every window in the application, but none of them display any of their data or user objects... 

Is there a ways to get something like PBDebug output while running in PowerServer?

Thanks,

Tom

  1. PowerServer Web
Error code 11030
How to get ODBC Data Source to appear in Profiles\...
Accepted Answer
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Friday, 12 October 2018 09:14 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # Permalink

Hi Tom,

it is quite normal a Web application does "nothing".

It usually happens because, as you say, user objects are not created and their code is not executed.

If any (Javascript-related) error is fired, you can increase the visibility level by displaying popups, go to AEM -> Client features and scroll to Error Message Mode.

However, as Chris suggested, debugging is the best way to investigate. Enable Appeon debugger and find the line of code that alters the application workflow.

Please take into serious account the Unsupported Features Report. If a user object contains unsupported feature it might not get created at all. Not to mention the handling of NULL values in boolean conditions or string/math operations, which can also produce different runtime behaviour (search for "NULL" in the Appeon PB help).

Last option, kinda slow&rude but definitively effective, is to insert MessageBox(). If you don't see it, wrong execution flow happened beforehand.

Best,

.m

Comment
Tom Peters
  1. Tom Peters
  2. Monday, 22 October 2018 14:31 PM UTC
Hi Marco - Thanks for this info. When I run my Analysis on my source and get "Have to Modify / Unsupported", it seems that even though that code is wrapped with IF ( AppeonGetClientType( ) = 'PB' ) THEN, the unsupported code still appears in the Unsupported Feature Analysis Report. May I safely assume that as long as the unsupported code does not run that things should still work in PowerServer Web? Thanks, Tom
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 22 October 2018 15:03 PM UTC
Yes, you may always get that message. What I did in my frameworks though was to isolate the commands that were PB Native vs PowerServer in different libraries and then dynamically instantiate objects based on PB vs PS. I then created different targets for PB vs PS. That allowed me to always have a clean full build / deployment.

HTH





  1. Helpful
There are no comments made yet.
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 11 October 2018 16:10 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Tom;

  There is no application "Profiling" feature for PowerServer based Apps. However, you can use the PS Web Debugger .... https://www.youtube.com/watch?v=ygGlWw4bpQM

HTH

Regards ... Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.