1 / 12

K2 blackpoint Fundamentals

K2 blackpoint Fundamentals. Module 1: Understand. J Scott Pitman – scottp@k2.com. Overview. What is K2 blackpoint, the product?. how are K2 blackpoint applications used?.

dacian
Télécharger la présentation

K2 blackpoint Fundamentals

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. K2 blackpoint Fundamentals Module 1: Understand J Scott Pitman – scottp@k2.com

  2. Overview

  3. What is K2 blackpoint, the product?

  4. how are K2 blackpoint applications used? People interact with K2 applications using SharePoint. Including using Lists, Workflowforms, and InfoPath forms. People also use theK2 Worklist Web Part to interact with user tasks. • Reporting and administration is handled through K2 Process Portalsthat live inside SharePoint.

  5. how are K2 blackpoint applications built? K2 Studio OR K2 Process Designer

  6. designing K2 blackpoint applications K2 Studio Installed on analyst’s computers Full functionality with no code K2 Process Designer No installation, requires Silverlight Limited functionality with ease of use

  7. the role of the K2 Server People Systems K2 assigns work to people and manages the completion of that work using K2 Client Events Work assigned to a user is collected in his own Worklist Each user’s worklist tracks all the work they have been assigned across all running K2 processes K2 assigns work to machines and manages the completion of that work using K2 Server Events Work assigned to machines is executed immediately

  8. applications and processes K2 blackpoint applications are made up of one or more K2 processes It is helpful to consider any K2 process lifecycle in two parts: Start and Run Process Start Process Running / Active InfoPath Integration SharePoint Workflow Integration SharePoint Events Integration K2 Client Events (work for people) K2 Server Events (work for machines)

  9. activities, events and lines Start Activity This is an illustration of the simplest possible process allowed with K2 blackpoint. This process has a Start Activity where the process begins. This process has one Activity other than the start activity. This activity is attached to the default Start Activity with a Line. Lines are one possible container for the Rules that drive K2 processes. Except for start, every Activity must include at least one Client Event or Server Event. Line Activity Event

  10. rules Line rules are based on Boolean logic. This just means that the rule must evaluate to either true or false. In the example below, the line rule will evaluate to true (if expense amount is less than or equal to $5000) OR (if the expense type is “cellphone” AND amount < $50) Line rule Boolean Line rules that evaluate to true are followed to the next Activity. Line rules that evaluate to false are ignored. Line rules often use data stored in Process Data Fields or Process XML Fields.

  11. summary K2 blackpoint is a platform for developing applications that extend workflow functionality in SharePoint. Applications are deployed to a K2 server at which point anyone with proper permissions may use the application as designed. Applications are made up of one or more processes. When designing K2 processes it is helpful to consider the process start and process run separately. Processes contain one or more activities, or stages, that are connected by lines. Lines are one possible container for business rules. Each activity must contain at least one client event or server event. Client events assign work to people while server events assign work to machines.

  12. Questions?

More Related