AdvoLogix provides an excellent ecosystem in which to manage your organization's conflict of interest requirements. The following options will allow implementing a disciplined business process in your efforts to comply with your requirements.
The foremost resource for facilitating conflict of interest checks within AdvoLogix is the Conflict Check feature. This feature is designed to aid the process of conflict checking through a centralized and cohesive user experience and work space.
Business Process Automation
Activity Plans provide structure and automation to your organization's planning and scheduling process and represent a series of Activities grouped by virtue of a common time-line objective. This results in the ability to manage a group of interconnected Activities that move forward independently of (and/or in unison with) each other.
Approvals allow you to specify a sequence of steps required to approve a record.
Although AdvoLogix provides an excellent ecosystem in which to manage your organization's conflict of interest requirements the Conflict Check feature is uniquely designed to aid the process through a centralized and cohesive user experience and work space. The conflict search and and accompanying results are memorialized and maintained within the context of a Matter providing a unique work space for managing a unique conflict check while simultaneously memorializing a reference audit trail.
The Process Builder is a workflow tool providing a powerful and user-friendly graphical representation of your process as you build it. The Process Builder’s allows you to: change field values, create other records, update related records, send email and chatter notifications, submit records for approval and much more.
A validation rule is a formula (or expression) that evaluates the data in one or more fields and returns a value a “True” when the record is not valid. Validation rules also include an error message to display to the user when the rule returns a value of “True” due to an invalid value.
Workflow allows you to automate processes to save time across your organization. Workflow rules can be broken into two main components. Workflow rules execute actions when specific criteria are met. (if this then do that)
Searching Your Data
The Conflict Check feature searches within AdvoLogix data for a specific search term, usually an entity name. Presumably a potential conflict may arise should the entity name be found within your AdvoLogix Contacts, Accounts and/or Participant records.
When you use the global search bar, you search through all objects and multiple fields types, including custom and long text fields, within a record. Options allow you to restrict your search to items you own, if available, to exact phrase searches, and to divisions, if your organization uses them. Individual object filters are available to further limit the results. *Also see other considerations regarding lookups.
The Matter Search component allows users to search information related to a particular Matter, within the context of the Matter. Options allow the user to "fine-tune" the results by searching specifically designated related information. *Also see other considerations regarding lookups.
Participants are those parties attributed to having a relationship to a specific Matter. Assigning Participants to your Matters ensures the global search can quickly find the nature of a particular person's relationship, using the Participant database. The Participation Map is also a valuable tool for exploring the relationship(s) a Matter's Participants might share with other Matters.
- When searching, make sure the user has rights to the appropriate information.
- Use Chatter collaboration to communicate between stakeholders, in context to the Client or Matter.
- Use custom Apex or object triggers to develop proprietary or custom conflict of interest solutions.
- Lookup fields are stored as record IDs not the Name attribute of the lookup object. For instance, if your custom object has a lookup to the Contact object, Global Search will not return a result if you’re searching for the Contact’s name. The Contact record will be returned however your custom object will not. There are solutions to this issue. You may create a mirror field to save the Contact’s name in the custom object.