Eventing in Visual Composer 7.1 Enhancement Package 1

[Former Member]

We are running Enhancment Package 1 on 7.1 and the release note says that client side event is supported. However I build 2 iViews one with Data Entry text iput and and a signal out and the the sencond one with a signal in and a text field. I cannot get what I type in to the first iView to pass to the second. Is there a simple example that illustrates that eventing is working in this release.

[Former Member · Accepted solution]

Hi,

Plz follow the below steps to get the Eventing.

Step 1.Drag a From and adda Input field and adda Button with Cutsome action "Pass" then adda Signal out to the Form.

Right click on the line connecting between Form and Signal Out and set the Event "Pass"Ii think here you had miseed)

Step2.Drag one more fom and add a inputfield and then add the Signal in to the form.

Runa dn deploy the model once You click on the Pass button the value you had typed in Form1 WILL BE passed to second form input field.

Regards,

Govindu

[Former Member]

Hello Gretchen,

You wrote:

"add a signal out and draw a line between the form and the signal out.

Right click on the line and name it Pass

On the signal out define the name as AdhocTag and the event as com.osisoft.pct.RtPM"

You have to add a field to the signal out name it Paramname and map the value from the form's Paramname to it.

Hope this helps,

Shay

[Former Member]

Just checked Gretchen's hints using NW7.11 (EHP1) and she is right.

VC implicitly prefixes the Namespace with "urn:", so the WebDynpro has to raise Events with the Namespace explicitly prefixed with "urn:"

VC SignalIn "Client event" = de.innobis.test
=> WD Namespace = urn:de.innobis.test

VC encodes the SignalIn/SignalOut Data using XML

VC SignalOut Data-Name="Payload", Type=String, Value="Test"
=> WD receives: <Params version="3"><Row Payload="Test"/></Params>

So WebDynpro has to XML-encode/decode the Event-Payload to communicate with VC via portal-eventing.

And it's a real shame that there is literally NO DOCUMENTATION regarding this inconsistent use of urn:prefixes and XML-Encoding!

-Kai

[Former Member]

I used the non WEB Dynpro event tested with the following results.

For an iView that I had build with Visual Composer 7.0 and converted using the CE 7.1.1 converter tool I now see the following. In this case the evnt had the prefix urn: on it

10:20:12 : urn:com.osisoft.pct.RtPM, AdhocTags, %3CParamsversion%3D%223%22%3E%3CRowParamname%3D%22%5C%5Cgsrtwebparts%5Ccdt158%22%2F%3E%3C%2FParams%3E, undefined

This same iView on Visual Composer 7.0 delivered the following message using the tool in EP 7.0

10:52:46 : urn:com.osisoft.pct.RtPM, AdhocTags, <Params><param name="Paramname" value="%5C%5Cgsrtwebparts%5Ccdt158"/></Params>, undefined

For an iView that I created new with Visual Composer 7.1.1 and tried to use the same tool the tool did not catch the event and nothing was displayed in the log when the event name had urn: on it.

I rebuilt and removed the urn: and now the tool picked up the event with the following log.

11:12:29 : urn:com.osisoft.pct.RtPM, AdhocTags, %3CParamsversion%3D%223%22%3E%3CRowParamname%3D%22%5C%5Cgsrtwebparts%5Ccdt158%22%2F%3E%3C%2FParams%3E, undefined

The XML has changed and the use of urn: is inconsistent between versions.

Thanks for pointing me to this tool.

The Web Dynpro version you suggest did not show anything so that is why I tried the non-WebDynpro.

Gretchen

[Former Member]

We have figured out how to connect 2 iViews built with Visual Composer by eventing. The issue we are now having is that the XML document format that is being passed by Visual Composer has changed from prior releases and therefore if we want to consume by a non Visual Composer iView we need to figure out the new format is. We need documentation for the XML document used by Visual Composer in its event format.

Gretchen

[Former Member]

Hi Gretchen,

The XML format for the events should not have changed from NW 7.0

I would like you to monitor the data which is passed during event trigger/catch, in the following way:

1. Go to the portal Content Administration tab

2. Expand:

Portal Content -> Content Provided by SAP ->

Templates -> iView Templates -> Generic Event Tester (Web Dynpro)

3. Add the Event Tester iView to your page

With this iView you can monitor the data that is send/received during event trigger/catch.

If possible, please answer with the XML that you are receiving, and the format you are expecting.

Thanks,

Dan

[Former Member]

Still have a problem the following are the exact steps:

Create composite iView call it test12

Insert a form

Add input field to the form that has a defined value Paramname which is a string and its control is input field

Add a button to the form

On the button add a custom action called :Pass (nothing set other than the name)

add a signal out and draw a line between the form and the signal out.

Right click on the line and name it Pass

On the signal out define the name as AdhocTag and the event as com.osisoft.pct.RtPM

Create a second composite iView call it test13

Insert a form

Add an input field

Add a signal in.

Name the signal in AdhocTag and the event as com.osisoft.pct.RtPM

To the signal in define data of a string with the name Paramname

Connect the signal to the form

Added a start point

Deployed each project. Created a page and put both on the page. Entered a value on Test12 form and selected the button. Nothing was sent to Test 13 form.

Edited by: Gretchen Schwenzer on Jan 30, 2009 9:25 PM

[Former Member]

Hi Gretchen,

In the third model where you've placed the test12 and test13 i-views - did you connect the out port of test12 to the in port of test13?

If not, Please do so and then right click the connecting line --> select Map Data --> and make sure the mappings between the fields are correct.

I think the method you used was the right one in Visual Composer 7.0, in Visual Composer 7.1 signaling changed a bit.

Hope this helps.

Regards.

Omer.

[Former Member]

Hi Omer,

I think what Gretchen tried to do was to connect the iViews in a portal page. And I think what you explained is how to connect 2 nested models inside a composite view.

Regards,

Eitan