Properties Tab Overview
The Properties tab is the first page displayed when adding a new process or viewing an existing process.
From the Properties tab, you can:
- Enter all the details of the process including any custom fields if any exist for the project and overall instructions that apply to the entire process.
- View process details or edit them by making changes to the fields on the Properties tab.
- Allow the process to be available on the e-Builder mobile application.
- Enable offline use of the process in the e-Builder mobile application. You will then be able to work with the processes, save them while offline and e-Builder will automatically sync the process updates when you go back online.
The following are detailed descriptions of the fields located on the Properties tab:
- Process Name: Enter the name of the process in this field.
- Process Prefix: Enter a short or abbreviated name/ acronym of the process (e.g. PCO for Potential Change Order). The same prefix cannot be use more than once. The prefix shows in various areas of the product such as the Project Processes page. Once a process has been started by a user the prefix can no longer be edited.
- Description: Enter notes or a description of the process. The description is shown on the Start Process page to give users direction on which process they need to start.
- Active: When a process type is first created it is set to not active. When set to active all users that have permission are able to fill one out.
Leave the process type inactive when configuring the process to prevent any users from accessing a process type that is not completely configured.
- e-Builder Mobile Enabled: Select this check box to make this process available in the e-Builder app on any mobile device.
Cost processes are not currently available on mobile devices. If you intend to make this a cost process, do not select this check box, otherwise, the cost options will not display on the Data tab.
- e-Builder Offline Mobile Enabled: Select this check box to allow users to login to the e-Builder mobile app while offline. If the user is using SSO or MFA, then they will be able to login using a biometric profile that has been linked to their e-Builder user account.
This check box will be displayed and available for selection only if the e-Builder Mobile Enabled check box has been selected first.
When this option has been enabled, the Attached Documents Default Folder Path field becomes mandatory. You will need to specify a folder path for offline use in that field.
- Map Location Enabled: Select this check box to allow users to set the process location on a map. You can set permissions to view or edit on the Page Layouts tab.
- Enable the Ability to Delegate Work: Select this check box to allow the actor(s) in the step the ability to delegate work. This applies to all steps in the process.
- Instructions: Enter generic process instructions that apply to the entire process. Remember, you are also able to add step-specific instructions for each step in the process. You can type directly into this box or paste text from a word processing application. Pasting tables is also permitted. From the user's perspective, these instructions show up in the top right corner of the process as a help button in the form of a question mark. When selected, instructions display in a pop up window.
- Allow comments to be deleted:This setting determines whether or not comments are allowed to be deleted by either the commenter or an administrator (account admin, project admin, or users with Manage Workflow permissions). Users will be able to see that there had been a comment, but it was "Deleted." If necessary, deleted comments can be overridden by an administrator (account admin, project admin, or users with Manage Workflow permissions).
- No (Account Default): By default this setting is disabled. Leave this radio button selected to keep this setting disabled.
- Yes: Select this radio button to enable this setting.
- Project(s) using this process: Select from the following options:
- All projects: Select this option to assign this process to all projects.
- All Projects except the following blocked projects: Select this option to create a blocked list of projects to exclude this process from.
- Only the following selected projects: Select this option to create a list of projects to assign this project to.
- Projects filtered by one or more custom fields: Select this option to assign this process to projects filtered by one or more custom fields. For example, a project could have a custom field called region and a sample project could have a value east. A process can be configured so that it is only available in those projects where the region is equal to east.
- Allow external uses to view attached forms and processes when external comment is requested: Select from the following options:
- Yes - Select to allow external participants to view forms and processes that have been attached to this process when external comments are requested. This would only allow them to view attached forms and processes up to one tier.
- No - Select to prevent external participants from viewing forms and processes attached to this process when a comment is requested by them.
- Who can start this process?: Set permissions on who can start the process; possible values are all users, selected roles or no users.
One use case for not allowing anyone to start this process is if it will be spawned from another process.
- Who can view drafts of this process: If this process spawns another, this setting will be set to No Users by default, as a draft can not be created of a spawned process. To learn more, see About Spawned Processes. Draft processes are created for many different reasons. At times, team members do not remember to use a draft process and create a new one or co-workers who are unable to see the draft processes of others do not know the draft exists and submits a new process for the same item. Draft process will be accessible from the Unfinished Drafts page.
Any person or role given the ability view draft processes will automatically be given the ability to start the process, if they do not already have this permission.
Set permissions on who can view drafts of this process from the following options:
- All users selected for start process: Select to give view draft rights to all users that have the ability to start the process.
- Selected roles: Select to restrict the viewing of drafts to select roles.
- No users: Select to prevent everyone from viewing draft processes.
- Who can view all process instances?: Set permissions on who can view the instances of this process.
- All users - This is the default option. Select to give all project participants the ability to view instances of this process.
- Selected roles - Select to restrict viewing of process instances to select roles.
- No users - Select to prevent anyone from viewing process instances.
- Who can report on this process: Set permissions on who can report on this process.
- All users: This is the default option. Select to give all users the ability to report on this process.
- Selected roles: Select to allow only certain roles to report on this process.
- No users: Select to prevent any user from reporting on this process.
- Who is notified as the process moves between steps?: Make a choice to set automatic email notifications as the process moves between steps; possible values are all users, selected roles and no users. By default the value is set to no users.
Be careful when setting this control to a set of users. The amount of emails received can be abundant.
- Who can view/ add private comments for this process?: These are controls that allow you to set who can see the comments. If the comments are marked private, only those users selected to be able to see the comments may see them. If the comments are marked public, all users may see them.
- Set Comments to Private by default: This check box becomes active when a role is selected in the previous field (Who can view/ add private comments for this process?). Select this check box to automatically set comments to private by default, giving users the choice to clear this check box and make comments public.
- Lookup Fields: Lookup fields are standard options that allow you to pull data from the Cost module. These fields show up on the dependent process tab after the dependent process has been linked to a primary process as an audit trail and for quick viewing access. For more information on lookup fields, see About Lookup Processes.
- Process Lookup Tab Name: Enter a name for the process lookup tab in this field. If this process has dependent processes linked to it, this name (the primary process name) will display when users hover over the dependent process tab on the process details page.
- Default Sort: Selections in this field are directly related to options that have been selected in the Lookup Fields section above it. Click this drop-down arrow to select a field that these options will be sorted by default.
- Attached Documents Default Folder Path: Click Browse to set a default folder path for documents attached to this process type. This feature will apply to all projects.
- Allows users to place the file in a different folder: Select this check box to allow team members to make a different folder selection at the time of upload.
Click Remove Folder to remove the folder path.
The following are detailed descriptions of the buttons located on the Properties tab:
- Delete Process: Click to delete the process, including process instances; or to delete process instances only. For detailed steps on deleting a process, see Delete Processes/Instances.
Deleted processes cannot be recovered.
This button is displayed only for account administrators, project administrators and users with manage workflow permissions.
The following are dependencies that will prevent a process from being deleted:- The process is used in a data field process lookup.
- The process is used in a custom report type
- The process is used in a dynamic cost column
- Copy Process (View Mode): Click this button to create a duplicate of the process. The copied process will include every object in the process such as layouts, data fields, and published workflows only; saved and auto saved workflows will not copy over. By default, the copied process will be inactive. You must edit project properties to make it active. For more information, see Activate a Process.
- Edit (View Mode): Click this button to modify process properties.