Discovery, Status Session & Post – Live
The OSA DISCOVERY SESSION
is held with all the stakeholders via GoToMeeting and is an information-gathering process meant to dig deep into the details of what is important to a client’s business, target audience, and industry. This is where we can begin to define functional requirements.
STATUS SESSIONS are regularly scheduled calls to review the status of previously defined requirements and discuss any new requirements. These sessions also help the client with further solution bases consultation elements.
POST LIVE SESSIONS are held after the Go-Live date for review and training purposes. These sessions may also identify errors and tweaks to the platform that needs to be addresses by the client or OSA. These sessions will also provide training to users who may have not been involved in the development but need basic training revolving around your unique business process.
Advologix Base Configuration
OSA will insure proper configuration of Advologix’ core components. Matters, Time Keepers, Participants, Document Assembly, etc.
Custom Video Channel
Each OSA Client is provided with a custom Video Channel whereby they can access video knowledge transfers concerning functionality that may be specific to their organization and platform. Clients can distribute the password to this chanel amoung users of the system to help with training and use.
Security Sharing Rules
Sharing Rules Overview. Salesforce sharing rules are put into force when records and other data requires to be shared among the multiple users in the organization. Sharing the records using Advologix therefore becomes the option to be used by the organization.
This provides OSA clients, who are on project pricing with set deliverables, a number of hours that are Agile based and flexible to be used toward development of other task that may yet be defined.
Should you need data placeholders for information not native to the platform, OSA can add custom fields on any page layout. These fields can be created in various types. e.g. Text, Picklist, Formula, Dates etc.
Page layouts control the layout and organization of buttons, fields, s-controls, Visualforce, custom links, and related lists on record pages. They also help determine which fields are visible, read only, and required.
Assigned app settings specify the apps that users can select in the Advologix app menu. Custom permissions give you a way to provide access to custom processes or apps. After you’ve created a custom permission and associated it with a process or app, you can enable the permission in profiles.
OSA will create custom reports with data native to the platforms capabilities with the provided report types and custom report types. Reports are available as summary or matrix.
Some implementation packages are quoted to prep and import relatively clean data. OSA may need to add columns such as unique identifiers e.g. Record Type or other minimal edits to the provided CSV data. Some more extensive requirements for a data load may included deduping, formating data, and scrubbing data. These are addresses either at an additional cost or part of a larger implementation package. A large amount of time is consumed in data prep ensuring data relationships across the platform.
Legacy Notes and Emails
Notes and Emails consume a large amount of data and are not as easily exported from legacy systems or imported in to new platforms. Data configurations may differ greatly. There are a number of approaches to storing this legacy data which can be discussed in the discovery session.
Many time there is a need to have differing data sets and page layouts for a particular object such as Matters. Record Types allow tailored business processes to different Users. Record types let you offer different business processes, picklist values, and page layouts to different users. You might create record types to differentiate your Divorce matters from your Patent Matters or other legal area offering different picklist values for each.
In the user interface, you can extend your organization’s data by defining custom objects. Custom objects are custom database tables that allow you to store information unique to your organization. For example, if you need a data base of all courts in your area with associated data. We would create an object called courts wich we can place on the matter object. You can then add specific courts to that matter.
Workflow rules can help automate the following types of actions based on your organization’s processes: Tasks: Assign a new task to a user, role, or record owner. Email Alerts: Send an email to one or more recipients you specify. Field Updates: Update the value of a field on a record.
3rd Party Applications
Via the platforms cloud computing marketplace users can access, download and install software apps that help in business process and integration with other systems. Examples included Document Management, Accounting, Marketing Apps etc.