NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm

Glossary

 
Any specialized subject brings its own language, and Pulse is no exception.  The following document is designed to define some common Pulse terminology and help to provide a common language when speaking about all things Pulse.  

 


 A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z


A

ActiveX Controls (Classic)

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. For more  information about installing the ActiveX controls see Internet Explorer Settings for ClientSpace.

Action Center

The right navigation area in the application is referred to as the Action Center and provides a centralized location for actions within the application. Actions available in the Action Center vary based on location in the application.  For more information about the Action Center see Navigating ClientSpace.

Action Items

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 like "My Tasks" and Activities.

Agile Development

The methodology of software development used at PrismHR that focuses on frequently delivering small increments of working software in regular development cycles or Sprints.

Ad-hoc Reporting

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.

Admin Workspace

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.  Having these dataforms live in a single workspace makes management and configuration of them easier.

API

Application Programming Interface 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 back and forth between the two systems. APIs generally require additional configuration in both ClientSpace and the other software system and may have an associated cost. Some of the current ClientSpace APIs include:

  • PrismHR: two-way communication between ClientSpace and the PrismHR payroll System for Client and Employee data
  • Salesforce: two- way communication between the sales process in ClientSpace and the Salesforce API.
  • Single Sign On: ClientSpace API which allows you to connect external system users to ClientSpace via Single Sign On (requires a user account for the user in your ClientSpace installation – can be External user)
  • DocuSign: Provides for electronic signature of merged ClientSpace documents
  • Email to Case: Configure ClientSpace to sweep through an IMAP enabled mailbox to generate Client Service Cases automatically and send automated email responses.

For more information regarding current API availability and upcoming projects, contact your PrismHR Account Manager.

B

Business intelligence

Business intelligence, or BI, is an umbrella term that refers to a variety of software applications used to analyze an organization's raw data.  In the case of 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: 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: Fields are the individual data points available from a datasource in business intelligence. An example of this would be – tblOrganization is the datasource, Name, Address1, City, etc. would be 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.  
  • Exporting: 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.

For more information on how Business Intelligence reporting from Izenda works, reference Business Intelligence.

Business logic (Rules)

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 even automatically complete fields based on values from other source fields.  For more information about business logic and rules, see Configuring Rules and Business Logic.

C

Candy

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.

Case

If you use Cases and Tasks, then a Case could be your top-level project and Tasks would be assigned to complete the project. For example, to onboard a new employee you create a Case and set the manager as the Assigned To person. Then you would create Tasks that contribute to the onboarding process such as procuring a computer (assign to IT person), setting up the computer (assign to IT person), set up onboarding training (manager of the learning management system), walk the new employee through benefits enrollment (human resources staff), and so on. Tasks are for the individual items that need to be completed, sometimes by the person that's running the case, sometimes by someone else.   

Chiclet (NEXT)

Individual filtered search criteria that display as buttons below the Quick search on the Dashboard modules in Next.

Client Installation

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 will have separate databases to store the individual data associated with the site.

ClientSpace

A powerful Enterprise Workflow Automation platform, which 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

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

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 or even Users. Cloning is often used to provide consistency of data, or for Workflow design.

Cloud

The word "cloud" often refers to the Internet, and more precisely to some datacenter full of servers that is connected to the Internet - in ClientSpace terms, we purchase datacenter space from a third party in a secured offsite location which we use to house the servers that run each of our ClientSpace installations. 

Concierge

A category of the PrismHR work process which does not include Sprint development work. Concierge work can include such items as database scripts, configuration, imports, merges, and reports.

Configurable 

Configurable features may be unique to an installation - these are customizations to the system that may be configured by a Global Administrator of the system through the Admin Settings area. Some examples of Configurable items are Dataform links, template tasks, 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 

Contextual help text may 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 .  

Core Layer 

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 however as it is the foundation of all ClientSpace functionality. This includes our powerful Dataform Engine, Workflow Engine, Data Integration tools, and Ad-Hoc Reports & Dashboards. Using the tools available here we are able to build elaborate systems to help manage your business. 

CRM

Customer relationship management (CRM) is a term that 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

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.

D

Dashboard

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.

Database

A database is an organized collection of data.[1] 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 modeling the employees and their related information that is attached to a client in order to facilitate HR management.

Database Management System (DBMS)

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.

Dataform

The dataform in ClientSpace 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. For more Information see Dataforms: Workspace Building Blocks.

Datasource

With regards to reporting, 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.  

Datatype

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 in a consistent manner throughout the system and can help to ensure proper format is preserved.  For more information about datatypes, see Dataforms: Workspace Building Blocks.

DEV

The Dev or development site is the client installation used by PrismHR for developing new code. Changes made to this site are scripted into packages that can then be applied to other sites such as UAT or PROD.  As such DEV sites are accessible only to PrismHR employees.

Display Configuration

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. For more information on field display configuration refer to Configuring Dynamic Field Display.

E

EDV (Employee Deduction Vouchers)

EDVs are ClientSpace records each of which equates to a single deduction record from an employee payroll voucher (check). These EDVs are merged to generate Payroll Deduction Master Benefit records or MBRs which are then compared to other MBR records created from Carrier Invoices for the same time period and client. This is the heart of Benefits Reconciliation.

Entities

Units of security - entities provide specific access rights (View / Edit / Add / Admin) to a system component, such as a specific dataform or even dataform field. Entities can also be more esoteric, such as the Download entity which provides access to download dataform data in ClientSpace.  For more information about security entities review Organization and Workspace Security Configuration

Extranet (PrismHR)

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. And 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 clients, normally the principals and "Go To" people for ClientSpace within their organization.

F

Field

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 dataforms 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 may be grouped in Fieldsets for better organization of data on the page. Field requirement is negated when a field is hidden.

Fieldset

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.

File Upload Utility

The PrismHR 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.  For more information about file uploads, review the File Uploads section of our KnowledgeSpace documentation. 

Filing Cabinet Scenario

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). 

Foreign Key Relationships (Primary key to Foreign key)

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.

G

Global Admin

Global Admins are the designated administrators of your ClientSpace system. Global Admin functionality is set via the Global Admin checkbox 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 has the ability to 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.

Go Live Date

This refers to the date a PrismHR client and their employees are able to 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.

H

Hamburger Menu

An expandable menu icon found in NEXT  that when clicked, will expand 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.

Header (dataform)

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. Headers in Classic can also contain dynamic links to other dataforms, reports, and merges. 

I

Incident

See Tasks.

Implementation

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

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 a number of methods, including the File Upload utility, Formatted reports or API integration.

Info Bubble

Info bubbles  present field level help. Simply hovering over an available info bubble will present the text that has been saved into the description of this field. This is often used to describe the math used for calculated fields.

L

Landing Page Tiles (NEXT)

The Workspace Landing Page provides a quick overview of the client and 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 clickable link on the header row to drill into more detailed information about that tile. Visible tiles vary based on the status of the workspace.

Lead

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.

Left Navigation: Work Items (NEXT)

A running list of work items currently opened in ClientSpace Next.  Left Nav items are hierarchical, meaning that in some cases, such as a task opened from a dataform, the lower item (task) will take 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 will also close the task that was opened from the dataform.  This hierarchy can be multiple levels deep such as Workspace – Dataform – Task.  Closing the workspace will close all the items below it in the hierarchy.

Links (configurable)

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.  For more information on Links, see Configuring Links.

Lookups

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 dropdown field on a dataform.

M

MBR (Master Benefits Record)

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.

Merge

A ClientSpace merge gives our customers the ability to merge specific data from the ClientSpace system dynamically into your businesses 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 currently available in Word, Excel, or Pdf format.

Metadata

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 will have 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

Modules are configurable access buttons which allow you to open a number of 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 users module configuration to be unique.

MultiForm

A ClientSpace dataform where there may be multiple forms per Client Workspace. An example of this would be the Employee dataform.  For more information on dataforms and their configuration read Dataforms: Workspace Building Blocks.

N

Not-It! 

 A mission-critical process at PrismHR by which a person is selected who will be responsible for procuring the fermented barley and hops for the Friday afternoon team bonding session.

O

Org

Organizations or Orgs are client specific forms designed for collecting data on potential clients through the prospecting stages of the sales process. When pricing is required, a workspace is generated from the Org, creating a foreign key relationship between the Workspace and the Org.

Outlook Add-In

The Outlook add-in is a separate application which installs into Outlook on your local desktop and communicates directly with your ClientSpace installation via a remotely connected Web service. This application is configurable via 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.

P

Pricing Console

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, allowing for centralized management of Pricing and profitability at the client level.

Primary Key

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 will be used on other tables as a foreign key, allowing you to tie data from different tables together through this foreign key relationship

PROD

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, etc.) 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).

Project Milestone

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.

Prospect

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.

R

Relational Database

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.

Release (software)

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.

Requirement (field)

Dataform fields can be made 'required' on save of the dataform either through configuration (checking the Required checkbox) or via business logic such as the RequireFieldOnThisForm business rule. When a field is required, the system will not allow the dataform to be saved if the field is visible and empty. 

RFP (Request for Proposal)

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 which uses ClientSpace data to customize the document to the prospective Client.

Right Navigation: Action Center (NEXT)

Navigation center for links, CRM notes, attachments and time tracking items.  The contents of the Right Nav will change based on the current active work object. For example, an open Org will have a Right nav that contains Contacts, Activities, Appointments, Tasks, Attachments, and Security, while a Workspace Landing Page may only contain Links, Reports, Tasks, Activities, and Time Tracking.

Role

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.

S

Scrum

An iterative and incremental agile software development framework for managing product development focused on maximizing the team's ability to deliver quickly and respond to emerging requirements.

Security Entities

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. For more information on Security entities review Security Entities in the Organization and Workspace security document.

Security Policy Editor (Classic)

The ClientSpace security policy editor is a small application which installs to your local desktop and allows the ClientSpace application to make remote calls to MS Office applications such as Word and Excel to generate automated, prefilled documentation in the form of Merges.  For more information see Installing And Configuring The Security Policy Editor.

Self Hosted

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.

SET (NEXT)

Top level work items in ClientSpace NEXT 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.

Single Form

A ClientSpace dataform where there is only ever one per Client Workspace.  An example of a single form would be the Client Master dataform.  For more information on dataforms and their configuration read Dataforms: Workspace Building Blocks.

SOUNDEX Checking

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.

Sprint 

A sprint (or iteration) is the basic unit of development in Scrum. The sprint is a "timeboxed" effort; that is, it is restricted to a specific duration. The duration is fixed in advance for each sprint, for PrismHR sprint schedules normally last 6 weeks.

Stored Procedure

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 - since 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.

Sub-Thread (NEXT)

A Sub-Thread is a Child of a work item in the left navigation or Work Center area in NEXT.  Examples of sub-thread items would be time records opened from a task, or a task record opened from a case.

Subscriber (Dataform)

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

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 done 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.

T

Tasks

Used in ClientSpace to track individual work items, tasks are configurable assignment items with an Owner and Assigned To person and defined start and end dates. Tasks can be linked to workspaces, or directly to an associated dataform. Tasks can also be scheduled via the Template Task scheduler, allowing for complex Workflows to be built within the application. Additionally, Tasks can be individual items that need to be completed for the project that is defined at the Case level. In this scenario, a Task is a child of the parent Case.

Template Tasks

Template Tasks are really just pre-made Tasks that are either automatically generated in real time when something happens in ClientSpace, scheduled based on a date field, or manually initiated on demand. Template Tasks can also be configured to serve the purpose of providing a notification to users when something happens.  For more information about template tasks and their configuration, see Template Tasks - Automate Your Workflow.

Template Workspace

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 via System Admin > Workspace Templates.

Thread (NEXT)

A Thread is a work item organized below and associated with a Set item in the work items are of ClientSpace Next. 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 will close all associated items below it.

Typeahead

Typeahead search is a method for progressively searching for and filtering through text. It is also sometimes known as autocomplete, incremental searchsearch-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.

TOC (Classic)

The TOC or Table of Contents refers to the Left Navigation bar that appears when inside a workspace in the ClientSpace application. TOC items can be secured as well as grouped in folders, making the TOC configurable by the user.

U

UAT

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 prior to upgrading their production site with the new changes.

Users

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).

W

Widget

Panels that appear on the landing page, or dataform header in Next 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.

Work Center

The Left navigation pane in the application is called the work center.  This is were multi-tasking takes place as each Work Item opened is opened with its own thread.  

Work Item

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.

Work Item Hierarchy

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 will close all items below the closed item.

Workflow

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.

Workspace

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.

Workspace Landing Page (NEXT)

A current (based on Contract Status) overview of the Client Workspace. The Workspace Landing Page acts in many ways as the container for Client Information, much as the TOC did in Classic.  Links may be configured on this page.



RETURN TO TOP

 A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z



 Images
 



NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm