Component: "SigningDocumentList" - customize sequence of documents shown

[Hedda-ro]

Description

Årsregnskap desires an opportunity to customize the sequence of documents shown in this component. Ideally to reflect the user flow:

1. Schema (the PDF)
2. Attachments

(and the opportunity to hide the raw data/JSON-files if possible)🙏

Additional Information

No response

[cammiida]

Hello @Hedda-ro!

With regards to hiding documents, the component will show all documents that have be configured to be the basis of a signature in "dataTypesToSign" in process.bpmn. That is, what the user actually signs. As we see it, it would not make much sense to hide such documents since the user won't know then what they're actually signing. But feel free to challenge this!

Regarding the sorting, would it be sufficient to return the documents in the order they're defined in the dataTypesToSign tag in process.bpmn? :)

[Hedda-ro]

Hi @cammiida ,

Apologizes about timing of reply here! And thank you for following up and the questions here.

After discussing, we wish for an opportunity to still be able to hide these raw data files from this component from the end user, since the information the end user needs to confirm will be shown in the PDF/summary (and further in a more end user friendly format in terms of options etc.) :)

Absolutely, sounds good regarding how to define sorting!

[cammiida]

No worries @Hedda-ro !

We would still argue that the documents that should not be visible to the end user should not be included in the basis for the signature. Is it an option to remove it? Data would still be available in the data model if that is what you need it for? :)

[HauklandJ]

@Hedda-ro

For the setup of a signing task, the dataTypesToSign section of the signatureConfig is where the signing-package is defined. What we mean by that is simply put that the dataTypes listed here is what the Signee is asked to sign, and thus what is shown in the signing document list.
If a raw data file is not to be signed but rather a pdf, then I would suggest to leave the raw json files out of the dataTypes which are defined in the dataTypesToSign section.

<bpmn:task id="my-signing-task-id" name="my-task-name">
      <bpmn:extensionElements>
        <altinn:taskExtension>
        ...
          <altinn:signatureConfig>
            <altinn:dataTypesToSign>
              <altinn:dataType>ref-data-as-pdf</altinn:dataType>           //Skjemadata
+             <altinn:dataType>my-nice-pdf</altinn:dataType>               //DataType for PDF 
-             <altinn:dataType>my-raw-json</altinn:dataType>               //DataType for the raw data
            </altinn:dataTypesToSign>
            ...
          </altinn:signatureConfig>
        </altinn:taskExtension>
      </bpmn:extensionElements>
</bpmn:task>

Does this make sense? Did I understand the need/use case correctly?

[Hedda-ro]

@cammiida @HauklandJ Thank you for all questions and feedback :)

We do need to keep those raw data files in dataTypesToSign in process.bpmn for verification and further reception process.
Futher it also makes sense that the user should get full control of what is being signed - in this case data shown as both PDF and XML - as you suggest above.

If we are able to just customize the sequence of these documents ourselves- it is all good and this issue can be closed :)

An additional question - we now look for a way to give other descriptions in the cloumn "Vedleggstype" in the component "SigningDocumentList" - e.g. "underskjema-S" => "Selskapsregnskap". Current understanding is that the tag-property from IProcessTaskEnd is being shown in the column now. Is there a current possibility to overwrite these tags by using text resources (the config/texts-folder) at this point? Otherwise I can create a separate feature request :)

[HauklandJ]

@Hedda-ro Excellent!

There is currently no other way to configure the "Vedleggstype" for the signing document list, so a separate feature request would be great! :)

[Hedda-ro]

Ok, perfect 😊 The other feature request: #3444