Fast_Track_131-205.txt

• - Test validity of Single input value
• - Built using Java
• - Can be referenced in other rules
• - Property Rules
• - Validate Rules

131

• - Yes
• - Validate users and data from other systems

132

- Process Category

133

• - An Activity
• - Flow Action

134

- Property: must be a single value property or reference to a property in repeating group

- Required: when checked user must input

- Conditions: allows for detailed conditions

- Continue: process other rows if current fails

135

- Validate: directly validate a top-level property

- Validate Each: directly validates an embedded property

- Call: calls another validate rule

- Call for each: calls another validate rule on an embedded page

136

- To determine the conditions of the validation select the Expression Field

- Click to find Expression Types

137

- Persons, Organizations, or other entities involved in the progress of a work object

- May not have any responsibility

- Can be thought of entity "Data"

e.g., - Applicant for a quote; - External lender or insurer

138

- Roles can determine a work party's involvement (i.e., interested, originator, etc.)

- Work Party information is aggregated by party roles such as Originator, Customer, Manager, etc.

139

- In a Work Party rule

- Work Parties are named default by convention

- Listed in the Process category

140

• - To hold commonly used Properties for Roles such as:
• - Originator
• - Manager
• - Interested
• - etc.

141

Data-Party-Com (for business orgs)

Data-Party-Gov (for government orgs)

Data-Party-Operator (for Process Commander Operators)

Data-Party-Org (for Non-Profit orgs)

Data-Party-Person (Individuals)

142

- Work Parties within Work Object

143

- Correspondence

- User Interface display

- Reporting

144

- Makes it easy to capture and store info about a Party, Person, or other in a Work Object

145

PyWorkParty

146

CoreParty

PartyDisplay

147

- To allow users to add Work Parties while they process assignments, add AddParty as local flow action for that assignment

148

- Templates used for out-going notifications

- Can include Properties & other rules for customized output

- Are located in Process Category

149

- Rich Text Editor

150

• - Email
• - Fax
• - Mail
• - SMS Text

151

1) Notify - used to send Auto notification message about assignments

2) Utility - used to send other correspondence; use with OOTB CorrNew activity

152

- Attach notify shape to assignment shape (Notify is left facing arrow with solid back)

153

• - CorrQuickStart
• - CorrNew

Input Parameters: CorrName, PartyRole, Broadcast (sent to all parties)

154

- Used for easily maintained Data Instances

• - Data Table editor allows developer to easily maintain data instance that have a simple structure
• - Can add, update, or delete instances of data for which no form is defined

155

- Use only for small data set

- Typically much of the data used by PRPC resides outside

Instead, create a separate DB table if your data set: contains hundreds of items, have high turnover, may be moved to other systems

156

• - Click Application > Data Tables
• - Starts Wizard
• - Click Add to Create

157

• - Data Class & Parent Class
• - Define Properties stored in the table

158

- Class generated with the data instances for the Data Table

159

- a display is presented when a condition is met

e.g., a drop-down list of clients only appears if Preferred Client check box is checked

160

• - Client Events
• - Dynamic conditional display of fields
• - Dynamic selects
• - Dynamic calculations
• - "smart info" pop-ups

• - HTML properties used to render properties in a fixed mode
• >Many Rule-HTML-Property rules available OOTB
• >Can create custom HTML Properties

161

1) Connectors

2) Services

162

- Integration-Connectors category

163

• - MQ (Queue Information)
• - RDB (Database Information)
• - SOAP (Host Information)
• - Parse & Stream rules (e.g., XML - parse or assemble stream)

164

- Used in a flow to call an activity (which calls a connector rule)

>Steps in activity may update property values in the clipboard or call a method that calls the connector rule

165

• - SOAP and .Net
• - IBM Websphere
• - JMS (Java Messaging Service)
• - Java (Interface to other Java apps)
• - BPEL (With other rules engines)
• - EJB (Server side interaction Java apps)
• - File (Output file)
• - HTTP (Send XML, text, etc.)
• - J2EE (Connect to ext. systems using common client interface)
• - RDB (Databases using SQL)

166

- Rectangle box with clock on right

167

• - Reports result of several checks on the rules
• - Checks for Warnings/Summarizes
• >Warning by Rule Type chart
• >Performance warnings by Rule Type
• >% of Rules with warning Rule Type
• >Warning by severity Pie Chart
• >Browser Compatibility
• >Accessibility

- Encourages good design & summarizes warnings

168

• - PRPC provides automated documents
• >Assists developers in providing detailed applciation documentation

- Is only as good as the comments entered in History Tab of various rules

- Developers should be disciplined in commenting rules

169

- An HTML Page listing the rules associated with the currently selected application

- Select Application>Inventory

170

- MS Word listing all rules (useful for SOX purposes)

- Select Application > Document

171

1) List View

2) Summary View (can drill down)

3) Chart

172

- Monitor Activity

173

- Rule Reports

174

1) Monitor Assignments

2) Monitor Processes

3) Analyze Process Quality

4) Analyze Process Performance

175

- Processes can be monitored by Category & Dates

176

- Custom Report button for the list of custom reports

- Browse Category button is used to browse categories

- Create Custom Reports button starts the report wizard

177

• - Rule Checkouts
• >Checked out by time
• >All Checkouts
• >Checked out by RuleSet, version

• - Updated
• >Recently by me
• >All by me
• >Summary of all recently updated
• >Summary of recently updated by RuleSet

178

- Report Wizard allows creation of Reports based on certain criteria

179

- The WorkManager Portal allows managers to leverage over 40 OOTB work related reports.

- Can create own ad-hoc work reports using the Monitor Activity workspace.

180

• - Show work
• - Process work
• - Find work

181

- Portal layout is defined within an access group

• - OOTB Portals:
• >WorkUser
• >WorkManager
• >Developer

182

- Managers can transfer from Operator to another or to Work Basket

- Assignments can be automatically transferred depending on an operator's availability

183

• - Bulk Processing can perform one action on each of multiple assignments
• - Can perform on all assignments in a WorkList or WorkBasket
• - Transfer work from select operator or from Select Work Basket
• - Re-assign Operator's work to other operator or Work Basket

184

- Manage & coordinate the execution of separate but related processes.

e.g., Customer calls to log several related problems or a P.O. that requires each item to be ordered separately

185

• 1) Covers
  
  2) Folders
  
• 186

- Split a case into separately executing process (for concurrency)

• - Split a case into separate Work Objects (allows the work objects to be opened and processed independently from one another
• > Concurrent Execution

187

- No - can only belong to 1 Cover

- Nested Covers are not allowed

188

- No, nested Covers are not allowed

189

- Harness rules

190

- Cover Harness

191

- Hold a collection of Work Objects, Covers, and/or other Folders

- Better for managing large sets of items (20 or more)

- Do not Provide coordinated processing

192

- Like Covers, a built-in user interface is available for adding & removing items

193

• - Application migration (from Dev to QA, etc.)
• >When moving from Elaboration phase to Transition phase

• - Work is being done remotely with no access to the Internet
• >e.g., Development

194

• - Desired Rules and data must be:
• >Archived
• >Downloaded from Server
• >Imported in next environment

• - Process
• >It creates a Product Rule
• >Zip file created from Product
• >Zip is downloaded from Server
• >Zip is uploaded in Server2

195

• - Locate the Product Rule
• >Select Rule by Type tool
• >Select SysAdmin category
• >Click Product
• >Select QuoteApplication

• - Create and download the archive
• >Click CreateZipFile button
• >Enter Filename (e.g., MyFt55Work)
• >After created, click hyperlink to download zip

- File>Import>Import Archive

197

• 1) Iterative approach
• 2) Establish a robust foundation
• 3) Do nothing that is hard (use OOTB)
• 4) Limit custom Java
• 5) Build for change
• 6) Design intent-driven process
• 7) Create easy to read flows
• 8) Monitor performance regularly
• 9) Calculate & edit Declaratively, not Procedurally
• 10) Keep security object-oriented too

• - Use OOTB functions - especially in the initial release
• - Avoid custom HTML screens or adding buttons
• - Always use "Auto generate HTML"
• - Always use standard rules, objects, and properties
• - NEVER add a Property to control status and typical work or for managing timing of work

198

• - Design Class Structure to comply with recommended class pattern
• - Understandable, easy to extend and use the standard work and data classes
• - Use organization entities as start pattern - then proceed with class groups
• - Lead with Work Objects
• - Position Rules correctly by class and/or ruleset
• - Actively use inheritance to prevent Rule redundancy

199

- Identify & define 10-100 specific rules that business users own and will maintain

- Activities should not be on this list

201

• - Your app control structure must consist of Flows and Declarative Rules, calling Activities only as needed
• > Use Flow Actions to prompt users for input
• > Present fewer than 5 connector flow actions for any 1 assignment - if you need more re-design the process
• > Maximize re-use, create activity rules with single purpose

202

• - Flows must fit on 1 page
• - Must NOT contain more than 15 Smart Shapes (Excluding routers)
• >If more than 15, create sub-flow or use Parallel Flows

203

• - When rule of Property is calculated or validated, you must use declarative rules wherever appropriate
• >Create a Declare expression rule instead of using a Property-Set method in an Activity
• >Use a Declare Constraint rule instead of Validation Rule

204

• - Security design must be rules based and role-driven on who should have access to each type of work
• >Never code Security controls
• >Use standard PRPC access roels to start with
• >Use RuleSets to segment related work for the purpose of introducing rule changes - not as security measure

205