sign-requests:create - order parameter not accepted on signer flag

[ericladwig]

I have checked that the SDK documentation doesn't solve my issue.

• Yes I've checked them.

I have checked that the API documentation doesn't solve my issue.

• Yes I've checked them.

I have checked that the Box Developer Forums doesn't solve my issue.

• Yes I've checked them.

I have searched Issues in this repo and my issue isn't already reported.

• Yes I've checked them.

Describe the bug

While attempting the sign-requests:create command, if you specify a --signer with an order value, the command fails with the following error:

Unexpected API Response [400 Bad Request | 0d4fb016a69e2cae957bcec29f9f544b0.0d4fb016a69e2cae957bcec29f9f544b0] bad_request - Bad request Errors: - Name: order Message: >- should be integer (Schema path: #/allOf/1/properties/signers/items/properties/order/type; Data path: .signers[0].order) Reason: invalid_parameter

when looking at the file src/commands/sign-requests/create.js, in the case logic within the parse, the order value is not converting to a number which the Box API expects. Making the change signer.order = Number(value); allows the command to run successfully locally on my machine.

Expected behavior

When defining a signer order, the order value is accepted and the request is successful.

Steps to reproduce

Run the command declaring an order for any of the signers, e.g.

box sign-requests:create --source-files={fileId} --signer=email={email},role=signer,order=1

Authentication method used in your application

Server Authentication (with JWT)

App Access Level

App + Enterprise Access

What is Box CLI Version and Node used?

4.8.0

What is your Operating System Version?

Tahoe 26.4.1

[lukaszsocha2]

PR with the fix was merged - it will be included in the next release