Accorto Parameters are used for various settings.
Go to Setup > Develop > Custom Settings
- Click on Manage Accorto Parameters
- Click on New (or edit existing)
Note that defining the First Day of Week is defined in the Payroll Processor now.
Examples Settings:
| Description | Name | Key | Value String | Value Int |
|---|---|---|---|---|
| Create Invoice from Project: Default query option for Project Line Fixed Charge Amount (default: ge: =>0) | InvoiceProject. queryFixedChangeAmt | InvoiceProject. queryFixedChangeAmt | eq|ge(default)|(empty)| | n/a |
| Project Workbench: Link | -any- | ShowWithNamespace | true|false(default) | n/a |
| Project Line Allocations: Save only changed allocations if more than x allocations | ProjectLineAllocation | ProjectLineAllocation | OnlyChanged | number of allocations |
| Pre-Billing detail records to be displayed (default: 600) | PreBillingRecords | PreBillingRecords | number of records |
Lookup Contents
You can use Parameters to define the fields to query and display for Lookup fields in the Lightning Time components.
| Key (value in Value String) | Description | Example |
|---|---|---|
| ALookup:sObjectType:1 | Fields for item title - separated by a comma "," | ALookup:opportunity:1 = Account.Name,Stage |
| ALookup:sObjectType:2 | Fields for item subtitle - separated by a comma "," | ALookup:Opportunity:2 = MyField__c,Name |
| ALookup:sObjectType:parent | Field in the selection record indicating the parent | ALookup:Opportunity:parent = AccountId (provided by default) |
| ALookup:sObjectType:recordParent | Field in the T+E Item indicating the parent for the field | ALookup:Opportunity:recordParent = accorto__Opportunity__c (provided by default) |
| ALookup:sObjectType:optional | If set to true, includes also records without a parent value (e.g. Opportunities w/o account) | ALookup:Opportunity:optional = false (default) |
| ALookup:sObjectType:restrict | SQL Were clause to restrict the selection options | ALookup:Opportunity:restrict = StageName='Closed Won' |
| ALookup:sObjectType:recordMatch | List Activity Type if Resource Price contains Activity Type for Project | ALookup:a__ActivityType__c:recordMatch = accorto__Project__c |
| ALookup:sObjectType:active | Checkbox (boolean) field name to determine if the record is used (active). Inactive records are displayed but cannot be selected | ALookup:Opportunity:active = IsPrivate (will then show only private records) |
| ALookup:sObjectType:status | String field name to determine if the record is used. Invalid records are displayed but cannot be selected | ALookup:Opportunity:status = StageName |
| ALookup:sObjectType:noStatuses | Comma-separated status field Values of unwanted/invalid records | ALookup:Opportunity:noStatuses = Closed Won, Closed Lost |
| ALookup:sObjectType:maxLookups | Max Lookups to be cached (default 1000) - no need for search queries | ALookup:Opportunity:maxLookups = 2000 (number) |
| ALookup:sObjectType:icon | Icon name for the display | ALookup:Opportunity:icon = standard:opportunity (default) |
For "restrict", you can also use variables
- {!resourceId} = the user's recorce id
- {!contactId} = the user's resource contact or user contact id (e.g. community users)
- {!userId} = the user's resource user id
SQL Where restriction examples
- MyContactId__c={!contactId}
- select options restrictcted where the custom object field MyContact__c matches the users's resource contact
- key: ALookup:MyCustomObject__c:restrict
- value: MyContactId__c={!contactId}
- OwnerId={!userId}
- show only records owned by the user - example: only own cases
- key: ALookup:Case:restrict
- value: OwnerId={!userId}
Here is an example, to show a custom field in the Case lookup
Here an example, where the lookup values of the custom object Applicants__c is restricted by the selected project:
Project Status info
You can show additional project information in the Project Status popup in the Timesheet, Timer, etc.
The Key has the format
- PjStatus:x:Project
- PjStatus:x:Line
depending from where to get the information from. If the information is not directly on the Project or Project Line, you could create a formula field.
The Value String contains the name of the field in either Project or Project Line, e.g. MyCustomField__c