More about the home page.
- In the View section, select an appropriate list view from the drop-down list to go directly to that list page, or click Create New View to define your own custom list view. List views let you display a list of records that match specific criteria.
- In the Recent section, select an item from the drop-down list on the right to display a brief list of the top records matching that criteria. The choices are listed in the table that follows.
- From the list, you can click any object name to go directly to its detail.
- Click New to create a new message type.
- To change the owner of one or more records, select the records you want to change from the list view then click Change Owner.
- To change the value of an editable field shown in the list double-click it, enter the value you want and click Save.
|
Recent Choice |
Description |
|
|---|---|---|
|
Recently Viewed |
The last 10 or 25 records you viewed, with the most recently viewed item listed first. This list is derived from your recent items and includes records owned by you and other users. |
|
|
Recently Created |
The last 10 or 25 records you created, with the most recently created item listed first. This list only includes records owned by you. |
|
|
Recently Modified |
The last 10 or 25 records you updated, with the most recently updated item listed first. This list only includes records owned by you. |
In Foundations, FinancialForce products publish and subscribe to information using message types. Publications and subscriptions belong to a message type. A message type defines the actions to be carried out in the applications that subscribe to it.
When a registered product publishes information, the message type that the product publishes determines the actions to be carried out in the registered products that subscribe to that message type. For instance, a message type can determine whether records are created, updated, or deleted.
For example, the message type Resource.Create might contain messages with information relating to HCM worker records that have been created. PSA might subscribe to the Resource.Create message type and create resource records based on the information in its messages. Similarly, the Resource.Update message type and its messages can contain information regarding HCM worker records, which have been updated. PSA can subscribe to this message type and update its relevant resource records.
You can also use message types to group messages.
Importing and Exporting
You can import and export message types and their publications and subscriptions.
You can export your publications and subscriptions as a JSONJavaScript Object Notation. A lightweight format based on a subset of JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. This is a text based format that is easy for both humans and computers to read and write. file. You can then import those publications and subscriptions to another Salesforce orgSalesforce organization that has the same registered products. This enables you to copy your Foundations message types, publications and subscriptions from one Salesforce org to another. When you export publications and subscriptions, a JSON file is created. You can then choose whether you want to open the file or download it.
Parent Message Types and Child Message Types
Some FinancialForce applications publish information in child message types while others subscribe to information contained in parent message types. You manage this on the Publications & Subscriptions tab.
Custom Message Types
You can create custom message types. Using custom message types you can:
- Publish information from your own products
- Subscribe to information from your own products or FinancialForce products.
Developer Names
When you create a custom message type, a unique developer name is required. Developer names enable you to create a unique identifier for the record and action being carried out on it. You can enter any value, but it must be unique. If you do not enter a value, a developer name is generated automatically.
The table that follows shows the way in which developer names are generated.
| Message name | Parent | Entered Developer Name | Created Developer Name |
|---|---|---|---|
| Item | – | – | Item |
| Add | Item | – | Item.Add |
| Update | Item | Modify | Item.Modify |