Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Components installed with Expense Line

Log in to subscribe to topics and get notified when content changes.

Components installed with Expense Line

Several types of components are installed with the Expense Line plugin.

Tables installed with Expense Line

Tables are added with activation of Expense Line.

Table Description
Expense Line

[fm_expense_line]

Stores information about expense lines, including a link to the associated rate card. Contains the status and next scheduled processing date for the expense line.

Roles installed with Expense Line

Roles are added with activation of Expense Line.

Role Contains roles Description
Financial admin [financial_mgmt_admin] [financial_mgmt_user] Can create, write, and delete allocation units, fixed assets, depreciation, rate cards, distribution costs, expense lines, and expense allocations.
Financial user [financial_mgmt_user] none Can read allocation units and expense allocations. Can create, read, and write rate cards and expense lines. Can create, read, write, and delete fixed assets, depreciation, distribution costs.

Script includes installed with Expense Line

Script includes are added with activation of Expense Line.

Script include Description
ExpenseLine Helps create expense line records.
ExpenseManagementUtils Provides utilities for financial management modules.
ExpenseManagementUtilsAJAX Provides AJAX utilities for expense lines.

Domain separation and Expense Line

This is an overview of domain separation and Expense Line. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

Overview

Domain separation in this application is supported at the Data only level, meaning it supports the data security model of separating visibility of data from one domain to another. To learn more, see Application support for domain separation.

Client scripts installed with Expense Line

Client scripts are added with activation of Expense Line.

Client script Table Description
Populate sources if inherited [fm_expense_line] Copies the source fields of the parent expense line to the current line on the Expense Line record if an expense line is inherited.
Populate source fields from asset [fm_expense_line] If the source asset changes, updates related source fields on the Expense Line record . For example, if the asset source field changes, the configuration item source field is updated, as well.
Populate source fields from ci [fm_expense_line] Updates related source fields if the source configuration item changes on the Expense Line record.
Populate source fields from contract [fm_expense_line] Updates related source fields if the source contract changes on the Expense Line record.
Populate source fields from task [fm_expense_line] Updates related source fields if the source task changes on the Expense Line record.

Business rules installed with Expense Line

Business rules are added with activation of Expense Line.

Business rule Table Description
Create Expense Line [alm_asset] Automatically creates an expense line for a new asset based on asset cost unless the asset is a merged software license.
Set source allocation fields [fm_expense_line] Sets the related source fields when the source ID changes. For example, when an asset becomes the source ID, the asset source field and configuration item source field are automatically populated.
Update Costs [alm_consumable] Updates the cost of a consumable when quantity is reduced.

Domain separation and Expense Line

This is an overview of domain separation and Expense Line processing. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

Overview

Support: Data only

Domain separation in this application is supported at the Data only level, meaning it supports the data security model of separating visibility of data from one domain to another. To learn more, see Application support for domain separation.

Feedback