No, this does not actually transmit the data, rather it locks the data that will be submitted and moves the workflow into its final version. The submission of data to APRA takes place in the Return Management screen.
This can be configured through email configuration within the workflow function. Otherwise the Reviewer will see they have a task open within the workflow.
The task becomes re-opened for the Reviewer function to attend to again.
The reviewer of data/form is the first stage in that task and hence can not reject the task. Once they have submitted the task the approver will need to reject for them to review/update the data/form again. Whether the task is submitted or not any user assigned to their tasks can open a task for […]
The CoreBIS workflow is designed to work with users. Each user in the system has a group which is a one-to-one assignment to the user. This group is used as a proxy for the user. In the security setup a user will be defined under the GRP_User group and applied to the workflow as a […]
CoreBIS was designed this way to accommodate the most logical business flow, with a three tiered review applicable for the Form workflow.
The “Form User Assignments” screen can be updated and the workflow regenerated. This will reset all tasks, so ensure you know about the holiday in advance of the workflow setup. Alternatively the backup user can always be assigned to all the relevent tasks and only used when required.
During the workflow setup and Form User Assignments a user can not be assigned to a form/entity combination if they do not have access to it. If after the workflow is setup the user has their security adjusted then the user will still see the workflow task but will not be able to see any […]
Ensure you have been assigned to the task, and the task is at the appropriate stage for you to submit it. The Form workflow tasks can only progress once all the data workflow process are submitted.