Organizational Units are used to organize the company’s network and define the collaboration between them

EXAMPLE

The allocation process is used to allocate credit transactions against debit transactions to settle them.
The allocation process is an automated process triggered every time a financial transaction becomes 'Posted'.
Within CRM.COM, you have the option to select between one of 2 main allocation process principles, that will be applied to all financial transactions within the system;

• FIFO :Where a credit is allocated against the oldest available (non-allocated) debit automatically
• FIFO & Against Item :Where a credit is allocated first against a designated debit and any remaining amount is allocated FIFO

Privacy level restrictions are applied as part of the processes which are enforcing the collaboration between communities and groups. Privacy levels are used to apply additional restrictions on top of the restrictions which are derived by the specified collaboration options. For example users belonging to sales branch 1 might be able to view records belonging to sales branch 2 only if their privacy level is set to public. The following logic is followed to apply privacy level restrictions:

• Record is accessible if its privacy level has a numeric value which is equal or less than the privacy level defined for a specific collaboration option
• Record is accessible if its privacy level is ignored because a specific collaboration option is set to be allowed for all privacy levels
• Record is accessible if its privacy level is ignored because is not specified (i.e. Applicable to all by default)

All Users can change the privacy level, through a dedicated “Set Privacy Level” action, if they are allowed by the security profile assigned to them. The new Privacy Levels which can be set are filtered based on the following logic:

• Privacy Levels belonging to Privacy Level Groups which are applicable to all Communities, Group, Units i.e. no restrictions were specified
• Privacy Levels belonging to Privacy Level Groups which have the Group that the User used during log in included in the list of Communities, Groups or Units which can select that record

Audit Trail is visible in the detail pages of all Audit Trailed Entities, as a tab at the bottom. If an entity is audit trailed and a user makes changes to an audit trailed field then all the related information will be captured and made available in the Audit Trail Tab of the specific record.

The information displayed in the audit trail tab is the following:

• Attribute: The field that has been manipulated
• Action: The action applied on the field
  • Addition
  • Removal
  • Modification
• From Value: The old value (before the change)
• To Value: The new value (after the change)
• Modified Date: Date the change was executed
• Modified by User: User that made the change
• Modified by Unit: Unit the user that made the change belonged to

•  Controlled Selection Access Entity