38
edits
Changes
→Creating a Personal Transaction Type
Set of [[Custom Fields|custom fields]] grouped together into a specific transaction type and linked to a [[Role|role]]. For example, a candidate [[Role|role ]] may have a career type transaction. Multiple transaction records can be linked to a single contact in that [[Role|role]].
Personal transactions also represent items that the [[User|user]] maintains in their profile using the [[User Centric Interface|UCI]].
* The [[Administrator|administrator]] defines the transaction types.
* Examples of transaction types are education, work history, or publications history.
* Each transaction type supports [[Custom Fields|custom fields]], a list view [[TemplateList View|list view template]]template, and the ability to control if the transaction type is available to the [[User|user]], via the UCI.* Each transaction type can be associated with one or more [[Role|roles ]] within the system.
* These transactions are also visible within the administrative interface for each contact.
* When a [[User|user ]] subscribes to a folder, their profile becomes searchable to all other [[User|users ]] subscribed to the folders.* The [[Administrator ]] defines the folders and associates the folders with each [[User Centric Interface|UCI]].* These folders are actually constructs from the [[SmartSimple ]] [[Applicant Tracking ]] system.
=Creating a Personal Transaction Type=
1. Click [[Configuration Menu|Configuration]], [[User Centric Interface]] [[Menu|menu]].
2. Click the '''Transaction Types''' tab.
3. Click the '''New Type''' tab.<br/>[[Image:transaction grant.png]][[Image:transaction grant2.png]]<br/>
Each Transaction type consists of the following standard settings:
* '''Associated Roles''' - the roles to be associated with this transaction type. Use everyone to associate the transaction type with all users.
* '''Deny Review Roles''' - the roles to be associated with this transaction type that you want to deny view ability.
* '''[[Use Publication Service]]''' – indicates that this transaction type can be completed using a web service such as PUBMED. Enabling this option will display a service lookup link in the User Centric Interface when the user adds a transaction of this type.* '''Builtin Use Third party Verification Service''' - You can store the values returned from the external database search in the transaction custom fields.* '''Built-in Fields''' - there are four standard fields associated with a generic transaction type: start date, end date, subject, and description. If these fields are not required, set their label settings to blank.
* '''Field Button''' - provides a link to the custom field list for this transaction type.
==See Also==* [[Category:GlossaryTransaction Status]]* [[Transaction Attribution]] [[Category:System ManagementTransactions]]
