Section | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Excerpt | ||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Access Control List User Interface
Open the Access Control wizard by
Form designers as well as users with the publisher role are authorized to configure access control. The Access Control wizard makes the following permissions available for forms/flowsworkflows:
Dynamic ACLsTemplates provide the ability to dynamically determine and restrict access to submissions/ task audit trails when assigning Access Control permissions. Templates are like variables in your form that can be filled in by the user, populated by a business rule or from a back end system. Any item on the Access Control screens contained in curly braces is a form template and will be replaced with the value of the associated control. For example, the list below contains a fixed role (reviewer) and one dynamic template based role - {AcctMgrRole} : In the example discussed below, templates are used to navigate the flow workflow to the correct employee in the Accounting department and to define user lists to dynamically control access.
Who can start the form/flowworkflowSetting this permission determines who is allowed to create form/flow workflow submissions. The choices for Form/Flow Workflow visibility are:
Who can edit the form/flowworkflow
Form and flow workflow owners (designer users that created the form/flowworkflow) can give other users (designers/non-designers) the capability to edit form/flowsworkflows. This is particularly helpful if a designer user takes a leave of absence or leaves the company. The "backup designer" has the ability to make changes to the form/flow workflow without having to download the form/flowworkflow(s) from the owner's account to the backup designer's account. The "backup designer" also can view related submissions by clicking on the Submission or Legacy Submission icons. The ability to edit submissions is granted by a different permission.
Users given this permission access the shared form/flow workflow from the Shared Items tab even if they have the frevvo.designer role assigned to them. They can only edit the form/flow workflow that was shared with them. They will not have the ability to create new forms/flows workflows from the Shared Items tab. The ability to make changes to a form/flow workflow is not available from Shared Items on the Important Items menu in a space. To assign users the ability to edit forms/flowsworkflows, follow these steps:
Users that have been granted the editing permission, access forms and flows workflows that have been shared with them via the Shared Items tab on their Home Page. It will not work from the Shared Items selection in a Space or any other embedded scenario. The Who can edit the form/flowworkflow permission does not apply if you are running with Confluence. Confluence users share form/flow workflow editing by specifying the Forms Editor group on the /wiki/spaces/frevvo91/pages/901493435 screen. Users who will be sharing the editing function must be assigned to the specified group. A browser notification message displays if the user who has been granted permission to edit forms/flows workflows tries to modify their own ACL. will not allow the "backup designer" to remove themselves from the ACL list. Who can view submissionsThe designer can assign permission to view form/flow workflow submissions to specific roles/users. Any user with view access can view submissions in read-only mode. Submission deletion is not allowed. Templates can be used to dynamically determine at runtime which users and roles are allowed to view submissions. To assign permission to view submissions, follow these steps:
Who can edit submissionsThe designer can assign permission to edit form/flow workflow submissions to specific roles/users. Any user with edit access can view, edit and delete submissions in the SUBMITTED, ABORTED or ERROR states. Submissions in the PENDING, SAVED or WAITING states can only be deleted by the tenant admin, flow workflow admin or designer user that created the flowworkflow. Refer to the Deleting Submissions for more information. Templates can be used to dynamically determine at runtime which users and roles are allowed to edit submissions. To assign permission to edit submissions, follow these steps:
Who can access the audit trail -FlowsWorkflows OnlyThe audit trail is accessed on a user's Task List by clicking the View Task History icon. Roles/Users granted this permission will see theView Task History icon on tasks in their task list. To assign permission to view the audit trail, follow these steps:
Who can administer theflowworkflow -FlowsWorkflows OnlyThis permission lets a user abort, reassign and reset tasks that are not assigned to them. These administrative tasks are no longer restricted to tenant admins. The designer can delegate these tasks to additional users/roles by assigning them in the Who can administer the flow workflow section of the Access Control dropdown. Any user/roles listed here will be considered a Flow Workflow Administrator. As such, the Modify Task icon on a task in the task list will be displayed. Tenant admins and designer users get the Modify Task icon by default. To assign user/roles as Flow Workflow Administrators, follow these steps:
User jerry has been designated as a flow workflow administrator for the Expense Report but not for the Time Sheet workflow. When Jerry logs into , his task list will appear as shown: The Modify Task dialog allows a 'flow workflow admin' to execute any one of abort/reassign/reset functions. When searching for tasks, if a flow workflow is chosen, and the user is a flow workflow admin for it, then all tasks for that flow workflow display. If no flow workflow is selected, then all tasks, even those that the flow workflow admin has not participated in, plus tasks for which the user is a flow workflow admin will display. |
Shared Items
Submissions
All users granted Submission Access, either by user id or because they have a granted role, will see the Shared Item tab on their Home Page. Click on the Action menu and select Submissions or Submissions (legacy) icons to view/edit them.
You can add the Shared Item URL to your your existing Space so that a logged in user with the correct permissions will be able to access form/flow workflow submissions from the space menu. The submissions link is automatically added when you create a new space.
...
The functions needed to edit forms/flows workflows are only displayed when users given the permission access the Shared Items tab from their Home Page if they are a designer or by clicking the icon on the Task List. The ability to make changes to a form/flow workflow is not available from Shared Items on the Important Items menu in a space.
Warning |
---|
Just a reminder, edit permissions should not be given for production forms or flowsworkflows. Please see the Admin Best Practices Guide. |
The functions provided to edit forms/flows workflows from the Shared Items tab, do not include the option to delete or copy them. Deletion of a form/flow workflow is not available to the "backup designer". Forms/flows workflows can be copied by the download/upload functions. The backup designer has the ability to run the Refresh Searchable Fields process to update previous submissions with changes made to Searchable Fields by clicking on the Action Menu and selecting Refresh Search Fields. This process can be run for a for a particular form or flowform or workflow.
Let's say users Jack and Jill are both given the ability to edit the Expense report workflow. Jack logs into the flow workflow designer and begins to make changes. When Jill logs in, she will see the error shown in the image:
...
Let's consider an example to illustrate how this feature works. An Accounting Department in a company has three employees, Sue, Jack and Jill. There are three project catagories: Sales Demo, Customer Meetings and Infrastructure. Sue is responsible for processing Expense Reports for the Sales Demonstration project, Jack processes Expense Reports for the Customer Meeting project and Jill process Expense Reports for the Infrastructure project. The Accounting employees must have the ability to view and edit only the Expense Report submissions they processed. Jerry is the manager who approves/rejects the Expense Reports. He can view all the Expense Report submissions but cannot edit them. Any employee in the company can submit an Expense Report. Jerry, Jack, Jill and Sue are flow workflow administrators so you will see the Modify icon in the images of their task lists.
...
To comply with these requirements, the company designer has configured the Access Control screens for the Expense Report as shown:
Let's say Tom Cat submits three Expense Reports, one for each project type:
...
The workflow routes the three tasks to Jerry the Reviewer. It is his responsibility to approve/reject the expenses. When Jerry logs into , Tom's Expense Reports appear on his task list. The Access Control permissions above allow him to view the Audit trail for these tasks as well. Jerry approves all three Expense Reports and the flow workflow is routed to the user id specified in the {AccountUser} template in the Expense Report form. Remember, we used this template when assigning access control. The Sales Demonstration Expense Report goes to Sue for final processing while the Customer Meeting Expense Report is routed to Jack and the Infrastructure Expense Report is routed to Jill.
...
When Sue logs into , she will see tasks for any employees in the company who submitted an Expense Report for the Sales Demonstration project. Tom's will be among them. She can view the Audit trail for the flow workflow as indicated by the View Task History icon.
...
When Jack logs into , Tom's Expense Report for the Customer Meeting project will appear on his Task List along with any others submitted by company employees. Jack can view the Audit trail for the flow workflow as indicated by the View Task History icon.
...
When Jill logs into , Tom's Expense Report for the Infrastructure project will appear on her Task List. She can view the Audit trail for the flow workflow as indicated by the View Task History icon.
...
Harry is the company Technical Writer. Since the form/flow workflow visibility is set to Public in Tenant, Harry will be able to access the form/flow workflow if he needs to submit an expense report after he logs onto but he does not need permissions to view/edit the Expense Report submissions. When Harry clicks on the Shared Item tab it will be empty.
...