Unable to assign parameters in Explorer

Support
1

I've created a project and used it successfully with explorer in earlier version of EM & server, but since the last update I'm no longer able to use a parameter (dropdown) in an explorer item when adding a row command.

When selecting the assigned value as a parameter the below dropdown is just a blank list. And I'm getting a strange error when trying to save anyway.

image
image665×204 7.42 KB

image
image675×495 18.8 KB

The project and module (selected) contain theese parameters

image
image670×587 16.9 KB

2

Workflow parameters don't become asset parameters automatically. Like with Server tasks, a computed Catalog asset can expose only some of the workflow parameters to the user.

To expose workflow parameters as asset parameters, press "Select parameters..." in the asset settings and then select the workflow parameters that should be exposed as asset parameters.

image
image1281×633 31.9 KB

The list of available parameters is empty if no workflow parameters are exposed.

3

The text of the "strange error" has been corrected. The updated version is available on our website.

4

Yes, I've tried to separate the project into 2 different assets (example below)
1 list asset
2 run asset ( several input parameters exposed)

But when I try to create a row command for asset 1 that runs asset 2, the input parameters are blank. (it seems like it's getting the input parameters from asset 1 instead of asset 2?)
Could that be the case? That input parameters should be in the asset that has the command?

5

Any Idéas here @dgudkov?
Strange thing is that it's working when we're runnning Explorer in EM Desktop. But when running it on server, the fields aren't there.
I'd be happy to setup a call to show you if possible

1 Like
6

If you create a command that runs asset B from asset A, and you want to assign the parameters of asset B with parameters (not column values) of asset A, then make sure that:

  • Asset A is a computed asset (i.e. uses a .morph file). Static dataset assets (i.e. those that use a .dset file) can also have commands, but since they don't have a workflow, they can't have parameters. Although, in this case, parameters aren't even available in the list of options.
  • Asset A has parameters declared as is my response above (by default workflows parameters are not declared as asset parameters)

I just tested it again in v5.9 - and everything works as expected. The declared parameters of asset A appear in the list.

If it still doesn't work - let's have a call and look at it together. Send me a DM for that.

7

Thank you for a fast response!
But i believe that I’ve not explained the issue clearly enough.
I’m trying to assign input parameters of asset B in this way:
User to select (dropdown) input parameter from asset B
And this is what I cannot get to work.

8

The parameters of asset B are shown on the left, not on the right.

image
image675×495 25.4 KB

If that's still confusing, let's have a call.