Business task response structure
 
Forums / SmartComponent Library - Developer Forum / Business task response structure

Business task response structure

3 posts, 1 answered
  1. Patrik Wikström
    Patrik Wikström avatar
    68 posts
    Registered:
    15 Oct 2018
    Answered
    15 Oct 2018
    Link to this post
    Why is the dataset repeated twice in the response structure? Probably related to my other thread I opened recently (which kind of explains it), so one could assume that the first dsGetData could be plcDataset (but isn't)?
    {
        "plcParameter": {
            "SerializedType": "Consultingwerk.CharacterHolder"
        },
        "dsGetData": {
            "dsGetData": {
                "eLicenseInfo": [
                    {
                        "System":
    ...
  2. Mike Fechner
    Mike Fechner avatar
    319 posts
    Registered:
    14 Sep 2016
    15 Oct 2018 in reply to Patrik Wikström
    Link to this post
    Patrik Wikström said:Why is the dataset repeated twice in the response structure


    It is not. 

    The outermost dsGetData is the name of a property in the response. The second dsGetData is already part of Progress' serialization of the ProDataset. 

    Both nodes have the same name. But it's not repeating the dataset twice. If this irritates you, I'd implement an Adapter in the frontend wrapping the access to the JSDO to return the response parts in a format you prefer. 

    The JSDO has never been made for Business Tasks. As an alternative, check the RESTful method of invoking Business Task Methods:

    https://documentation.consultingwerkcloud.com/display/SCL/Support+for+RESTful+invocation+of+Business+Task+and+Business+Entity+Methods

  3. Patrik Wikström
    Patrik Wikström avatar
    68 posts
    Registered:
    15 Oct 2018
    16 Oct 2018 in reply to Mike Fechner
    Link to this post
    Yeah I understood that when writing the question.Thanks for the confirmation!
3 posts, 1 answered