Arguments not visible in Deployed Process!

Feedback Studio Web
, , , , , , ,
1

I converted a project that was initially deployed without any input arguments into a process with 3 input arguments.

image
image1530×737 32.9 KB

The process version was changed to v2.0.1 make sure of this major enhancement during deployment:

image
image1520×1205 81.2 KB

But when the package is deployed to Orchestrator, the v2.x of the process does not reflect the process arguments! :neutral_face:

Is this because I converted an existing cross-platform process and changed it’s entry point signature?

image
image3060×1270 164 KB

Thanks

2

Subsequently, I scratch built a basic process with 2 In arguments and 1 out argument.
On deployment, the process arguments still do not show up!

Is this a bug? Or am I missing something?

image
image2917×1235 136 KB

image
image2880×1035 142 KB

Thanks

3

@AndyMenon , this is a bug, thanks for reporting. Please expect a fix to be deployed today.

4

Thanks for the update @Cosmin_Popescu !

Eagerly awaiting the fix.

5

@AndyMenon we deployed a fix for this issue, check it out :relieved:

1 Like
6

Yep! It works! :slight_smile: One thing to note is the fix is not applicable to already deployed automations. I had to redeploy it once more to see the fix.

In addition, I modified the process to test an In/Out argument. Results below:

image
image980×910 31.1 KB

image
image1475×500 48.1 KB

Thanks @alinvelea! :+1:

2 Likes
7

You are right, this is not applicable to already deployed automations, this was intentional. Taking into account that we are in a preview state we haven’t backfilled existing deployments.

8

Understood. Not an issue at this moment.

Thanks for the update.

1 Like