Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-9470

User Task output variable mapping to an object attribute

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Critical Critical
    • 7.47.0.Final
    • None
    • Runtime Engine
    • None
    • False
    • False
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • NEW
    • NEW
    • 0
    • 0% 0%
    • Undefined
    • ---
    • ---

      When we have an object as a process variable (eg. applicant, of type Applicant), and we want to modify a specific attribute of that object (eg. applicant.name ), see the following screenshot:

      Unless we expose the whole applicant object in the task output mapping, like in the following screenshot, we are not able to only modify just the name attribute of the applicant object. 


      This has two major flaws:

      • Security-related: we expose the whole Applicant object to be eventually modified, instead of a specific attribute.
      • process/task self-documentation: we can't visually know what is exactly the information that we need to add/modify in this User Task

      Can we enable the usage of mvel expressions in the Target field of the mapper, to notify the engine to assign name to applicant.name?

       

       

            ftirados Francisco Javier Tirado Sarti
            ftirados Francisco Javier Tirado Sarti
            Antonio Fernandez Alhambra Antonio Fernandez Alhambra (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: