parses out spiffworklow:property tags in bpmn extensions and makes th… #191

danfunk · 2022-07-13T14:34:02Z

…em available as a dictionary on the task spec.

if the xml looks like this:

      <bpmn:extensionElements>
        <spiffworkflow:properties>
          <spiffworkflow:property name="formJsonSchemaFilename" value="my_json_jschema.json" />
          <spiffworkflow:property name="formUiSchemaFilename" value="my_ui_jschema.json" />
        </spiffworkflow:properties>
      </bpmn:extensionElements>

Then the task properties will be accessible here:

task.task_spec.extensions['properties']

…em available as a dictionary on the task spec. if the xml looks like this: ```xml <bpmn:extensionElements> <spiffworkflow:properties> <spiffworkflow:property name="formJsonSchemaFilename" value="my_json_jschema.json" /> <spiffworkflow:property name="formUiSchemaFilename" value="my_ui_jschema.json" /> </spiffworkflow:properties> </bpmn:extensionElements> ``` Then the task properties will be accessible here: ```python task.task_spec.extensions['properties'] ```

essweine · 2022-07-13T15:02:34Z

I would add a properties attribute to spiff.UserTask and store them there, but I am unlinely to be dealing with a random dictionary of stuff on the frontend, so I don't have a strong opinion about this.

burnettk

tested this in the backend, it didn't immediately work, added a debugger to the parser, it was never getting into your code, and realized we were importing the camunda parser explicitly. so after updating to use the spiff parser and serializer and updating expectations in the code about how the extensions would come out, things are looking good.