a) What would be the max and minimum values. (Assumption 0 so it is controlled by the org)
b) How can we differentiate between different messages in the same instance.
How to instantiate an instance with a message
We would use the Post Method on instance controller to instansiate it.
a) How is Process moved to first task? (Is this already handled?)
b) What about data. Can we instantiate without any data? We probably need to update.
How to present message view
App frontend would need to be updated to support presenting the correct view when instance is in message task.
a) Instance is instantiated with a message and task status is the message
How to instantiate a form as a response to a message
How can we let the user instantiate a form from the message and move to the data task in the BPMN Process
How to go to a form that is already instantiated.
How can a user be redirected from the message task to a data task with a given dataid.
How to update read status on a correspondence message?
Do we need read status?
How can we present a message from the archive?
For regular receipt we show receipt application with pdf. Should we do the same with message
How to support multiple messages.
There will be instances with multiple messages.
Do we need to mark them in specific way. To we need to be attached to a specific task?
How to support attachments
It should be possible to add links to other data elements so they can be shown as attachments
How to prevent overwrite of message
We need to clarify what is the standard behavior when it comes to deleting and overwriting of the message and attachments related to that message. Should it be allowed?
The assumption is that it would not be allowed. The delete method should check if the data element is a message and if so not allow the deletion of it.
How to prevent message attachment deletion
In the same way on deletion of dataelement we should check if it is referenced in a message.
How to prevent deletion of a message
We need to define if it is possible to delete a message from org.
Description
As part of #1330 we have defined that we need to support messages as part of an instance
The UX has not been finalized, but there are some technical issues that need to be resolved even if not all details are in place.
This analysis needs to identify those and suggest a solution
Considerations
What are the scenarios supported?
Type of BPMN Task
The type of BPMN task needed to be supported is suggested to be called "message"
This task would require Read right to read the message.
We need to decide what is the right needed to move forward in that process.
How to define the message datatype
In the below Applicationmetadata.json there is defined a datalement with type altinnmessage.
a) What would be the max and minimum values. (Assumption 0 so it is controlled by the org) b) How can we differentiate between different messages in the same instance.
How to instantiate an instance with a message
We would use the Post Method on instance controller to instansiate it.
This method parses the multirequest including all attachments in the [ExtractrInstanceTemplateMetod]https://github.com/Altinn/altinn-studio/blob/master/src/Altinn.Apps/AppTemplates/AspNet/Altinn.App.Api/Controllers/InstancesController.cs#L575)
a) How is Process moved to first task? (Is this already handled?) b) What about data. Can we instantiate without any data? We probably need to update.
How to present message view
App frontend would need to be updated to support presenting the correct view when instance is in message task.
a) Instance is instantiated with a message and task status is the message
How to instantiate a form as a response to a message
How can we let the user instantiate a form from the message and move to the data task in the BPMN Process
How to go to a form that is already instantiated.
How can a user be redirected from the message task to a data task with a given dataid.
How to update read status on a correspondence message?
Do we need read status?
How can we present a message from the archive?
For regular receipt we show receipt application with pdf. Should we do the same with message
How to support multiple messages.
There will be instances with multiple messages. Do we need to mark them in specific way. To we need to be attached to a specific task?
How to support attachments
It should be possible to add links to other data elements so they can be shown as attachments
How to prevent overwrite of message
We need to clarify what is the standard behavior when it comes to deleting and overwriting of the message and attachments related to that message. Should it be allowed?
The assumption is that it would not be allowed. The delete method should check if the data element is a message and if so not allow the deletion of it.
How to prevent message attachment deletion
In the same way on deletion of dataelement we should check if it is referenced in a message.
How to prevent deletion of a message
We need to define if it is possible to delete a message from org.
Could we add a flag to datalement to as readonly
How to support senders information on a message
We need to define how the sender of a message can be sent. In Altinn 2 this is disconnected from the org.
How to support archiving of instance when submitting form is an option
If this is required we would need a way to
Deletion of messages Multiple messages?
Tasks
Development task