Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-4679

[GSS](6.4.z] Unable to relate subform input/output with forms input/ouput from kie ser rest api response in BPM Suite 6.4.x

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 6.4.2
    • Business Central, Form Modeler

    • BPM Suite 6.4.2 - subforms
      Form Modeler
      Kie Server Rest API

    • Hide

      1. clone git repository to business-central;
      2. the project contains a simple process definition and some forms (task form is: issue_description-taskform);
      3. open "issue_description-taskform" and you will see that "issue" makes use of a Single Form (its mapping contains - Input :ticket/issue and Output: ticket/issue);
      3. build&deploy;
      4. create kie-server container by using GAV from project built;
      5. start the process definition by using curl:

      curl -X POST -H "Accept: application/json" -H "Content-Type: application/json" --user user:password 'http://{host}:8080/kie-server/services/rest/server/containers/{container}/processes/ticket-support.support/instances'

      6. then get task form:

      curl -H "Accept: application/json" -H "Content-Type: application/json" --user user:password 'http://{host}:8080/kie-server/services/rest/server/containers/{container}/forms/tasks/task_number?filter=true'
      Show
      1. clone git repository to business-central; 2. the project contains a simple process definition and some forms (task form is: issue_description-taskform); 3. open "issue_description-taskform" and you will see that "issue" makes use of a Single Form (its mapping contains - Input :ticket/issue and Output: ticket/issue); 3. build&deploy; 4. create kie-server container by using GAV from project built; 5. start the process definition by using curl: curl -X POST -H "Accept: application/json" -H "Content-Type: application/json" --user user:password 'http: //{host}:8080/kie-server/services/ rest /server/containers/{container}/processes/ticket-support.support/instances' 6. then get task form: curl -H "Accept: application/json" -H "Content-Type: application/json" --user user:password 'http: //{host}:8080/kie-server/services/ rest /server/containers/{container}/forms/tasks/task_number?filter= true '

    Description

      By calling 

      http://{host}:8080/kie-server/services/rest/server/containers/{container}/forms/tasks/{task_id}?filter=true

      you get taskForm_response.json (please see attachments).

      According to the dataHolder of the form, this form has one variable with the id, output_id and input_id ticket. For the subform, the dataHolder defines another variable, (with id, output_id and input_id issue). In business-central Form Modeler interface, the variable of the subform is mapped to the variable of the form (the Output and Input binding expression are set to ticket/issue - see "issue_description-taskform" from git repo attached). The kie-server's response doesn't provide this mapping, so, although you have the subform definition, you do not have the necessary information in order to relate the data of the subform with the form's.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-14 Unable to relate subform input/output with forms input/ouput from kie ser rest api response in BPM Suite 6.4.x

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              swiderski.maciej Maciej Swiderski (Inactive)
              rhn-support-ajuricic Amana Juricic
              Jan Hrcek Jan Hrcek (Inactive)
              Jan Hrcek Jan Hrcek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: