Progressus Project Setups
To complete setup for items related to Progressus Projects, use these links to view help files for related set up pages:
Topic | Link |
---|---|
Items & Expenses Setup | Items & Expenses Setup |
Project Posting Groups | Project Posting Groups |
Work Types | Work Types |
Cost Types | Cost Types |
Project Codes | Project Codes |
Billing Cycle | Billing Cycles |
Tax Posting Setup | Tax Posting Setup |
Configure Progressus Project Setup
The settings selected in Progressus Project Setup establish the setup, structure, and parameters the system uses for all Project transactions.
Number Series
The Number Series FastTab is used to set up the unique identification Codes, with starting and ending numbers for a variety of objects used in processing Project transactions. Codes should be set up with no spaces or gaps. For more information see: Create Number Series
Create Number Series Codes for the following categories. The numbering sequence is then added onto the Code to create sequentially numbered Projects, Budgets, etc. To see the available Number Series for all fields, use the drop-down arrow in the field and click on Select from full list.
Field Name | Description |
---|---|
Project No | Specifies the Code for the Number Series that will be used to assign numbers to Projects. |
Contract Nos. | Specifies the Code for the Number Series that will be used to assign numbers to Contracts. A Contract can be set up to group multiple Projects for billing, reviewing budgets, usage, and sales postings. Each Project is associated with a Task on the Contract Plan. |
Income Analysis Nos. | Specifies the Code for the Number Series that will be used to assign a number to Income Analysis. Used for cross-Project reporting. |
Active Budget Version | Specifies the Code that will be used as the default for the Project Active Budget. |
Resource Factor | Specifies the Code for the Number Series that will be used to assign numbers to Resources. |
Calculate WIP No. | Specifies the Number Series to use when calculating WIP. |
Post WIP No. | Specifies the Number Series to use when posting WIP. |
Progress Billing Nos. | Specifies the Code for the Number Series that will be used to assign numbers to Progress Billing Applications. |
Invoicing
The Invoicing FastTab contains the basic setup defaults for invoicing and General Product Posting Groups and includes the following fields:
Field Name | Description |
---|---|
Gen. Prod. Posting Group | Use the arrow to display a list of General Product Posting Groups. The posting groups designate the General Ledger Accounts used for project transactions. |
Note
The necessary accounts in the Chart of Accounts must be set up before Posting Groups are created. For more information, see Set Up or Change the Chart of Accounts
Inv. Rounding Precision | Used when client is working in different currency than the company currency. If the exchange rate changes between when the usage entry is created and when the entry is billed, and there is a difference between sales value and usage value, the system will close any records below the value entered in this field. Currency translation of payments can result in a rounding discrepancy between the usage amount and the sales invoice line. The rounding precision is used to allow the payment to close when the invoice is posted. |
Tip
On the Currencies page, you specify how to round invoices in foreign currencies.
Use Enhanced Invoice Processing | Specifies that the new Create Invoice process will be used. This will become mandatory in the future. |
Summary Sales Line | Specifies how document line detail will be stored. |
All | If this field is set to All, then all lines related to a sales document are stored in the Document Line table. |
Summary Only | If this field is set to Summary Only, then lines which are not visible on the document, due to grouping, are stored in a separate table. The Summary Only option is useful for data handling related to external electronic document interchange and document printing applications. |
Price Equal to Payment | Specifies, if selected (true) to use validation when setting up the Payment Plan. The Sold Amount on the Progressus Project Card and Sales Price must equal the Payment Plan value. |
Payment Plan Value | Select the default for the Payment Plan Value for Projects. Options are: |
None: No default | |
One: One single payment | |
Repetition Period: Repeating payments. | |
Use Scheduled Billing Budget Cost | Specifies how the Project Task Scheduled Billing Budget Costs will be stored and how the Project Task Completion Percent is calculated for the related Milestones. |
If this option is selected, budget entries for Scheduled Billings will be created with the cost amounts set from the Scheduled Billing Cost values. | |
When the Calculate Completion % is performed for Milestones, the Total Budget Cost for the Milestone Task will be based on the cost values of the related Scheduled Billing records. | |
If this option is not selected budget entries for Scheduled Billings will be created with cost values set to zero. It is assumed that Budget Entries are created for cost using other methods such as Budget Matrix or Journal. When the calculate completion % is performed for Milestones, the Total Budget Cost for the Milestone Task will be based on the cost values found in Budget Entries. | |
Use Invoice Currency Code | Specifies, if selected (true), to use the Progressus Project Card Invoice Currency Code on the invoice. This is important if the Customer's Currency Code is different than the Project Currency. If this option is not selected, then the invoice will be created with the Customer's Currency, unless Used Posted Currency is selected on the Progressus Project Card, Invoicing FastTab, for Resource, Item, and/or Expense. |
Use Sales Account When Applying Invoice | Specifies, if selected (true) to use the Purchase Account instead of the Sales Account from General Posting Setup. |
Resource Invoice Type | Specifies the default for Resource Invoice Type on Project creation. Options: |
- Fixed: Specifies that invoicing for Time will be at an agreed, contract price. Invoicing may or may not be associated with a Scheduled Billing. | |
- Time/Material: Specifies that invoicing will be for the actual price for Time. | |
- Percent Complete: Specifies the invoicing will be based on the completion percentage of the Project. The calculation of the Percent Complete for the billing line will be Actual Total Cost/Budget Total Cost or Actual Quantity/Budget Quantity, depending on the Percent Complete Basis (cost, or quantity) for the Project. | |
Item Invoice Type | Specifies the default for Item Invoice Type on Project creation. Options: |
- Fixed: Specifies that invoicing for Items will be at an agreed, contract price. Invoicing may or may not be associated with a Scheduled Billing. | |
- Time/Material: Specifies that invoicing will be for the actual price for Items. | |
- Percent Complete: Specifies the invoicing will be based on the completion percentage of the Project. The calculation of the Percent Complete for the billing line will be Actual Total Cost/Budget Total Cost or Actual Quantity/Budget Quantity, depending on the Percent Complete Basis (cost, or quantity) for the Project. | |
Expense Invoice Type | Specifies the default for Expense Invoice Type on Project creation. Options: |
- Fixed: Specifies that invoicing for Expenses will be at an agreed, contract price. Invoicing may or may not be associated with a Scheduled Billing. | |
- Time/Material: Specifies that invoicing will be for the actual price for Expenses. | |
- Percent Complete: Specifies the invoicing will be based on the completion percentage of the Project. The calculation of the Percent Complete for the billing line will be Actual Total Cost/Budget Total Cost or Actual Quantity/Budget Quantity, depending on the Percent Complete Basis (cost, or quantity) for the Project. | |
Sales Order Invoiced | Specifies the options for billing when a Sales Order is created. Options: |
- At Shipment: Specifies that the invoice is to be sent at the time of the shipment. | |
- Through Project: Specifies that the invoice is to be created through the normal project billing. | |
Sales Order Creates Usage | Specifies, if selected (true), that the system will create a Project Ledger Entry for Usage, at posting. This only applies to Items, not Resources or Expenses. |
Sales Invoice Creates Usage | Specifies, if selected (true), that the system will create a Project Ledger Entry for Usage, at posting. This only applies to Items, not Resources or Expenses. |
Resources % Complete | Specifies if selected (true), that Resource Usage is to be included in Percent Complete calculation for billing. |
Items % Complete | Specifies, if selected (true), that Item Usage is to be included in Percent Complete calculation for billing. |
Expenses % Complete | Specifies if selected (true), that Expense Usage is to be included in Percent Complete calculation for billing. |
% Complete Override | Specifies if the user can override the calculated Percent Complete for billing. |
% Complete Based On | Specifies the calculation value on which Percent Complete is based, as quantity or cost. |
% Compl. Billing Level | Specifies the default level for Percent Complete billing as the entire Project or each Task and at the Summary or Detail level. Options: |
- Project Summary | |
- Project Detail | |
- Task Summary | |
- Task Detail | |
- Not Applicable | |
% Complete Task | Specifies the Task to use when doing Percent Complete billing for Project Summary or Project Detail billing levels. Project billing does not get posted to the individual Tasks, just to one designated Task. |
WIP & Allocations
WIP & Allocations FastTab defines the parameters to be used in WIP and Allocations transactions and includes the following fields:
WIP
Field Name | Description |
---|---|
Allow change entries with WIP | Once WIP has been calculated, select this option to allow user to adjust the WIP entries before posting. |
Allocations
Field Name | Description |
---|---|
Allocation Batch | Specifies the numbering sequence used for Allocation batches. |
Automatic Calculations | Specifies, if enabled, that Allocations happen as each transaction is posted to the Project Ledger, if not enabled, Allocations are processed when the Allocation process is run. |
Allocation Task Template | Specifies the Allocation Task Template to use in Allocation Multi-Level Rate Entry. Set up this new template under Setup > Template Setup > Task Templates. For more information see: Create Task Templates |
Important
The Allocation Task Template must contain ALL Task Nos. used for Projects. It is a listing of every Task No. from every Task Template. Copy all lines in a Task Template and paste into Excel worksheet. Copy just the column with the Task No. and paste into a new template. The Description field can be populated but is not required. No other fields/settings are necessary.
EXAMPLE Results: the numbers from 2 separate templates combined to create the Allocations Task Template.
Capacity
Capacity FastTab defines the parameters to be used in capacity planning for Resources and includes the following fields:
Field Name | Description |
---|---|
Limit of Time Reg. (Years) | Enter the number of years for calculating capacity. This setup option is used on the Update Capacity page. If you select Total Update, when this activity is started the system will update the capacity on all active Resources based on their norm time as well as the number of periods defined in this field. |
Period/Type | Select the Period Type to be used as the default when viewing Capacity. Options: |
- Date | |
- Week | |
- Month | |
- Quarter | |
- Year |
Time and Expense Registry
The Time and Expense Registry FastTab is used to define the defaults for Time and Expense Entry in the system and includes the following fields:
Field Name | Description |
---|---|
Appr. can Edit Time & Expense | Enable this option if approvers are allowed to edit time and/or expense during the approval process. |
Time
Field Name | Description |
---|---|
Use Modern Timesheets | Specifies that the Modern Timesheet experience will be enabled. This includes the option to enter timeline by line or in a matrix. |
Use Time Jnl for Timesheet approval and posting | Specifies that the Time Journal will be used to post approved Timesheets instead of the Progressus Project Journal. |
Time Reg. Journal Template | A Time Register Journal is created when the Timesheet is approved. This setup defines the journal template used to create the time posting entries. |
Time Reg. Batch | Select the code to be used for the Time Register Batch for Time Entries. |
Post When Approving Time | Select this option to post to the Project Ledger when approving time. Deselecting this means that posting will need to be done as an additional step. To post the Time Journal, navigate to the Role Center > Journals, choose the appropriate journal for the time and choose Post. |
Auto update Dim. Time entry line | Select this option to enable automatic update of Dimensions when you change the Dimension on a Project. If not enabled any open Timesheets/Entries/Journals would need to be manually updated. If selected, the next time you open the Timesheets/Entries/Journals, the Dimension will be updated to the new Dimension on the Project. |
Limit Time Entry Project List to Permissions | This is to set up the default configuration for new Projects created. If this box is checked the new Project will also have this box checked. This default can be modified on the Progressus Project Card. Specifies, if enabled on the Progressus Project Card, that Resources or Resource Groups are prevented from selecting the Project in the lookup from the Timesheet. Only those Resources or Resource Groups added to Project > Permissions with Timesheet rights will be able to choose the Project for time entry. |
Limit Time Entry Task List to Permissions | This is to set up the default configuration for new Projects created. If this box is checked the new Project will also have this box checked. This default can be modified on the Progressus Project Card. Specifies, if enabled on the Progressus Project Card, that Resources or Resource Groups are prevented from selecting the Task in the lookup from the Timesheet. Only those Resources or Resource Groups added to Project > Permissions with Timesheet rights will be able to select from the Task list for time entry. Additionally, there is an option to limit choosing individual Task Codes for a Timesheet. |
Post Time Entries to GL | Select this option to allow Time Entries to post to GL. |
Update Time Entry Dimensions | Specifies the handling of Dimensions on time entries when Dimensions are changed, e.g., from changing the Project. Options: |
- Prompt User: Displays a message giving the user a choice as to updating the Dimensions. | |
- Always: Change the Dimensions without a message. | |
- Never: Do not change the Dimensions or display the message. |
Expense
Field Name | Description |
---|---|
Use Exp Jnl for Expense Sheets | Specifies that the Expense Journal will be used to post approved Expense Sheets instead of the Progressus Project Journal. |
Expense Reg. Journal Template | An Expense Register Journal is created when the Expense is approved. This setup defines the journal template used to create the expense posting entries. |
Expense Reg Batch | Select the code to be used for the Expense Register Batch for Expense Entries. |
Expense Sheet Nos. | Select the Number Series for the Expense Sheet. |
Post When Approving Expenses | Select this option to post to the Project Ledger when approving expenses. Deselecting this means that posting will need to be done from the Expense Journal. To post the Expense Journal, go to the Role Center > Journals, choose the appropriate journal for the expense and select Post. |
Above Mileage Post not allowed | Select this option to prevent expense entry for mileage above the limit. The limit is set on the Progressus Project Card of the Project. |
Use default mileage on customer | Select this option to only use the default mileage on the customer and do not allow override during entry. |
PDF Viewer URL | Specifies the URL to use for the PDF File Viewer on attachments. |
Create Project
Use the Create Project FastTab to define the defaults when using the Create Project Wizard. The following fields are available:
Field Name | Description |
---|---|
Project Posting Group | Specifies the posting group that links transactions made for the Project with the appropriate General Ledger Accounts according to the General Posting Setup. |
Contact Related to Customer | Specifies, if selected (true) that the system will require that contacts must be related to the selected customer to be used in Project creation. |
Job(Project) Dimension | Specifies which Global Dimension is used for job (Project) identity. Options: |
- None | |
- Global Dimension 1 | |
- Global Dimension 2 | |
Create Job Dim. Value | Specifies that the number on a job (Project) will automatically be created as a Dimension value and assigned as a default Dimension on the Job (Project). |
Create Project Integration | Depending on the option selected, the CE Opportunity, the Progressus Project, or the Progressus Import Project line will be created as follows: |
- Option 1 | - None: No action is taken. |
- Option 2 | - CE Opportunity to Progressus Project: Specifies that a new Progressus Project will be created from the CE Opportunity when the CE Opportunity is designated as Won. The Project is created with a Status of Planning. |
- Option 3 | - CE Opportunity to Progressus Import Project: Specifies that a new line will be inserted into the Import Projects page when the CE Opportunity is designated as Won. |
Important
If Option 4 or 5 is required, then the Setup Integration for Dynamics 365 Sales is required.
- Option 4 | - CE Opportunity to BC CRM Opportunity & Progressus Project: Specifies that a new Business Central CRM Opportunity and a new **Progressus ** Project will be created from the CE Opportunity when the CE Opportunity is designated as Won. The Project is created with a Status of Planning. |
- Option 5 | - CE Opportunity to BC CRM Opportunity & Progressus Import Project: Specifies that a new Business Central CRM Opportunity and a new line will be inserted into the Progressus Import Projects page from the CE Opportunity when the CE Opportunity is designated as Won. |
- Option 6 | - BC CRM Opportunity to Progressus Project Card: Specifies that a new Progressus Project Card will be created from a Business Central CRM Opportunity when the BC CRM Opportunity is designated as Won.The Project is created with a Status of Planning. |
- Option 7 | - BC CRM Opportunity to Progressus Import Project: Specifies that a new line will be inserted into the Progressus Import Projects page from the BC CRM Opportunity when the BC CRM Opportunity is designated as Won. |
Effective Date | Specifies the Effective Date for the Project created from the Opportunity. If the user chooses an option in Project Setup > Create Project FastTab > Create Project Integration <> NONE, they will be required to enter an Effective Date. |
The Effective Date will be used to compare to the date the Opportunity was WON. If it is before the Effective Date,the integration will not create the Project from the Opportunity. If the WON date is > or = Effective Date, the integration wil create the Project from the Opportunity. |
Tip
All the integrations create the Project in Progressus when the Business Central Job Queue is run. The appropriate job queue is enabled with the above selection. The synchronization is scheduled to run every 10 minutes. The user can change the frequency of integration by modifying the Business Central Job Queue. For information on setting up Job Queues in Business Central, see: Job queue
For more information on setting up Progressus Project Integration with Microsoft CE/Business Central CRM, see: Setting up Progressus Integration with Microsoft CE and Business Central CRM
Qualification
For future use only.
Management
The Management FastTab contains data related to invoicing and some reporting management and includes the following fields:
Field Name | Description |
---|---|
Progressus Active | Select this option to activate the software after registering the Progressus License.** |
Prompt For Update | Select this option to be prompted to update in resource management views. |
Apply and Close When | You can have the system automatically apply and close the values in the invoice suggestion in different ways. Options are: |
Option | Positive Lines | Negative Lines | Correct Option Used |
---|---|---|---|
Blank | If you invoice the quantity and price of the original transaction, or select the Close Line function, the line will close after posting the invoice. If you change the quantity or the price during invoicing, then the remaining amount will be available in Invoice Suggestions and the line will not close. To close the line, use the Close Line function. | If you invoice the quantity and price of the original transaction, or select the Close Line function, the line will close after posting the invoice. If you change the quantity or the price during invoicing, then the remaining amount will be available in Invoice Suggestions and the line will not close. To close the line, use the Close Line function. | All lines will be restored to Invoice Suggestions. |
Quantity to Invoice Changed | If the quantity to invoice has been changed, for either positive or negative lines, the line will be closed when the sales invoice posts. | If the quantity to invoice has been changed, for either positive or negative lines, the line will be closed when the sales invoice posts. | All lines will be restored to Invoice Suggestions. |
Remaining Quantity is Zero or Below | For positive lines, if the remaining quantity is zero or remaining quantity is negative then it will close. | For negative lines, if the remaining quantity is zero or remaining quantity is positive then it will close. | All lines will be restored to Invoice Suggestions. |
Remaining Quantity or Amount is Zero or Below | For positive lines, if the remaining quantity or amount is zero or remaining quantity or amount is negative then it will close. | For negative lines, if the remaining quantity or amount is zero or remaining quantity or amount is positive then it will close. | All lines will be restored to Invoice Suggestions. |
Field Name | Description |
---|---|
Earning Rate Diff. More Than % | This setup applies to the Resource Profit page. Enter the percentage On Load Per Resource or Project will be red or green. |
Client Rate Diff. More Than % | This setup applies to the Resource Profit page. Enter the percentage same as above. |
Overrun Split | This setup applies to the Resource Efficiency page. |
Max Records | This setup is used in the resource management views to limit the number of records used for each individual resource performance indicator calculation. Limiting the list will improve the amount of time the load takes to display the efficiency values. |
Resource Load Nos. | Number series for Resource Loads. Enter the code for the numbering sequence to create resource loads. This is used in the Resource Load Per Project page. |
Price/Cost Not Found Action | Select option to control response when a price or cost record cannot be found that matches the transaction parameters. Options include: |
- Zero Amount: make the record 0 (zero) amount. | |
- Warning: Display a warning message alerting the user to the issue. | |
- Error: Display an error message and prevent the user from proceeding until the issue is resolved. | |
Enhanced Dimension Handling | If selected, all Dimension handling will be done using the new procedures created in this feature. This includes Job Task Dimension priorities being enforced correctly. Progressus Project Journal Dimensions will be determined using the source code based on the type of entry. If a line is for Resource Time, the time entry source code will be used to determine Dimension priority. If the line is for Expense, it will use the Expense Entry source to determine Dimension priority. The main result of these changes is to ensure each Project Ledger Entry will have the same Dimensions regardless of where it was entered (for example, Time related entry from Timesheet, Time Journal or Progressus Project Journal). For more information on Default Dimension Priorities, see: Working with Dimensions > To set up default dimension priorities |
Use Ledger Dimensions on Purchase Invoice | Select to specify that the Dimensions assigned to the Project Ledger Entry will be used for the Purchase Invoice line, regardless of the purchase source code Dimension priorities. |
Use Ledger Dimensions on Sales Invoice | Select to specify that the Dimensions assigned to the Project Ledger Entry will be used for the Sales Invoice Line, regardless of the sales source code Dimension priorities. |
Archiving
Field Name | Description |
---|---|
Archive Projects | Specifies if you want to automatically archive Projects. Options: |
Never: Don't archive projects automatically. You can manually archive projects by using the Archive Document action, if needed. | |
Question: Be prompted to choose whether to archive a project when one of the events mentioned earlier occurs. | |
Always: Silently archive the project automatically when one of the events mentioned earlier occurs. |
Hour Bank
The Hour Bank FastTab allows pre-billing of a block of time against a Project for future use. An example would be a Project where a customer pre-purchases a block of resource time to be used as needed for project tasks. As Project Usage occurs, it is posted against the Hour Bank. This relieves the prepaid hours and books the revenue.
Field Name | Description |
---|---|
Hour Bank Nos. | Specifies the Code for the Number Series that will be used creating a new Hour Bank. To see the Number Series information, click the drop-down arrow in the field. |
Hour Bank Prepaid Account No. | Specifies the Balance Sheet Account for holding the payment from the customer until it is used. |
Note
For more information about hour banks, see: Hour Bank Billing
Budget
The Budget FastTab contains default information for settings used in the Budget Matrix, Budget Matrix with Capacity, Budget Matrix with Calendar, Budget Matrix by Resource, and Resource Planning. It includes the following fields:
Field Name | Description |
---|---|
Default start time Matrix | Enter the default start time for the Budget Matrix. |
Default Budget Column Value | Select the default for the time period to display columns for the budget. Options: |
- Day | |
- Week | |
- Month | |
- Quarter | |
- Year | |
- Accounting Period | |
Planning Integration | Provides a lookup into the Budget Version list. Specifies the default Budget Version to be linked to Planning Lines. If this field is blank, a link to the Planning Lines can be created on the individual Progressus Project Card > Budget FastTab, Planning Integration field. |
Default Capacity Column Value | Select the default for the Time Period to display columns when viewing Resource Capacity. Options: |
- Day | |
- Week | |
- Month | |
- Quarter | |
- Year | |
- Accounting Period | |
Add Project Permissions Based on Budget | Check this to automatically add Permissions to a Project for a Resource added to the Budget. |
Move Budget with Task | Specifies how Budget Entries are moved when the Task Start Date (planning) is changed. |
- Never: If selected, the Move Budget with Task feature is disabled. | |
- Same number of days: If selected, when a change is made to the Start Date (planning) on a Task (e.g., in the Gantt Chart or from the Task Card), this will change the dates on Budget Entries accordingly. Only Budget Entries for the Task and in the Active Budget Version will be moved. |
Tip
Example: The Start Date is increased by 7 days, then the date on the Budget Entries for the Task and in the Active Budget Version will be increased by 7 days.
Enforce Dependencies in Gantt | Specifies, if selected (true), that moving one Task can move other Tasks when there are dependencies between them. |
Post Work Assignment Changes | Specifies, if true, that changes to a Project Budget will automatically be posted. If false, the changes will be available in the Budget Work Assignment Journal to review and post. |
Default Work Assignment | Specifies the default action for the Work Assignment Action field in the Budget Matrix, or Budget Matrix with Capacity. Options: |
- No Update: The Work Assignment will not be updated. | |
- Delete: The Work Assignment will be deleted. | |
- Update Budget Entry No. Only: The Work Assignment hours will not be updated, but the Budget Entry No. will be updated. | |
- Modify: Will modify the Work Assignment only if there is a 1:1 relationship between the Budget Entry and the Work Assignment. If so, the Budget Entry and the Work Assignment will be updated with a new Budget Entry Number. |
Note
No action will be taken when a Work Assignment is locked, has a Status of Completed, or no Work Assignment exists for the Budget Entry (example: the Budget Entry is new).
Purchasing
Purchase Receipt Posting specifies how and where Purchase Receipt costs should post.
Field Name | Description |
---|---|
Purchase Receipt Posting | Options: |
Received not Invoiced: Select to reserve the cost in the Received not Invoiced (LCY) field on the Project Plan. | |
Usage Cost: Select to post the receipt as Usage Cost to the Project. | |
Reserved to Project: Select to post the receipt costs directly to Inventory but Reserved to Project. |
Service Order
The Service Order FastTab contains information for settings linking Project with the Service Module. It includes the following fields:
Field Name | Description |
---|---|
Default Project No. | Select the default code for the Project Number to be used for Service Orders when Time needs to be charged to a Service Order and not a Project. |
Default Project Task Code | Select the default Code for the Project Task to be used for Service Orders when Time needs to be charged to a Service Order and not a Project. |
Parameters for Project, Contract and Subcontract Alerts
Parameters allow you to set up standardized messaging for the Subjector Body text of Email notifications on Projects, Subcontracts, and Contracts. The Email notifications can have key information (Project No., Task No., Changes) completed by the system if you use parameters to populate the text.
Use the following parameters to pull in values for Email notifications:
Alert Name | Parameters |
---|---|
Project Alerts | %1 = Project No. |
%2 = Project Name | |
%3 = Budget | |
%4 = Actual | |
Task Alerts | - %1 = Project No. |
- %2 = Task No. | |
- %3 = Budget | |
- %4 = Actual | |
Contract Alerts | - %1 = Project |
- %2 = Contract | |
- %3 = Change Order | |
- %4 = Approver | |
- %5 = Preparer | |
Subcontract Alerts | - %1 = Project |
- %2 = Subcontract | |
- %3 = Change Order or Payment Request (based on which is being sent). | |
- %4 = Approver | |
- %5 = Preparer |
Tip
Example of Task Alert Subject text for a task over budget: Over budget alert about Project %1, Task %2. This will produce an Email subject line text with the specific Project Number and Task Number in the Subject Line of the Email notification.
Tip
Example of Task Alert Body text: This Email is to alert you that your Project %1, Task %1 is over budget. Your budgeted amount for this is %3 and the actual used to date is %4. This will produce an Email body text with the specific Project Number and Task Number, and the Project's Budget and Actual amounts in the body of the Email notification.
Subcontract
The Subcontract FastTab contains information for settings linking Project with the Subcontract Module. It includes the following fields:
Field Name | Description |
---|---|
Subcontract Nos. | Specifies the Code for the Number Series that will be used to assign numbers to Subcontracts. To see the Number Series that have been set up in the No. Series table, click the drop-down arrow in the field. |
Rejection Email | Specifies Email notification. Select this option to enable Email notifications for rejection of Change Order and Payment Requests in Subcontracts. |
Change Order Body | Specifies the body text for Emails sent to the preparer on rejection of a Change Order. |
Tip
Example: Change Order %3, Project %1, Subcontract %2 was rejected by Approver %4. This will produce a Change Order Rejection Email Body text with the specific Change Order Number, Project Number, Subcontract Number and Approver ID in the body of the Email notification.
Change Order Subject | Specifies the Subject text for Emails sent to the preparer on rejection of a Change Order. |
Tip
Example: Change Order %3, Project %1, Subcontract %2 has been rejected. This will produce a Change Order Rejection Email Subject text with the specific Change Order Number, Project Number, and Subcontract Number in the Subject line of the Email.
Payment Request Body | Specifies the Body text for Emails sent to the preparer on rejection of a Payment Request. |
Tip
Example: Payment Request %3, Project %1, Subcontract %2 was rejected by Approver %4. This will produce a Payment Request Rejection Email Body text with the specific Payment Request Number, Project Number, Subcontract Number and Approver ID in the body of the Email.
Payment Request Subject | Specifies the Subject text for Emails sent to the preparer on rejection of a Payment Request. |
Tip
Example: Payment Request %3, Project %1, Subcontract %2 has been rejected. This will produce a Payment Request Rejection Email Subject Line text with the specific Payment Request Number, Project Number and Subcontract Number in the Subject line of the Email.
Approval Email | Specifies Email notification is enabled or disabled for approval of Change Order and Payment Requests in Subcontracts. |
Change Order Body | Specifies the Body text for Emails sent to the approver when a Change Order is ready to be approved. |
Tip
Example: Preparer %5 has submitted Change Order %3, Project %1, Subcontract %2 for Approver %4. This will produce a Change Order Submitted Email Body text with the specific Preparer ID (who submitted the Change Order), Change Order Number, Project Number, Subcontract Number, and Approver ID in the Body of the Email.
Change Order Subject | Specifies the Subject text for Emails sent to the approver when a Change Order is ready to be approved. |
Tip
Example: Change Order %3, Project %1, Subcontract %2 has been submitted. This will produce a Change Order Submitted Email Subject line text with the specific Change Order Number, Project Number, and Subcontract Number in the Subject Line of the Email.
Payment Request Body | Specifies the Body text for Emails sent to the approver when a Payment Request is ready to be approved. |
Tip
Example: Preparer %5 has submitted Payment Request %3, Project %1, Subcontract %2 for Approver %4. This will produce a Payment Request Submitted Email Body text with the specific Preparer ID (who submitted the Payment Request), Payment Request Number, Project Number, Subcontract Number, and Approver ID in the Body of the Email.
Payment Request Subject | Specifies the Subject text for Emails sent to the approver when a Payment Request is ready to be approved. |
Tip
Example: Payment Request %3, Project %1, Subcontract %2 has been submitted. This will produce a Payment Request Submitted Email Subject line text with the specific Payment Request Number, Project Number, and Subcontract Number in the Subject Line of the Email.
Contract Email Setup
The Contract Email Setup FastTab contains information for settings linking a Project with the Contract Module. It includes the following fields:
Field Name | Description |
---|---|
Rejection Email | Specifies, if selected (true) that Email notifications for rejections of Change Orders in Contracts are enabled. If not selected (false), Email notifications for Contract rejections of Change Orders in Contracts are disabled. |
Change Order Body | Specifies the body text for Emails sent to the preparer on rejection of a Change Order. |
Change Order Subject | Specifies the Subject text for Emails sent to the preparer on rejection of a Change Order. |
Approval Email | Specifies, if selected (true) that Email notifications for approvals of Change Orders in Contracts are enabled. If not selected (false), Email notifications for Contract approvals of Change Orders in Contracts are disabled. |
Change Order Body | Specifies the Body text for Emails sent to the approver when a Change Order is ready to be approved. |
Change Order Subject | Specifies the Subject text for Emails sent to the approver when a Change Order is ready to be approved. |
Project Alerts
The Project Alerts FastTab works in conjunction with the setup on the Project Plan to send alerts when the amounts for the Project and/or Task reach the threshold defined on the Project.
The system compares the actual usage amount to the Budget amount. If the Email alert is set to TRUE on the Project Plan, when Project or Task usage reaches the alert threshold, or exceeds the budget, an Email is sent. The Alert Option PGS on the Progressus Project List will be yellow when usage reaches the percent threshold. The color will be red when the actual amount exceeds the Budget.
Field Name | Description |
---|---|
Project Alert Subject | Specifies the Subject text for the Email alert to be sent to the Project Manager and Person Responsible when the yellow or red status is reached on a Project. |
Tip
Example: Project Alert: %1, %2. This will produce an Email Subject text with the specific Project Number and Project Name in the Subject line of the Email notification.
Project Alert Body | Specifies the Body text for the Email alert to be sent to the Project Manager and Person Responsible when the yellow or red status is reached on a Project. |
Tip
Example: %1, %2 has a budget of %3 and an actual of %4. This will produce an Email Body text with the specific Project Number and Task Number, and the Project's Budget and Actual amounts in the body of the Email notification.
Task Alert Subject | Specifies the Subject text for the Email alert to be sent to the Project Manager and Person Responsible when the yellow or red status is reached on a Task. |
Tip
Example: Task Alert: %1, %2. This will produce an Email Subject text with the specific Project Number and Task Number in the Subject Line of the Email notification.
Task Alert Body | Specifies the Body text for the Email alert to be sent to the Project Manager and Person Responsible when the yellow or red status is reached on a Task. |
Tip
Example: %1, %2 has a budget of %3 and an actual of %4. This will produce an Email Body text with the specific Project Number and Task Number, and the Task's Budget and Actual amounts in the Body of the Email notification.
Red, Yellow, Green | These icons are used in the Progressus Project List for the "traffic light" Status of the Project. |