Glossary

  • The Action Center is in the right navigation area of the interface. The Action Center provides a centralized location for actions within the application. Available actions vary based on location in the application.
  • Items displayed in the Action Center are Action items - this active content is based on the current active work item selected in the Work Center and can consist of Action Items such as Workflow, Links and Reports, or Action Center Panels such as My Tasks and Activities.
  • The ActiveX controls were a series of browser add-ins specifically designed to enhance functionality within the app. ActiveX controls should always be downloaded from the Admin workspace in your install.
  • From Latin meaning 'For this', ad hoc is literally defined as "formed or used for a special purpose: made or done without planning because of an immediate need." The Izenda Business Intelligence ad-hoc reporting module allows you to build customized, highly specific reports based on ClientSpace data with little or no need for programming.
  • The Admin Workspace is a specialized set of administrative dataforms used to set default information throughout the system, ranging from Pricing and Workers' Compensation defaults to system-wide settings governing imports. Co-locating these dataforms in a single workspace makes for ease in management and configuration.
  • An API is an Application Programming Interface and specifies a software component in terms of its operations, their inputs and outputs and underlying types and available methods. APIs are used in ClientSpace to connect one software system to another to facilitate the transfer of data between the two systems. APIs generally require additional configuration in both ClientSpace and the other software system and may have an associated cost.
  • BPM is a web portal that you, as a PEO, can direct your customers to so they can review upcoming benefits renewal options available to their company. It includes new plan offerings for their employees and premium and contribution comparisons for the upcoming renewal as compared to their existing benefit plans and rates. BPM is a web portal where a PEO can direct clients to review upcoming benefits renewal options available to their company. It includes new plan offerings for their employees plus premium and contribution comparisons for the upcoming renewal period *as compared to their existing benefit plans and rates.) The BPM portal clients to model various options for plan offerings in the upcoming year to determine what is best for their company. Their selections are then used by the ClientSpace Benefits Team to set up the Open Enrollment portal.
  • Business intelligence, or BI, is an umbrella term that refers to a variety of software applications used to analyze an organization's raw data. For ClientSpace, BI specifically refers to the embedded Izenda Business Intelligence module that allows you to create on-demand reports from your ClientSpace data using a simple interface. - Dashboards are a dynamic and interactive tool for viewing critical information from multiple sources in a single view. Users can hover over a report to get details or drill down into it for greater insight. Users can create and customize their own BI dashboards, then use them to print, save, share, and send reports. Security options let you decide who can view or make edits. - Data Source: With regards to business intelligence, a datasource is the table, view, or datasource report used to provide data for your Report – Datasources may be joined using Foreign Key relationships to aggregate data. In Business Intelligence, datasources are configured on the Datasource tab. - Fields are the individual data points available from a datasource in business intelligence. An example is: tblOrganization is the datasource, Name, Address1, City are fields from that datasource. - Filters: In the Filters tab, the fields of the table/view chosen in the Data Sources tab can be filtered so that only pertinent entries appear in the table. - Scheduling: Izenda BI allows reports and dashboards to be scheduled and automatically emailed to a recipients list. Care should be taken when scheduling reports or dashboards, because the schedule has no way of respecting the #CurrentUser or #CurrentWorkspace options for filtering, so each recipient of the report will receive all of the data contained within the report based on any static filters that are saved on the report.
  • Dataform business logic and rules are powerful tools that are available for supporting dataform workflow and managing data integrity in ClientSpace. These configurable rules allow you to trigger field validation, clear field values at specific sections of a workflow, and automatically complete fields based on values from other source fields.
  • Overlying the Core and PEO products is the Custom, or Candy layer of the software. This layer is client specific and is comprised of custom dataforms, business rules, reports etc. used by our clients to make ClientSpace their own.
  • A case is a top-level project, and related tasks are the individual items that need to be completed for the project. You can use cases only, or use tasks that are related to the case.
  • Chiclets are filtered search criteria that display as buttons below the Quick search on the dashboard modules.
  • The Claim Value is the dollar amount from the Comp Claim Financial form used to calculate the deductible. The Paid-Total or Incurred-Total amount from the Comp Claim Financial record may be used as the Claim Value. The field used is determined by the value in the Use TotalIncurred setting on the ClaimDeductibleBilling rule method parameter. If the setting is "Yes", the calculation uses Incurred-Total for calculated. Otherwise, the calculation uses Paid-Total.
  • The site where ClientSpace resides, the client installation could describe a Development or DEV site, a User Acceptance Testing or UAT site, a Quality Assurance or QA site, or the site that is used by our clients, their Production or PROD site. In most cases, each of these installations have separate databases to store the individual data associated with the site.
  • A powerful Enterprise Workflow Automation platform that provides the ideal environment for building software solutions that are perfectly suited to the needs of your workforce. If it’s a CRM, Sales Automation System, Workflow/Process Management System, or a Data Management system, we’ve got you covered. We pride ourselves on our unique ability to make software that fits your business, not vice-versa, to deliver measurable returns on your technology investment.
  • ClientSpacePEO is an integrated CRM and workflow management system that has been developed specifically for the PEO / Employee Leasing industry. ClientSpacePEO goes far beyond customary sales contact management and client service functionality included with competing software packages.
  • Cloning refers to the generation of a ClientSpace object by copying a template example of that object. Items that can be cloned range from Tasks and Dataforms to Workspaces and even Users. Cloning is often used to provide consistency of data, or for workflow design. You cannot clone a single dataform if it already exists in a workspace, such as the Client Master because single dataforms typically have a one-to-one relationship with the Workspace.
  • The word cloud often refers to the Internet, and more precisely, to some data center full of servers connected to the Internet. In ClientSpace terms, our data center space is in a secured off-site location, where servers run each of our ClientSpace installations.
  • A category of the PrismHR work process that does not include sprint development work. Concierge work can include such items as database scripts, configuration, imports, merges, and reports.
  • Condition expressions are used in email templates, workflow channels, widget layouts, and custom links. Condition expressions are used to control when an event or action is triggered. Condition Expressions use Labels from Display Conditions along with AND, OR, and NOT operators to control precedence and sequence.
  • Configurable features may be unique to an installation – these are customizations to the system that can be configured by a Global Administrator of the system through the Admin Settings area. Some examples of configurable items are dataform links, workflow, and standard CORE and PEO business rules. Configurable items are different from customizable items in that configurable items do not require PrismHR development to implement.
  • Contextual help text can be added to the Description field when adding a dataform field to provide more detailed information about the field. On any dataform, hover over the field label, and if the label changes color or the mouse pointer changes shape or both, then there is related help text to be found by clicking the info bubble.
  • ClientSpace is built in a series of software layers. Core is the most basic of the layers. Out of the box, it comes with basic CRM functionality, as well as the Lead Management and Client Service modules. This layer is still extremely powerful, as it is the foundation of all ClientSpace functionality. This includes our powerful Dataform Engine, Workflow Engine, Data Integration tools, survey functionality, task functionality, Ad-Hoc Reports and Dashboards. Using the tools available here we can build elaborate systems to help manage your business.
  • Customer relationship management (CRM) refers to practices, strategies, and technologies that companies use to manage and analyze customer interactions and data throughout the customer lifecycle, with the goal of improving business relationships with customers, assisting in customer retention and driving sales growth. CRM software systems such as ClientSpace are designed to help facilitate this process.
  • Customizable refers to features that may be unique to your ClientSpace install, but this customization happens in the code, requiring PrismHR development. This differs from configuration, which is also unique to an installation, but may be configured by a Global Administrator of the system. Some examples of customizable items are custom Business rules, Dataform flags that can be used for triggering actions on Save, or custom jquery to provide dialog boxes to ensure appropriate workflow.
  • Dashboards are a window into data management in ClientSpace providing at a glance, filtered access to ClientSpace data. Some, such as the Home Dashboard, or Home with Cases provide aggregate data across multiple ClientSpace systems, such as Workspaces, Organizations, Calendar Events, and Tasks.
  • A database is an organized collection of data. It is the collection of schemas, tables, queries, reports, views, and other objects. The data are typically organized to model aspects of reality in a way that supports processes requiring information, such as modelling the employees and their related information that are attached to a client in order to facilitate HR management.
  • A database management system (DBMS) is a computer software application that interacts with the user, other applications, and the database itself to capture and analyze data. A general-purpose DBMS is designed to allow the definition (set the default parameters - how big, what type of data, etc.), creation (adding new data), querying (attaching to and analyzing the data), update, and administration of databases. Well-known DBMSs include Microsoft SQL Server, MySQL, PostgreSQL, Oracle, Sybase, and IBM DB2. ClientSpace uses an underlying DBMS of Microsoft SQL Server relational database.
  • The dataform is a dynamically generated, configurable web page used for storing information. Dataforms are comprised of fields arranged in fieldsets, and can be designed to be dynamic, hiding, or displaying data as needed. A dataform is similar in concept to a table. Note that there are some Core tables that are not configurable as dataforms (such as Orgs and Contacts.) However, Contact Other Info is a configurable dataform.
  • With regards to reporting, a datasource is the table, view, or datasource report used to provide data for your report. Datasources can be joined using Foreign Key relationships to aggregate data.
  • A datatype is the type of field, such as text field, date field, lookup field, etc. Datatypes are the building blocks of dataform fields, allowing a Global Admin to create configurable forms for storing specific types of information. Datatypes allow the admin user to ensure information is stored consistently throughout the system to ensure proper formatting.
  • Deductible Basis is determined by evaluating which is smaller: the specified Claim Value OR the Claim Deductible from the Comp Claim record. (Also see Claim Value.)
  • Configurable field display allows you to configure dataform fields and fieldsets to be hidden, read-only, or editable based on trigger conditions set by the system administrators. This allows for highly flexible dataform configurations based on workflow or business need.
  • Security entities allow or deny access to resources. They typically provide specific access rights (View / Edit / Add / Admin) to a system component such as a specific dataform, dataform field, dataform fieldset. They can also be used to allow or deny access to other system components, such as a button if that button is used to initiate functionality that needs to be secured. For instance, the Mass Update button located in the Task Search module is an example of this. It is also important to note that Global Admin users have full rights to View, Add and Edit tasks regardless of whether they have been granted access using a security entity.
  • The Extranet is a custom version of ClientSpace used by PrismHR to track client interactions, handle support, track development, and pretty much manage all internal and external communications at PrismHR in Sarasota. Yes, Virginia - we do drink our own Koolaid. The Extranet is a Candy over CORE solution for PrismHR with highly customized versions of some standard ClientSpace modules such as Client Service cases and Business Intelligence. Access to the Extranet is restricted to a few key personnel at our client sites, normally the principals and "Go To" people for ClientSpace within their organization.
  • Dataform fields are the containers where a specific piece of information is stored in the ClientSpace system. Adding a field to a dataform dynamically generates a column on that dataform's underlying SQL table and creates a series of SQL stored procedures to handle inserting, deleting, and editing the data stored in that field. Dataform fields can be grouped in Fieldsets for better organization of data on the page. Field requirement is negated when a field is hidden.
  • Dataform fieldsets are descriptive bounding boxes used to group sets of data on dataforms together. Fieldsets can be nested within each other, as well as dynamically hidden or displayed based on trigger values. Dynamically hiding a fieldset hides all of the fields within it. Field requirement is negated when a field is hidden.
  • The File Upload utility is a small Windows utility designed to Produce and/or Upload formatted files from a third party system into the ClientSpace system. The utility resides on the database or reports server and can be scheduled to attach to most SQL type systems and produce formatted reports that the utility will then upload to your ClientSpace installation via a secured https connection.
  • The filing cabinet scenario is a metaphor for the ClientSpace relational database and the way data is stored. The filing cabinet in this scenario is the database - a place to store and access information. The folders in the filing cabinet represent Workspaces in ClientSpace, with the individual papers or groups of papers in the folder representing Dataforms. A single document would be a Single dataform, Multiforms would be a collection of related documents (all of the employee applications for example, paperclipped together).
  • In the context of relational databases, a foreign key is a field (or collection of fields) in one table that uniquely identifies a row of another table. In other words, a foreign key is a column or a combination of columns that are used to establish and enforce a link between two tables. The table containing the foreign key is called the child table, and the table containing the candidate key (or primary key) is called the parent table. ClientSpace most commonly uses foreign key relationships to relate data between dataforms within the same workspace. An example of this would be the relationship between clients and locations. The ProjectID of the client would be the fkProjectID (fk for foreign key) of the location allowing you to store the locations for all clients in one table, yet still, relate a client's specific locations to the client workspace.
  • Global Admins are the designated administrators of your ClientSpace system. Global Admin functionality is set using the Global Admin option on the User detail record. A user with Global Admin rights is normally not subject to the system security, which restricts a non-admin user and thus can Add/Edit and Delete most system records, including users. Because of this unrestricted access, Global Admin rights should be provided infrequently and with extreme care.
  • This refers to the date a PrismHR client and their employees can log into and use their production ClientSpace site for the very first time. Prior to Go Live, clients work with their PrismHR account manager and business analyst to configure ClientSpace for your individual company needs and implement the initial modules used.
  • An expandable menu icon that, when selected, expands to display other menu options. The name reflects the three horizontal lines that resemble a hamburger. It is also delicious and tastes great with fries.
  • A hard error is an error that triggers to prevent you from executing an action that goes against a business rule. Often, you cannot proceed with saving the form until you correct the issue that triggered the error, or in some cases, where data intregity is being protected, your input will revert to the previous value.
  • HCM refers to PrismHCM. This is PrismHR's Human Capital Managment system. This solution was designed for HROs and Payroll Service Bureaus who require a more customizable/scaleable solution than a traditional PEO platform might provide. This allows the HRO to offer their clients the option of running their own Payroll, for instance.
  • The header or dataform header is the area at the top of each dataform reserved for custom configuration and information display, normally used to display aggregate information about a specific client stored on other dataforms.
  • Implementation refers to the initial setup and configuration of a client's production environment. Implementations vary from straight forward to very complex, depending on your needs and how many modules you wish to implement when you go live.
  • Imports to ClientSpace are a method of integrating other systems with the ClientSpace application and can include data from Payrolls systems, Loss Run imports, Claims management (Unemployment and Workers' Compensation), etc. Imports are managed through the Import / Export area of Admin Settings and generally consist of an Import Configuration mapping and an associated text file (.txt, .csv). These files can be produced by several methods, including the File Upload utility, or API integration.
  • Info bubbles or Tool Tips present field-level help. It is a bubble by a field where an Advanced Admin can write instructions to the user about how to use this field. Merely hovering over an available info bubble presents help text about the field.
  • The Workspace Landing Page provides a quick overview of the client. The Landing Page Tiles provide quick access to the client information in the form of a series of panels at the top of the Workspace Landing Page. Most tiles contain a selectable link in the header row to drill into more detailed information about that tile. Visible tiles vary based on the status of the workspace.
  • The beginning of the Sales process in ClientSpace - a lead can be defined as a potential prospect. A lead can be as simple as a Company Name, or a contact and Phone number and are recorded in a ClientSpace Organization record.
  • A running list of work items currently opened in ClientSpace. Left Nav items are hierarchical, meaning that in some cases, such as a task opened from a dataform, the lower item (task) takes precedence, making the higher item (dataform) read-only until the lower item has been closed (certain top-level objects such as Landing pages and Organizations are exempt from this behavior). This also allows you to close multiple items with one click. In the example, closing the dataform also closes the task that was opened from the dataform. This hierarchy can be multiple levels deep such as Workspace > Dataform > Task. Closing the workspace closes all the items below it in the hierarchy.
  • Custom header links allow you link to custom reports, merges and dataforms within the current workspace or the admin workspace, or even configure your own workflow from scratch.
  • Lookups are the configurable selection options available in the Core lookup datatype. Lookups are related to a Lookup Group, which describes the lookup and is used to configure the lookup datatype when creating a new drop-down field on a dataform.
  • Master Benefits Records or MBRs come in two flavors: Payroll Deduction MBRs, which are generated by merging EDV records collected from the payroll system based on a specific set of criteria, and Carrier Invoice MBRs, which are generated from imported carrier invoice records. Comparing the positive amounts received from payroll deductions to the negative amounts paid to carrier invoices is the basis of Benefits reconciliation in ClientSpace.
  • A ClientSpace merge gives our customers the ability to merge specific data from the ClientSpace system dynamically into your business documents and forms, removing the need for manual completion of forms, such as a Request for Proposal (RFP) or Client Service Agreement (CSA). Merges are available in Word, Excel, or PDF format.
  • A Merge Procedure is a piece of prepared SQL code that can be reused over and over again.
  • Literally meaning data about data, metadata in ClientSpace is what is known as Descriptive metadata, which is defined as "Data about individual instances of application data or the data content." The application of metadata in ClientSpace is through lookups, where a particular lookup code, such as ContractType has associated metadata that can be used to associate other information directly to a particular code or drive business logic. Metadata relationships require the creation of a special metadata form and configuration at the lookup group level.
  • Modules are configurable access buttons that allow you to open several system objects, including system dashboards, BI objects such as reports and BI Dashboards, and even external systems through Third Party Applications administration or the Outlook Add-in. Modules are securable and selectable at the user level allowing each user's module configuration to be unique.
  • A ClientSpace dataform where there may be multiple forms per Client Workspace, such as Locations. The Multi dataform has a one-to-many relationship with the Workspace, such as physical locations for a client, or paycheck records for an employee. An example of this is the Employee dataform.
  • The Organization record is where you store company information about a potential client. The Organization record provides you with a single place to put lead-related tasks and calendar events (such as meeting with your prospect) as well as phone calls, emails, and follow-up activities. The Organization record is where track detailed information about a prospect such as name, address, federal identification number, phone, fax, website, and other company data. Additionally, you can maintain several fields for tracking the prospect's progress through the sales pipeline.
  • Organizations or Orgs are client specific forms designed for collecting data on potential clients through the prospecting stages of the Sales Process. After pricing is required, a workspace is generated from the Org, creating a foreign key relationship between the Workspace and the Org.
  • The Outlook add-in is a separate application that installs into Outlook on your local desktop and communicates directly with your ClientSpace installation using a remotely connected Web service. This application is configurable from the modules configured on the user profile and allows you to Create Cases and Tasks from the content of an email, attach emails to existing cases and tasks and post to ClientSpace, which adds the email contents as an activity to the ClientSpace contacts whose email address matches any of the recipients.
  • A pipeline determines which rules are applied when the data is saved.
  • The pricing console is the integrated pricing module in ClientSpace PEO. This module aggregates data from the Pricing Batch, Pricing State, and Pricing Comp Code dataforms, enabling centralized management of Pricing and profitability at the client level.
  • A primary key is a special relational database table column (or combination of columns) designated to uniquely identify all table records. A primary key’s main features are: - It must contain a unique value for each row of data. - It cannot contain null (empty)values. This primary key from one table is used on other tables as a foreign key, allowing you to tie data from different tables together through this foreign key relationship.
  • PROD or production sites are the client installations our clients use to do their daily work. These sites are configurable by local Global Admins and any changes that are created in the production site, (such as new dataforms) require a copy of that site's database be taken and replicated to the PrismHR development site before we can add custom code based around these changes (a custom business rule on the new dataform).
  • The Project Milestone dataform is a specialized multiform designed to be used to track the step-by-step workflow associated with bringing a Project to completion. Milestones have a defined start and end date, as well as an actual completion date to help with keeping your project on track.
  • Category assigned to a potential client in ClientSpace. Prospects generally require the salesperson to collect data about the lead with the goal of generating pricing.
  • The relational model is the conceptual basis of relational databases. Proposed by E.F. Codd in 1969, it is a method of structuring data using relations. In the relational model, all data must be stored in relations (tables), and each table consists of rows and columns (kind of like a spreadsheet). Each table must have a header and body. The header is simply the list of columns in the table. The body is the set of data that actually populates the table, organized into rows. You can extrapolate that the junction of one column and one row will result in a unique value - this value is called a tuple. The second major characteristic of the relational model is the usage of keys. These are specially designated columns within a table used to order data or relate data to other tables. One of the most important keys is the primary key, which is used to uniquely identify each row of data. To make querying for data easier, most relational databases go further and physically order the data by the primary key. Foreign keys relate data in one table to the primary key of another table.
  • A ClientSpace release is the packaged update produced by a Sprint development cycle. More information about individual sprint release items can be found in our Release Notes.
  • Dataform fields can be required on save of the dataform either through configuration (selecting the Required option) or from business logic such as the RequireFieldOnThisForm business rule. When a field is required the system does not allow the dataform to be saved if the field is visible and empty.
  • A request for proposal (RFP) is a document that solicits proposal, often made through a bidding process, by an agency or company interested in procurement of a commodity, service or valuable asset, to potential suppliers to submit business proposals. In ClientSpace terms, this is normally in the form of a pre-formatted merge or report that uses ClientSpace data to customize the document to the prospective client.
  • Navigation center for links, notes, attachments, and time tracking items. The contents of the right navigation pane change based on the current active work object. For example, an open Org has a right navigation pane that contains Contacts, Activities, Appointments, Tasks, Attachments, and Security, while a Workspace Landing Page may only contain Links, Reports, Tasks, Activities, and Time Tracking.
  • A ClientSpace role is a unit of security used to define specific rights within the system and can be attached to individual users and one or more security entities. Roles can be automatically generated by the system, such as Departmental roles, or manually created by a ClientSpace admin to aggregate security functions in the system together and assign them to a user or users.
  • In Salesforce, a Flow allows you to build a business automation, such as sending an email, inserting, updating, or deleting data, and much more. The automation is configured to trigger based on an event. In ClientSpace, we call this a Workflow.
  • A Salesforce Opportunity is a Salesforce deal in progress. An Opportunity record is created when a lead is converted.
  • In Salesforce, what is referred to as a Stage is the same as a Status in ClientSpace. Examples include Lead, Client, Terminated, etc.
  • Entities are the security objects used by the application to check what rights a user has to view, create or modify a system object. Entities are most commonly created by securing a Dataform or dataform field.
  • Most PrismHR clients use our cloud environment to host the web and database servers that are ClientSpace. In a few instances, however, clients have opted to purchase their own servers and Self Host. Self hosting can make upgrades less frequent and more difficult as we do not have direct access to these servers.
  • Top level work items in ClientSpace are referred to as Sets and are indicated in the Work Items area of the Left navigation pane by a brown bar. Sets may contain Work Items and Sub Threads. Some examples of a Set would be a dashboard, Workspace Landing Page, or other type of ClientSpace module.
  • A ClientSpace dataform where there is only ever one per Client Workspace. A Single dataform has a one-to-one relationship with the Workspace. An example of a single form would be the Client Master dataform.
  • A soft error is a warning message triggered by a business rule to warn you that there is missing information on a form, or that you are about take an action that could have undesired consequences or is not considered a best practice. You can continue by clicking a confirmation prompt to proceed with the action or you can cancel the action.
  • SOUNDEX converts an alphanumeric string to a four-character code that is based on how the string sounds when spoken. SOUNDEX codes from different strings can be compared to see how similar the strings sound when spoken. Soundex checking is used when creating new organizations in ClientSpace to ensure that Organization detail records are not duplicated.
  • A stored procedure is a piece of prepared SQL code that can be reused over and over again. So instead of ClientSpace having to create the same select statement every time you open something like the workspace search dashboard, the code is saved as a stored procedure and then just called by ClientSpace when you want to look for a workspace. There are multiple advantages to this, including efficiency (it is more efficient to store the code once than to re-write the same code again and again) and consistency - as the procedure is stored it will work in the same way every time. In addition to running the same SQL code over and over again, you also have the ability to pass parameters to the stored procedure, in our workspace search example this could be the Workspace name or Client Number, and depending on what parameters are passed, the same stored procedure can produce different results to match your request.
  • A Sub-thread is a Child of a work item in the left navigation or Work Center area. Examples of sub-thread items would be time records opened from a task, or a task record opened from a case.
  • Dataform subscribers are users that have requested dataform specific notifications when a save occurs. You can subscribe to dataform notifications by using the Subscribers Action item on any dataform where this is enabled, or for Client Service Cases by adding a subscription record using the Case Type Subscriptions dashboard.
  • System administration entails Global Administrator(s) configuring the ClientSpace system to suit the specific needs and business requirements at your company. Much of the work of system administration is performed through the System Admin control panel. Everything from App Settings to User Administration can be configured in this area, including such items as application security, Departments, System Defaults, Lookup configuration, and more.
  • Used in ClientSpace to track individual work items, tasks are configurable assignment items with an Owner and AssignedTo person and defined start and end dates. Tasks can be linked to workspaces, or directly to an associated dataform. Tasks can also be scheduled using the Scheduled Workflow Channels, allowing for complex workflows to be built within the application.
  • Template Workspaces are special workspaces used for cloning during the workspace creation process. In this way, ClientSpace allows you to set up multiple workspace configurations (such as an industry-specific workspaces with a specific, limited list of TOC items) then choose how you want the workspace to look and feel by selecting the appropriate template during workspace creation. Template Workspaces are not available from Workspace Search and must be accessed from System Admin > Workspace Templates.
  • A thread is a work item organized below and associated with a Set item in the work items are of ClientSpace. Threads may have sub-threads associated below them. An example of this would be a Workspace landing page (SET) opened in the Work items area, a Client Service case (Thread) opened from the landing page, and a task (sub-Thread) opened from the Case. Closing the Thread or Set using the X in the upper right corner closes all associated items below it.
  • Typeahead search is a method for progressively searching for and filtering through text. It is also sometimes known as autocomplete, incremental search, search-as-you-type, inline search, instant search, and word wheeling (from dynamicweb). As you type in the field, one or more matches for the term are found and immediately presented. The immediate feedback enables you to find what you are looking for much quicker than scrolling through a potentially long list.
  • User Acceptance Testing or UAT is both the ClientSpace installation and the process used by the PrismHR quality assurance department to test new development items. This installation type is also used by PrismHR account managers and business analysts to demonstrate new candy functionality to our clients before upgrading their production site with the new changes.
  • ClientSpace users are distinct logins used to access the ClientSpace system. Users can be defined as one of two types: - Internal users: These would normally be employees of the company using ClientSpace as a CRM. - External users: Non-employees who need to access ClientSpace data. (brokers or clients for example).
  • Panels that appear on the landing page, or dataform header that offer snippets of data from other sources within the database, such as the Required Forms widget at the top of the Client Master page. Also called landing page tiles.
  • The Wildcard (%) search symbol is used to search fields for records or list values containing the search string that follows the % symbol.
  • The left navigation pane in the application is called the Work Center. This is were multitasking takes place as each work item opened is opened with its own thread.
  • A top-level item (in the hierarchy) opened in the Work Center is called a work item. Each work item is opened under its own thread, allowing for true multitasking within the app.
  • The step-down arrangement of work items and sub-threads in the work center showing related items. Work item hierarchies can be collapsed to preserve space. Closing an item in the hierarchy closes all items below the closed item.
  • Workflow Channels enable you to create automatically generated tasks and dataforms (and associated notifications) based on predefined triggering conditions.
  • Workflows map business processes systematically and help prevent some tasks from falling through the cracks or getting lost amongst numerous emails. In ClientSpace, Workflows are often designed using template tasks and configurable links.
  • A Workspace is a set of dataforms for collecting and storing information, normally about a specific client or business. Workspace dataforms are related to a specific project, and so share a common fkProjectID (foreign key). Workspaces are often created by cloning a Template Workspace, allowing for a consistent look and feel, as well as a consistent set of dataforms.
  • A current (based on Contract Status) overview of the Client Workspace. Think of it as a folder on your computer that contains information about a specific client.
  • Workspace Templates are special workspaces used for cloning during the Workspace creation process. In this way, ClientSpace allows you to set up multiple workspace configurations (such as an industry-specific Workspaces with a specific, limited list of TOC items) then choose how you want the workspace to look and feel by selecting the appropriate template during workspace creation.