You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add possibility to skip finished page in case of embedded assignment.
In the future we need a solution where embedding is a feature for selected customers that can be managed in the Assignment CMS.
Temporary solution is to add embed flag to the participate url that is used by external panels: http://localhost:4000/assignment/1/participate?participant=1234&embed=true
This wil set the embedded flag which triggers the existing logic to skip the finished page. The end state will be the last page of the last task. In case of a singleton workflow (which is the mo of external panels that embed the assignment in their own workflow) a custom finished page can be implemented in the task.
The embed flag is a power user feature (we can somewhat control who uses it) and will not be shown in the url for the panel agency:
The Embedded use case is a bigger epic than only the finished page. It also needs to deal with progress callbacks in the future. This topic will be addressed later on this year.
The text was updated successfully, but these errors were encountered:
Add possibility to skip finished page in case of embedded assignment.
In the future we need a solution where embedding is a feature for selected customers that can be managed in the Assignment CMS.
Temporary solution is to add
embed
flag to the participate url that is used by external panels:http://localhost:4000/assignment/1/participate?participant=1234&embed=true
This wil set the embedded flag which triggers the existing logic to skip the finished page. The end state will be the last page of the last task. In case of a singleton workflow (which is the mo of external panels that embed the assignment in their own workflow) a custom finished page can be implemented in the task.
The embed flag is a power user feature (we can somewhat control who uses it) and will not be shown in the url for the panel agency:
The Embedded use case is a bigger epic than only the finished page. It also needs to deal with progress callbacks in the future. This topic will be addressed later on this year.
The text was updated successfully, but these errors were encountered: