Datatransfer across WDcomp and screen refreshing ...

[alfred_behrends68]

Hello!

I'm looking for a solution on this scenario:

WDComp A has an InputField.

WDComp B has a TextViewField which shows modified text depending on the input and replaces WDComp A.

A "uses" B and I can transfer the InputField via external mapping and show the modified text.

Which is the best way to handle

- a navigation back to A,

- changing the InputField and

- refreshing the view from WDcomp B?

Right now I'm only able to do this by creating and destroying comp B (conrolled from A).

Can I get a parameter transferred to comp B via eventing,

although the use-relation is "A uses B" (and not B uses A, like in the tutorial)?

Thanks in advance

Alf

[Former Member · Accepted solution]

Alfred,

Which is the best way to handle

- a navigation back to A,

<i>Via pair of outbound(B interface view) and inbound (A view) plugs, link between them (window of A), event handler in B, and invoking plug in event handler.</i>

- changing the InputField a

<i>If you have "external mapping" of context, then you may alter context attribute on either side (A or B), value will be in sync (mapping works in both ways)</i>

- refreshing the view from WDcomp B?

<i>Could you explain?</i>

Valery Silaev

EPAM Systems

http://www.NetWeaverTeam.com

[alfred_behrends68 · Accepted solution]

>> Which is the best way to handle

>> - a navigation back to A,

> <i>Via pair of outbound(B interface view) and inbound

> (A view) plugs, link between them (window of A),

> event handler in B, and invoking plug in event

> handler.</i>

OK, I can understand this )

>> - changing the InputField a

> <i>If you have "external mapping" of context, then

> you may alter context attribute on either side (A or

> B), value will be in sync (mapping works in both

> ways)</i>

OK, can see that too ...

> - refreshing the view from WDcomp B?

> <i>Could you explain?</i>

I need to modify the transfered value before displaying it. This currently happens in comp B (internal).

It's not sufficient to just bind the context attribute to the view (for self refreshing).

Thanks again.

Alf

[alfred_behrends68 · Accepted solution]

Ok,

I think I just got the kick.

It's all about the eventing Tutorial.

After doing this step-by-step it works for me.

Thanks,

Alf