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
  • Ideally, the REST API should be enhanced so that it becomes consistent with the way that user options can be accessed from within business rules (i.e. entity.UserOption.OptionName)

    e.g.

    {
             "entities": [{
                       "entity_type": "Request",
                       "properties": {
                                "DisplayLabel": "Test Title",

    ...

                                "UserOptions
                                {
                                        "OPTION1_c": "OPTION_1_VALUE",
                                        "OPTION2_c": "OPTION2_VALUE",
                                        ...
                                 }
                       }
             }],
             "operation": "CREATE"
    }

    Not directly related to this use case, but very similar nonetheless:
    The same could be done for complex properties (in the SACM area)

    Andre

Comment
  • Ideally, the REST API should be enhanced so that it becomes consistent with the way that user options can be accessed from within business rules (i.e. entity.UserOption.OptionName)

    e.g.

    {
             "entities": [{
                       "entity_type": "Request",
                       "properties": {
                                "DisplayLabel": "Test Title",

    ...

                                "UserOptions
                                {
                                        "OPTION1_c": "OPTION_1_VALUE",
                                        "OPTION2_c": "OPTION2_VALUE",
                                        ...
                                 }
                       }
             }],
             "operation": "CREATE"
    }

    Not directly related to this use case, but very similar nonetheless:
    The same could be done for complex properties (in the SACM area)

    Andre

Children
No Data