Idea ID: 2834168

Set UserOptions fields via REST

Status : Accepted
10 months ago

It has to be possible to set fields of UserOptions via REST.

At the moment it is possible to use a REST call to open a request for an offering without filling in the UserOptions, even if they are marked as mandatory.
In my opinion this is a major failure.
However, in my opinion it is not enough to prevent this, but it should also be possible to order an offering via REST, just like via the portal. This includes the specification of UserOptions.

Tags:

Labels:

SMAX
Parents
  • I like the idea and I agree this is a bug (perhaps design bug) and no enhancement request. There are much more API calls faulty or missing, e.g. the response of an API call to receive a request with its user options, all user options only contain their ids and not the display value. This should also be fixed.

Comment
  • I like the idea and I agree this is a bug (perhaps design bug) and no enhancement request. There are much more API calls faulty or missing, e.g. the response of an API call to receive a request with its user options, all user options only contain their ids and not the display value. This should also be fixed.

Children
No Data