The CreatorCon Call for Content is officially open! Get started here.

Regarding "Generate labor cost" in project workspace

WataruS
Tera Contributor

If anyone has information regarding the following points, please let me know.

 

①I want to reflect amounts for each employee number in the Rate Model.

1. The Rate Model Attribute is configured as follows.

WataruS_0-1757666082088.png

 

2.I also specify the employee number in the Rate Line as follows.

WataruS_1-1757666237520.png

However, even when you actually click Generate labor cost, this amount is not reflected.

Is there anything that could be the cause?

 

②Please tell me the conditions under which the calculation result is generated when the “Creat Labor Cost” button is pressed.

If a task's date is in the past, does that prevent cost calculations from being performed?

 

2 REPLIES 2

Vinay3
ServiceNow Employee
ServiceNow Employee

Hi @WataruS , the rate model definition looks to be right. Please ensure that the rate model is assigned to the respective project and the resource conditions exactly match the rate line. Ex: the resource assignment should also match the role and group besides the employee number for the right rate line to be used.

Labor costs are generated even for the task dates in the past the resource assignment is done newly for a task in the past.

WataruS
Tera Contributor

Hi, @Vinay3 
Thank you for answering.

This information is very helpful for me.

I have successfully generated costs based on employee number according to the specified conditions.

 

Regarding ②the generation conditions when pressing the “Creat Labor Cost” button,

When I look at the Condition for the Generate Labor Costs UI Action, the following is listed.

gs.hasRole('project_manager') && GlidePluginManager.isActive('sn_plng_att_core') && current.attr_based_planning == true && current.canRead()

 

Is it correct to understand that costs are generated under the following conditions:
(1)The user has the project_manager role
(2) The sn_plng_att_core plugin is enabled
(3)The record's attr_based_planning is set to true
(4)And the user has permission to view the record?