Axes Screens are not loading inside Command Handlers

[leojp]

Hi Team,

We have four tabs for which four different command handlers are tagged to each tab. Unfortunately tabs are not loading axes screens when executing as VLF-ONE in chrome browser. As we have used lansa Version 13 we have completed followed all the settings and choosed options was working in 13 to work in LANSA Version 14.

Attached is the screen shot for your reference kindly help here. Your help is highly appreciated here.

Additionally the attached command handlers will render axes screens only. It does not have any reusuable component attached or used.

[MarkD]

Is this a RAMP project?

[MarkD]

I mean are you using the RAMP product to embed the aXes screens inside the VLF-ONE application - http://docs.lansa.com/14/en/lansa050/index.htm#
or are you just trying to embed them yourself?

[leojp]

Hi Mark,

Thanks for your reply. Yes we are using a Ramp Project trying to embed axes screens inside the command handlers.

[MarkD]

The first thing to check is whether the command handler definitions are actually associated with a RAMP screen.

For example, the Details command in business object Orders here is associated here with the destination screen ORD_MAINT:

Capture.PNG (79.24 KiB) Viewed 22225 times

[MarkD]

You should also check that the you save your framework you have a server tagged as the deployment server.
If you are using the latest VLF version (EPC141034) it should warn you if this is not set correctly when you save.

Capture2.PNG (34.31 KiB) Viewed 22225 times

[MarkD]

Of course the other check is to execute with trace mode turned on.

[leojp]

Thanks for your suggestions. I have tried saving server as deployment server and also checked the Ramp option for the business object that we are trying to have axes screens rendered. But still we are facing the same issue when executing it as VLF-ONE is chrome browser.
Please see to the attached snap shot of Command Handler for the Business Object 'Post Transaction'.

[leojp]

Screen shot with changes highlighted(circled in Red color).

[leojp]

Kindly let us know on this issue. Thanks.

[leojp]

Hi Mark, I have tried all options to get the axes screens loading but still I could not achieve it. When I click on tabs opening in web(browser) it shows a message 'No instance list available'. Please clarify what does that mean by. Attaching again the same screen shot encircled that text.

[MarkD]

Sorry - I missed this first off:

Capture_1.PNG (25.07 KiB) Viewed 22230 times

You command (handlers) are tagged as instance level command handlers.
That means you have to have a filter that creates an instance list.

It look like you don't have one - or that its not functioning correctly or not snapped in.

How are you getting the command handler to be executed / displayed?

You could try changing the command (handlers) to be object level instead.
Make one of them the default command if you do this.

I don't know how your application is meant to function.
I think using object level RAMP command handlers is unusual - so it is possible you might have design issue that you need to address.

[Tim McEntee]

It looks like your command handler has gotten corrupted.

Under the command handler section it should have *Ramp and VF_CH001O for the component identifier.

The instance shown has Mock Up - RAD/PAd selected.

Try removing the RAMP link, then adding it again. Or removing the CH and adding it again.

Failing that contact support.