John, when you say “the second input didn’t come through”, can you elaborate on that? Are you using “skuid.events.subscribe” to subscribe to the event, and if so, can you share your code that you’re using?

When I subscribe like this:

skuid&#46;events&#46;subscribe("acme&#46;page&#46;resize", function(config, eventDetails) {<br />   console&#46;log(config);<br />   console&#46;log(eventDetails);<br />}); 

And then publish like you were doing initially, everything works as I’d expect:

var config = {``` doSomething: true<br />};<br />var eventDetails = {<br /> direction: 'vertical'<br />}; <br />skuid&#46;events&#46;publish('acme&#46;page&#46;resize',pconfig,eventDetails]);

I’m using a declarative action sequence to subscribe to the event, the idea being to kick off an action sequence from a link (i.e. from a url or div in a template), but keep the logic declarative by leveraging the action sequence. This may be a nuance with how the action sequence handles the subscription or not understanding the full structure of the data array of the event api.

I may not have fully picked up on how this is supposed to work, but what I was seeing is that in the example provided in the documentation, two objects are passed into the data array in the publish API. The action sequence only picked up the first object as an input parameter. When I switched this to one object with two key value pairs, the action sequence picked up both.

i.e. change:

config = {

doSomething: true

};

var eventDetails = {

 direction: ‘vertical’ };  skuid.events.publish(‘acme.page.resize’,rconfig,eventDetails]);

to:config = {


doSomething: true, direction: ‘vertical’ };  skuid.events.publish(‘acme.page.resize’,mconfig]);

I figured this might be a minor documentation issue, which took a couple hours to work out, so I thought I would spare others.  Here's a screenshot of the different outputs:





This worked as I would expect:

<img src="//cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/skuid/original/2X/9/9c7b94525b08f576de8a114424834f402622bfcb.png" alt="" title="Image httpsd2r1vs3d9006apcloudfrontnets3_images1742887RackMultipart20180726-9119-esq9g3-Capture2_inlinePNG1532644750" name="" value="" type="" target="" rel="">



The action sequence only picks up parameter1:

<img src="//cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/skuid/original/2X/e/e98c30d58e785ac0645344205cac91b814e8f589.png" alt="" title="Image httpsd2r1vs3d9006apcloudfrontnets3_images1742886RackMultipart20180726-4226-12xtw98-Capture_inlinePNG1532644613" name="" value="" type="" target="" rel="">

I think I’ve connected the dots on this.  Is is safe to say that the action sequence is expecting all of the parameters in one object, but that the publication event can be extended when working with the subscribe API?  So you could define your publish action with this type of structure:

skuid.events.publish(‘EventName’,N 
   {  Parameter1:ParameterValue1,
      Parameter2,ParameterValue2,
      Parameter2,ParameterValue3
   },
{AnotherArgument:ArgumentValue}
]);

John, yes that is correct, Event-triggered Action Sequences only pick up the first argument, and the argument is expected to be an object of key-value pairs. When you use the “Publish Event” action, each Parameter that you define will be incorporated as a key-value pair into a single JavaScript object which will be sent to subscribers as a single argument, as you have shown above, e.g. { Parameter1: ParameterValue1, Parameter2: ParameterValue2 }. When you define Event-triggered Action Sequences, you can declare expected Inputs to the sequence, with each Input’s Name/Value mapping to the parameter names/values that were published.

When you use the publish/subscribe API via JavaScript, you have more flexibility to publish multiple arguments and have subscription functions pick up on the additional arguments.