Workspace-level and Project-level Form Assignments for Risk Forms
After you have set up a custom form with the right context type to replace a default form for risks, you must decide whether to replace it at the project level or the workspace level.
Project-level Custom Form Assignments
You can assign forms at the project level to take the place of default system forms or forms that exist at the workspace level. There are two ways a workflow can be assigned at the project level.
- You can assign the form directly to objects and actions at the project level, or
- You can assign the form to objects and actions at the workspace level, and then you can have all projects within that workspace inherit the form assignment.
Either way, form assignments must eventually make it to projects in order to have any effect. So, the easiest and most direct way to assign custom workflows for one project is at the project level.
Assign a Custom Risk Form at the Project Level
Workspace-level Custom Form Assignments
If you have several projects in a workspace and you want a form assignment to take effect for all of the projects in that workspace, then you can assign a form at the workspace level. After that, you can have all of the projects in the workspace inherit the form assignment.
This is a convenient way to assign forms for multiple projects at once, but in order for a workspace-level form assignment to take effect for a project within the workspace, you need the privileges required to edit that project.
Assign a Custom Risk Form at the Workspace Level
Last Published Tuesday, May 21, 2024